Cargo handling plan support system and program

Abstract

To realize a cargo handling plan support system which is relatively easy to implement and is capable of automatically generating a cargo handling plan.SOLUTION: A cargo handling plan support system (7) includes: a client device (3) having a client module (31) for receiving an input of a calculation instruction for a cargo handling plan and transmitting a calculation request to a server device (2); and the server device (2) having a server module (21) which, upon receiving the calculation request from the client device (2), reads out data for calculating the cargo handling plan from a memory device (4) and instructs a calculation engine (22) to calculate the cargo handling plan. The calculation engine (22) calculates the cargo handling plan by a mathematical optimization technique according to an instruction by the server module (21).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a cargo handling planning support system that supports cargo handling planning for a ship. [Background technology]

[0002] When creating a plan for ship loading and unloading (for example, a plan for the work required at a port when transporting cargo by ship, such as unloading and loading containers; hereafter referred to as a loading and unloading plan), it is necessary to take into account a wide variety of information, such as the balance of the ship in question, the containers to be loaded, and the loading and unloading equipment to be used. Furthermore, creating a ship loading and unloading plan is a difficult task, as it relies in part on the planner's tacit knowledge.

[0003] For this reason, there has been a need for the development of technology to support ship loading and unloading planning. Patent Document 1 below is an example of a document disclosing technology that supports ship loading and unloading planning. Patent Document 1 discloses a shipping plan creation method that includes a shipping product information extraction step of extracting information about products scheduled for shipping from a product shipping database that records product shipping schedule information and product attributes and a ship database that records information about the ships that will transport the products; a calculation step of determining the loading holds and order on the transport ship based on the extracted shipping product information; and a step of outputting the calculated plan results. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-247219 Summary of the Invention [Problem to be solved by the invention]

[0005] To realize the shipping schedule creation method described in Patent Document 1, it is necessary to have a computer execute each of the above steps. However, it is not easy to incorporate a computer with such functions into the container terminal operation systems used in various port facilities. This is because incorporating such a computer would require large-scale modifications to the existing container terminal operation systems.

[0006] An object of one aspect of the present invention is to realize a cargo handling plan support system that is relatively easy to implement and that can automatically generate cargo handling plans. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, one aspect of the present invention provides a cargo handling plan support system that includes a client device, a server device, and a storage device that stores data for calculating a cargo handling plan, wherein the cargo handling plan is either a stacking quota plan that plans the stacking quota of containers on a ship, or a shipping plan that plans the order in which containers are to be loaded onto the ship, wherein the client device includes a client module that receives input of a calculation instruction for the cargo handling plan and, upon receiving the input, sends a calculation request to the server device, wherein the server device includes a server module and a calculation engine, wherein, upon receiving the calculation request, the server module reads the data from the storage device and instructs the calculation engine to calculate the cargo handling plan, and the calculation engine calculates the cargo handling plan using the read data in accordance with the instructions using a mathematical optimization method.

[0008] In addition, in order to solve the above-mentioned problems, a program according to one aspect of the present invention causes a computer to execute the steps of accepting input of calculation instructions for a cargo handling plan, which is either a stacking quota plan that plans the stacking quota of containers on a ship or a shipping plan that plans the order in which containers are to be loaded onto a ship, and sending a calculation request to a server device upon accepting the input, receiving the cargo handling plan calculated by the server device using a mathematical optimization method, and accepting input indicating whether or not the received cargo handling plan is adopted.

[0009] In addition, in order to solve the above-mentioned problem, a program according to another aspect of the present invention causes a computer to execute the steps of receiving, from a client device, a calculation request for a cargo handling plan, which is either a stacking quota plan for planning the stacking quota of containers on a ship or a shipping plan for planning the order in which containers are to be loaded onto the ship; upon receiving the calculation request, reading out data for calculating the cargo handling plan from a storage device that stores the data; instructing a calculation engine that calculates the cargo handling plan using a mathematical optimization method using the read data to calculate the cargo handling plan; and acquiring the cargo handling plan calculated by the calculation engine and transmitting the acquired cargo handling plan to the client device. [Effects of the Invention]

[0010] According to one aspect of the present invention, it is possible to realize a cargo handling plan support system that is relatively easy to implement and that can automatically generate cargo handling plans. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing an overview of a container terminal operation system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram illustrating an outline of a shipping operation. [Figure 3] FIG. 2 is a diagram illustrating a cargo loading area in a ship hull. [Figure 4]1 is a block diagram showing an example of the configuration of a cargo handling planning support system according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing an example of a UI (user interface) screen that presents a stacking plan calculated by a calculation engine. [Figure 6] FIG. 10 is a diagram showing an example of input data used in optimization calculation of a stacking frame plan. [Figure 7] FIG. 10 is a diagram illustrating an example of variables used in optimization calculation of a stacking frame plan. [Figure 8] FIG. 10 is a diagram illustrating an example of constraints for a stacking frame plan. [Figure 9] FIG. 10 is a diagram illustrating an example of constraints for a stacking frame plan. [Figure 10] FIG. 10 is a diagram illustrating an example of an objective function of a stacking frame plan. [Figure 11] FIG. 10 is a diagram showing an example of a UI screen for receiving input of input data for calculating a work plan for cargo handling equipment. [Figure 12] FIG. 10 is a diagram showing an example of a UI screen that presents a work plan for cargo handling equipment. [Figure 13] FIG. 10 is a diagram illustrating an example of a UI screen that presents an unloading plan. [Figure 14] FIG. 10 is a diagram illustrating an example of a UI screen that accepts input of input data for calculating a shipping plan. [Figure 15] FIG. 10 is a diagram illustrating an example of a UI screen presenting a shipping plan. [Figure 16] FIG. 10 is a diagram showing an example of input data for a shipping plan. [Figure 17] FIG. 1 shows examples of types of containers that may be shipped. [Figure 18] FIG. 10 is a diagram illustrating an example of input data related to a container. [Figure 19] FIG. 10 is a diagram illustrating an example of variables used in optimization calculations for a shipping plan. [Figure 20] FIG. 10 is a diagram illustrating an example of constraints for a shipping plan. [Figure 21] FIG. 10 is a diagram illustrating an example of constraints for a shipping plan. [Figure 22] FIG. 10 is a diagram illustrating an example of an objective function for shipping planning. [Figure 23] FIG. 10 is a diagram illustrating an example of an objective function for shipping planning. [Figure 24] 10 is a flowchart illustrating an example of a process executed by a client device. [Figure 25] FIG. 10 is a diagram illustrating an example of input data that the client module transmits to the server device. [Figure 26] 10 is a flowchart illustrating an example of a process executed by the server device. DETAILED DESCRIPTION OF THE INVENTION

[0012] [Container terminal operation system configuration] A container terminal operation system 100 including a client device 3 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an overview of the container terminal operation system 100. Fig. 1 also shows a server device 2 according to this embodiment.

[0013] As shown in the figure, the container terminal operation system 100 includes an EDI (Electronic Data Interchange) server 5 for linking with external systems, a storage device 4 for storing various data in the container terminal operation system 100, and a client device 3. The client device 3 is a device included in the container terminal operation system 100 that manages cargo handling plans. Details of the cargo handling plans will be described later.

[0014] The container terminal operation system 100 mainly has four functions: VP (Vessel Planning) 11, YP (Yard Planning) 12, YO (Yard Operation) 13, and TGS (Truck Gate System) 14.

[0015] More specifically, VP11 is a function that manages information about the vessel that is the target of container unloading and loading, and the work plan for unloading and loading containers, while taking into consideration the balance of the vessel and the running of the cargo handling equipment. YP12 is a function that manages the container position within the yard (also called a container yard) and the work plan within the yard. YO13 is a function that manages the work instructions and work results for the cargo handling equipment. TGS14 is a function that manages the entry and exit of external trailers at the entrance and exit of the terminal. These functions are realized by executing software on an information processing device, and the client device 3 is an information processing device that realizes the function of VP11 out of the above four functions.

[0016] The cargo handling plan support system 7, which will be described later, includes a server device 2, a client device 3, and a storage device 4, and is configured such that an automatic cargo handling plan calculation function is added to VP11 by the server device 2. This makes it possible to introduce the automatic cargo handling plan calculation function into VP11 with minimal modification to the existing container terminal operation system.

[0017] [About cargo handling plans] The cargo work plan supported by the cargo work plan support system 7 will be described with reference to Fig. 2 and Fig. 3. Fig. 2 is a diagram for explaining an outline of the loading operation. Fig. 3 is a diagram for explaining the cargo loading area on the hull.

[0018] As shown in FIG. 2, a delivery vehicle TR1 carries a shipper's container into a container yard. RTGs (Rubber Tired Gantry Cranes) 1-2 store the carried-in container in the container yard. Next, when the stored container is to be loaded onto a ship 1, the loading capacity of the container on the ship 1 is determined. In addition, work plans for GCs (Gantry Cranes) 1-2, which are cargo handling equipment used in the container handling work, are determined, as well as plans for unloading (also called unloading) the containers already loaded on the ship 1 and loading the stored containers onto the ship 1. The loading capacity plan for determining the loading capacity, the cargo handling equipment work plan, the container unloading plan, and the container loading plan are all cargo handling plans that are supported by the cargo handling plan support system 7, and details of each cargo handling plan will be described later.

[0019] Then, GC1-2 unload the containers loaded onto ship 1 into the container yard in accordance with the determined work plan. RTG1-2 load the unloaded containers onto delivery vehicle TR2, which then carries the containers out. GC1-2 also load the stored containers onto ship 1 in accordance with the determined work plan.

[0020] When unloading and loading containers, GC1-2 move forward and backward (towards the bay) along ship 1 to unload and load the containers. When loading, the work is carried out by moving the work object one by one from the sea side row to the land side row in one bay. When loading containers into each row, the containers are loaded in order starting from the empty space at the bottom.

[0021] FIG. 3 shows a schematic cross section of the vessel 1. More specifically, 301 in FIG. 3 shows a cross section in the xz plane when the fore-and-aft direction of the vessel 1 is the x-axis direction, the left-and-right direction of the vessel 1 is the y-axis direction, and the up-and-down direction is the z-axis direction. Also, 302 in FIG. 3 shows a cross section in the yz plane of the vessel 1. Note that the x-axis direction corresponds to the bay direction described above. Also, the y-axis direction can be rephrased as the row direction, and the z-axis direction can be rephrased as the tier direction.

[0022] As shown in Figure 3, the ship 1 is capable of loading containers both above (on board) and below (i.e., inside the ship) deck D. In Figure 3, multiple rectangles arranged above and below deck D represent unit spaces (hereinafter referred to as cells) for loading cargo. Generally, cargo is loaded into containers, and therefore the following description will be given assuming that containers are loaded into each cell.

[0023] The position of each cell can be expressed by coordinate values ​​(x, y, z). These coordinate values ​​can also be expressed as (bay number, row number, tier number). For example, in the example of Figure 3, the x coordinate (bay number) of the cell located furthest forward in the direction of travel of ship 1 may be set to 1. In this case, the x coordinate (bay number) of cell C1 is expressed as 1. The y coordinate (row number) of the cell located at the leftmost position when looking at ship 1 from the front may be set to 1. In this case, the y coordinate (row number) of cell C1 is expressed as 1. The z coordinate (tier number) of the cell located at the lowest level of the space inside and on the ship that can accommodate containers may be set to 1. In this case, the z coordinate (tier number) of cell C1 is expressed as 5. In other words, the position of cell C1 is expressed as (1, 1, 5).

[0024] Cells with the same bay number can be managed with one bay number. For example, as shown by the dashed rectangle in 301, cells with bay number 1 can be managed as cells of "Bay 1."

[0025] The cargo handling plan in VP11 includes (1) a loading frame plan, (2) a cargo handling equipment operation plan, (3) a discharge plan (a plan for unloading work on land), and (4) a stowage plan (a plan for loading work on a ship). The cargo handling plan in VP11 can also be called a vessel plan.

[0026] (1) In the stowage plan, the stowage slots for containers on the ship 1 are determined. Note that a "stowage slot" refers to the space reserved on the ship 1 for loading containers. Stowage slots are reserved for each attribute of the container. Examples of the container attributes include the container's POD (the port where the container is discharged), the container type, and the container size. Examples of the container type include a container for storing dangerous goods, a refrigerated container, and a special container.

[0027] For example, as in the example in Figure 3, when managing the unit space in which cargo (containers) are loaded as a cell, in the stacking slot plan, for each container group consisting of multiple containers with a common attribute, multiple spatially adjacent cells can be assigned as stacking slots for containers with that attribute. In this case, the stacking slot corresponding to each container group can be expressed by the (x, y, z) coordinates of the cell assigned to that stacking slot, or by a combination of (bay number, tier number, row number).

[0028] Restrictions may be placed on how stacking slots are allocated. For example, stacking slots may be allocated on a bay-by-bay basis. In this case, containers with common attributes are loaded into one bay. It may also be permitted to allocate stacking slots for containers with multiple attributes to one bay. It is also possible to allocate multiple adjacent cells to one large container.

[0029] (2) The cargo handling equipment work plan determines the work of the cargo handling equipment to load containers onto ship 1. For example, GC1 and GC2 shown in Figure 2 are examples of cargo handling equipment. The cargo handling equipment work plan determines, for example, which containers GC1 and GC2 will transport and the order in which they will transport them.

[0030] (3) In the unloading plan, the order in which each container is unloaded from ship 1, that is, the order in which each container loaded on ship 1 is unloaded, is determined.

[0031] (4) The shipping plan determines the order in which each container is loaded onto ship 1, that is, the order in which the containers are loaded onto ship 1.

[0032] [Configuration of cargo handling planning support system] The configuration of the cargo handling plan support system 7 according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the cargo handling plan support system 7. As shown in the figure, the cargo handling plan support system 7 includes a server device 2, a client device 3, and a storage device 4. As explained with reference to Fig. 1, the client device 3 and the storage device 4 are also components of the container terminal operation system 100.

[0033] As described above, the server device 2 is a device for adding an automatic calculation function for cargo handling plans to the VP11. As shown in the figure, the server device 2 includes a server module 21 and a calculation engine 22. The functions of these components can all be realized by software. The calculation engine 22 may be external to the server device 2. Also, a different calculation engine 22 may be used for each type of cargo handling plan.

[0034] As described above, the client device 3 is a device that realizes the functions of the VP 11. As shown in the figure, the client device 3 includes a client module 31 and a user interface 32. The functions of these components can all be realized by software.

[0035] The client module 31 receives an input of a calculation instruction for a cargo handling plan from a user (e.g., a cargo handling planner) of the cargo handling plan support system 7 via the user interface 32. Then, upon receiving the input, the client module 31 transmits a calculation request for the cargo handling plan to the server device 2.

[0036] When inputting calculation instructions for a cargo handling plan, the user can also input calculation conditions for some of the four types of cargo handling plans mentioned above. This ensures flexibility in creating plans through automatic calculation, making it possible to create cargo handling plans that flexibly correspond to the size of the ship 1 and the operating rules of the shipping company or prime contractor.

[0037] When the server module 21 receives a calculation request from the client module 31, it reads data for calculating a cargo handling plan from the storage device 4 and instructs the calculation engine 22 to calculate the cargo handling plan. Details of the data for calculating the cargo handling plan will be described later.

[0038] The calculation engine 22 calculates a cargo handling plan by a mathematical optimization method using the data read from the storage device 4 in accordance with instructions from the server module 21. The calculation engine 22 that calculates a cargo handling plan by a mathematical optimization method may be, for example, a mathematical optimization solver. By applying the mathematical optimization method, it becomes possible to quantitatively evaluate the quality of a cargo handling plan and generate an optimal cargo handling plan. In addition, when calculating a cargo handling plan, it is possible to set constraints in advance, and by setting the constraints, a cargo handling plan that satisfies the constraints is generated.

[0039] It is not necessary to calculate all of the four types of cargo handling plans described above using a mathematical optimization method. In this embodiment, an example will be described in which, of the four types of cargo handling plans described above, (1) loading slot plan and (4) shipping plan are calculated using a mathematical optimization method, and the other cargo handling plans are calculated using other methods (specifically, rule-based). Details of the calculations for the various cargo handling plans will be described later.

[0040] The server module 21 then acquires the cargo handling plan calculated by the calculation engine 22 and transmits the acquired cargo handling plan to the client device 3. As a result, the cargo handling plan is output to an output device (not shown) that is included in the client device 3 or connected to the client device 3. The cargo handling plan may be output in any manner. For example, the cargo handling plan may be displayed, printed, or output as audio. An example of displaying and outputting the cargo handling plan on a display unit (not shown) included in the client device 3 will be described below.

[0041] Furthermore, if the cargo handling plan transmitted to the client device 3 is adopted by the user, the server module 21 stores the cargo handling plan in the storage device 4. In this way, the server module 21 also has the function of registering the calculation results of the calculation engine 22 in the storage device 4. As described above, the server module 21 also has the function of extracting information necessary for the cargo handling plan from the storage device 4 of the container terminal operation system 100. In other words, the server module 21 functions as an interface connecting the user and the container terminal operation system 100.

[0042] As described above, the cargo handling plan support system 7 includes a client device 3, a server device 2, and a storage device 4 that stores data for calculating a cargo handling plan. The cargo handling plan is either (1) a loading slot plan or (4) a shipping plan. The client device 3 includes a client module 31, which receives input of a calculation instruction for the cargo handling plan and, upon receiving the input, sends a calculation request to the server device 2. The server device 2 includes a server module 21 and a calculation engine 22. Upon receiving the calculation request, the server module 21 reads data for calculating the cargo handling plan from the storage device 4 and instructs the calculation engine 22 to calculate the cargo handling plan. The calculation engine 22 then calculates the cargo handling plan using a mathematical optimization method using the read data in accordance with the instruction. This allows the cargo handling plan to be automatically generated. Furthermore, since the work plan calculation function is realized by the server device 2 external to the container terminal operation system 100, modifications to the client devices 3 included in the container terminal operation system 100 to accommodate the automatic generation of cargo handling plans can be minimized. Therefore, with the above configuration, it is possible to realize a cargo handling plan support system that is relatively easy to introduce and is capable of automatically generating cargo handling plans.

[0043] Furthermore, the client module 31 can further (2) request the server device 2 to calculate a work plan for cargo handling equipment. Upon receiving the request, the server module 21 reads data for calculating a work plan for cargo handling equipment from the storage device 4 and instructs the calculation engine 22 to calculate the work plan. Then, as will be described in detail later, the calculation engine 22 calculates the work plan using a rule base in accordance with the instruction, using the read data as input. This achieves faster and more labor-saving work planning for cargo handling equipment.

[0044] Furthermore, the client module 31 can also (3) request the server device 2 to calculate a landing plan. Upon receiving the request, the server module 21 reads data for calculating the landing plan from the storage device 4 and instructs the calculation engine 22 to calculate the landing plan. Then, as will be described in detail later, the calculation engine 22 calculates the landing plan using a rule base in accordance with the instruction, using the read data as input. This allows for faster and more labor-saving landing planning.

[0045] [Regarding constraints] As described above, when inputting calculation instructions for a cargo handling plan, the user can input constraints for the cargo handling plan. For example, the user can input constraints to be used in the optimization calculation for the cargo handling plan ((1) loading slot plan and (4) shipping plan) calculated by the optimization calculation. Hereinafter, the constraints input by the user will be referred to as "first constraints."

[0046] The client module 31 receives input of first constraint conditions for calculating a cargo handling plan via the user interface 32. The client module 31 then transmits the received first constraint conditions to the server device 2. The server module 21 provides the first constraint conditions transmitted from the client module 31 to the calculation engine 22. The calculation engine 22 then calculates a cargo handling plan that satisfies the provided first constraint conditions. This allows the user to generate a cargo handling plan that satisfies the first constraint conditions that the user inputs.

[0047] Furthermore, the data for calculating the cargo handling plan stored in the storage device 4 may include predetermined constraint conditions (hereinafter referred to as second constraint conditions) for calculating the cargo handling plan. In this case, the calculation engine 22 calculates a cargo handling plan that satisfies the second constraint conditions. In other words, the cargo handling plan support system 7 can generate a cargo handling plan that satisfies the second constraint conditions by storing the second constraint conditions in the storage device 4 in advance. For example, constraint conditions that cannot be changed by the user can be stored in the storage device 4 as second constraint conditions.

[0048] Furthermore, when the second constraint condition is stored in the storage device 4 and the first constraint condition is input, the calculation engine 22 calculates a cargo handling plan that satisfies both the first constraint condition and the second constraint condition. This makes it possible to generate a cargo handling plan that satisfies both the second constraint condition stored in advance and the first constraint condition input by the user.

[0049] It should be noted that, depending on the constraint conditions used and the calculation performance of the calculation engine 22, there may be a certain amount of waiting time from the start of the optimization calculation until the loading and unloading plan is calculated and presented to the user. For this reason, after transmitting a calculation request to the calculation engine 22, the server module 21 may obtain information indicating the progress of the calculation of the loading and unloading plan from the calculation engine 22. Then, the server module 21 may transmit the obtained information indicating the progress to the client device 3.

[0050] As a result, the client module 31 receives the information and displays the progress status on the display unit based on the information, allowing the user to recognize the progress status of the calculation. The display mode of the progress status is not particularly limited as long as it allows the user to recognize the progress status. For example, the client module 31 may display the progress status as a numerical value between 0% and 100%, with the progress status at the start of the calculation being 0% and the progress status at the completion of the calculation being 100%. Furthermore, if the calculation by the calculation engine 22 is unsuccessful, the server module 21 may transmit information indicating the error content to the client device 3. As a result, the client module 31 receives the information and displays the error content on the display unit based on the information, allowing the user to recognize the error content.

[0051] [Regarding cargo handling planning sequence] The cargo handling plan support system 7 can calculate each of the four types of cargo handling plans described above independently. For example, the user can (1) apply the loading quota plan indicated in the center plan notified by the shipping company without having the cargo handling plan support system 7 calculate the (2) cargo handling equipment work plan.

[0052] However, as mentioned above, the four types of cargo handling plans are executed in numerical order, and the contents of a cargo handling plan that is executed earlier and stored in the storage device 4 may affect the cargo handling plans that are executed later. For this reason, it is preferable to store the cargo handling plans in the storage device 4 in the following order:

[0053] For example, suppose that the server module 21 stores the stacking frame plan in the storage device 4 in response to the client module 31 receiving an input indicating the adoption of the (1) stacking frame plan calculated by the calculation engine 22. In this case, it is preferable to have the calculation engine 22 calculate the (2) cargo handling equipment work plan after the stacking frame plan is stored in the storage device 4. Then, it is preferable that the server module 21 stores the work plan in the storage device 4 in response to the client module 31 receiving an input indicating the adoption of the (2) cargo handling equipment work plan calculated by the calculation engine 22.

[0054] Furthermore, when (2) the work plan for the cargo handling equipment is stored in the storage device 4, it is preferable to have the calculation engine 22 calculate (4) the shipping plan after the work plan is stored in the storage device 4. Then, it is preferable that the server module 21 stores the shipping plan in the storage device 4 in response to the client module 31 receiving an input indicating the adoption of the (4) shipping plan calculated by the calculation engine 22.

[0055] According to the above configuration, the calculation results of a previously executed cargo handling plan can be reflected in the calculations of subsequent cargo handling plans, thereby making it possible to obtain appropriate calculation results for each cargo handling plan.

[0056] Furthermore, the cargo handling plan support system 7 may accept user corrections to the cargo handling plan calculated by the calculation engine 22 and stored in the storage device 4. In this way, by providing a function for manually adjusting the cargo handling plan rather than relying on completely automatic calculation, it becomes possible to create a cargo handling plan that meets the user's intentions down to the smallest detail. It also becomes possible to deal with irregular situations such as the shipping company specifying the actual loading location. However, if corrections are accepted, it is possible that corrections that will affect subsequent cargo handling plans will be made. When a correction that will affect subsequent cargo handling plans is accepted, it is preferable to process it as follows.

[0057] That is, in response to receiving an input indicating the adoption of the (1) stacking frame plan calculated by the calculation engine 22, the client module 31 may read out the stacking frame plan stored in the storage device 4 by the server module 21. Then, the client module 31 may receive an input to modify the information included in the read stacking frame plan, and store the modified stacking frame plan in the storage device 4. The process of storing the modified stacking frame plan in the storage device 4 may be performed directly by the client module 31, or may be performed by the server device 2.

[0058] In this case, it is preferable that the calculation engine 22 uses data read from the storage device 4 in which the corrected loading quota plan is stored when calculating the (2) cargo handling equipment work plan and the (4) shipping plan. This allows the contents of the corrected (1) loading quota plan to be reflected in the calculation of the (2) cargo handling equipment work plan and the (4) shipping plan.

[0059] Furthermore, in response to receiving an input indicating the adoption of the (2) cargo handling equipment work plan calculated by the calculation engine 22, the client module 31 may read out the work plan stored in the storage device 4 by the server module 21. Then, the client module 31 may receive an input to modify the information included in the read out work plan, and store the modified work plan in the storage device 4. The process of storing the modified work plan in the storage device 4 may be performed directly by the client module 31, or may be performed by the server device 2.

[0060] In this case, it is preferable that the calculation engine 22 uses data read from the storage device 4 in which the modified (2) cargo handling equipment work plan is stored when calculating the (4) shipping plan. This allows the contents of the modified (2) cargo handling equipment work plan to be reflected in the calculation of the (4) shipping plan.

[0061] (1) Loading Plan (Presentation of calculation results) The presentation of the stacking frame plan calculated by the calculation engine 22 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of a UI (user interface) screen that presents the stacking frame plan calculated by the calculation engine 22. The UI screen 500 shown in Fig. 5 shows the arrangement of cells in a cross section of the ship 1 in the yz plane, in other words, the arrangement of each cell in the row direction (y-axis direction) and tier direction (z-axis direction) for each bay.

[0062] In this UI screen 500, the display mode of each cell indicates the calculation result of the stacking quota plan. Note that a cell with an "X" displayed (for example, cell 501) is a cell that is not subject to the stacking quota plan. Such a cell can be defined in advance in the storage device 4, or can be set by the user.

[0063] More specifically, the UI screen 500 indicates the POD (port of discharge of the container to be loaded at the location of that cell) of that cell by the fill pattern that fills the cell. By displaying such a display screen, the client module 31 allows the user to check at a glance whether an appropriate stacking quota is set in the calculated stacking quota plan. As described above, attribute information such as the type and size of the container is also taken into consideration in the stacking quota plan. Therefore, the type and size of the container may also be displayed. Furthermore, the display color of each cell may indicate the POD or the type or size of the container.

[0064] The UI screen 500 also displays an adopt button B1 labeled "Adopt" and a restore button B2 labeled "Restore." The adopt button B1 is a button used when adopting the stacking quota plan displayed on the UI screen 500. When the user performs an operation to select the adopt button B1, the client module 31 instructs the storage device 4 to register the stacking quota plan.

[0065] On the other hand, the restore button B2 is a button used when discarding the stacking quota plan shown on the UI screen 500. When the user performs an operation to select the restore button B2, the client module 31 does not send a registration instruction for the stacking quota plan, and as a result, the stacking quota plan is not registered in the storage device 4.

[0066] When the restore button B2 is selected, if a stacking quota plan calculated previously is stored in the storage device 4, the client module 31 may display that stacking quota plan. Also, if a center plan notified by the shipping company is stored in the storage device 4, the client module 31 may display the stacking quota plan shown in that center plan.

[0067] The UI screen 500 can also be used as a UI for accepting modifications to the stacking slot plan calculated by the calculation engine 22. That is, the client module 31 may accept modifications to the stacking slot plan via the UI screen 500. For example, the client module 31 may accept a user operation (for example, a right click of the mouse) on a cell on the UI screen 500 that indicates that a container should be loaded (a cell filled with a predetermined pattern) as an operation to modify the cell so that a container is not loaded therein. Also, for example, the client module 31 may accept a user operation (for example, a left click of the mouse) on a cell on the UI screen 500 that indicates that a container should not be loaded therein (a white cell) as an operation to modify the cell so that a container is loaded therein. In this case, the client module 31 may display a screen for accepting input of attribute information, such as the POD, type, and size of the container to be loaded in the cell, before or after the operation.

[0068] (Input data for the framework plan) FIG. 6 is a diagram showing an example of input data used in the optimization calculation of the stacking slot plan. Some or all of this input data may be stored in advance in the storage device 4, or may be input by the user via the client device 3. The server module 21 acquires the information shown in FIG. 6 as input data required for creating the stacking slot plan. For example, the server module 21 acquires the number of the bay (CBC) located at the center in the fore-aft direction of the ship 1, the number of empty cells in the tier direction (CT) of the row number r of bay number b, and the number of empty cells in the tier direction (CT). br ), the number of containers to be loaded with port d as the destination (CL d ), the upper limit of the container weight that can be loaded into Bay number b and Row number r (CWM br ), the average weight of containers destined for port d (CWA d ), the weight of the container already loaded in Bay number b, Row number r, Tier number t (CWS brt ), the upper limit of the number of Rows that Bay number b has that can be used for containers destined for port d (CRL bd ), the upper limit of the number of destination ports for containers loaded in Bay number b and Row number r (CDL bd ), the upper limit of the number of bays that can load containers destined for port d (CBL d ), a value indicating how far forward the center of gravity of vessel 1 should be placed from the center to ensure visibility (CB bias ) and so on. The server module 21 transmits the acquired input data to the calculation engine 22.

[0069] (Variables in framework planning) 7 is a diagram showing an example of variables used in the optimization calculation of the stacking frame plan. The calculation engine 22 performs the optimization calculation of the stacking frame plan, which will be described later, and calculates the variables VX brd , V.Y. brd , V.Y. db Calculate the optimal value of variable VX brd represents the number of containers destined for port d and loaded onto row number r of bay number b. brdis a variable that indicates whether or not a container destined for port d is loaded in row number r of bay number b. db is a variable that indicates whether or not a container destined for port d is loaded at bay number b.

[0070] In addition, although not shown in the figure, variables OB1 to OB4 related to the center of gravity balance of the vessel 1 are prepared. OB1 is a variable that represents the distance from the ideal position of the center of gravity of the vessel 1 to the position of the center of gravity when the center of gravity is shifted forward. OB2 is a variable that represents the distance from the ideal position of the center of gravity of the vessel 1 to the position of the center of gravity when the center of gravity is shifted rearward. OB3 is a variable that represents the distance from the ideal position of the center of gravity of the vessel 1 to the position of the center of gravity when the center of gravity is shifted leftward. OB4 is a variable that represents the distance from the ideal position of the center of gravity of the vessel 1 to the position of the center of gravity when the center of gravity is shifted rightward.

[0071] (Constraints in the budget plan) Constraint conditions that can be applied in optimization calculation of a stacking slot plan will be described with reference to Fig. 8 and Fig. 9. Fig. 8 and Fig. 9 are diagrams showing examples of constraint conditions for a stacking slot plan.

[0072] For example, the following constraints (1) to (4) are set as constraints regarding the structure of the ship 1. (1) An upper limit is set for the number of rows in each bay. This constraint can be expressed by the constraint equation (a1) in Figure 8. By the constraint equation (a1), the variable VY brd and the variable VY bd Define the relationship. (2) An upper limit is set for the number of tiers in each bay and each row. This constraint can be expressed by constraint equation (a2) in Figure 8. By constraint equation (a2), the variable VX brd and the variable VY brd Define the relationship. (3) In each bay and row, the number of containers bound for a particular port cannot exceed the number of available tiers. This constraint can be expressed by constraint formula (a3) ​​in Figure 8. (4) Containers cannot be loaded onto each bay or row exceeding a certain weight limit. This constraint can be expressed by constraint formula (a4) in FIG.

[0073] For example, based on the experience of a planner of a loading slot plan who is a user of the cargo handling plan support system 7, the following constraints (5) to (7) are set. (5) Containers bound for one port of call are loaded into a certain number of bays at most. This constraint can be expressed by constraint formula (a5) in Figure 8. (6) Containers bound for one port of call are loaded into at most a certain number of rows within one bay. This constraint can be expressed by constraint formula (a6) in Figure 8. (7) Each bay and each row can only carry a certain number of containers bound for the port of call. This constraint can be expressed by constraint equation (a7) in Figure 8.

[0074] For example, the following constraint (8) is set as a requirement regarding containers to be loaded onto the ship 1. (8) For all ports of call d, all containers to be loaded are loaded onto ship 1. This constraint can be expressed by constraint formula (a8) in FIG.

[0075] For example, the following constraints (9) to (12) are set regarding the balance of the center of gravity of the vessel 1. (9) The distance by which the center of gravity shifts forward from the center in the longitudinal direction (number of containers) does not exceed variable OB1. This constraint can be expressed by constraint formula (a9) in FIG. (10) The distance (number of containers) by which the center of gravity shifts backward from the center in the longitudinal direction does not exceed variable OB2. This constraint can be expressed by constraint formula (a10) in FIG. (11) The distance (number of containers) by which the center of gravity is shifted to the left from the center in the horizontal direction does not exceed variable OB3. This constraint can be expressed by constraint formula (a11) in FIG. (12) The distance (number of containers) by which the center of gravity shifts to the right from the center in the left-right direction does not exceed variable OB4. This constraint can be expressed by constraint formula (a12) in FIG.

[0076] The variables OB1 to OB4 are optimized using an objective function, which will be described later.

[0077] (Objective function in frame planning) Fig. 10 is a diagram showing an example of an objective function of a stacking frame plan. Prior to the optimization calculation of the stacking frame plan by the calculation engine 22, an objective function constituted by formulas (b1) to (b3) shown in Fig. 10 is set. The objective function is set, for example, by the following formula (c1).

[0078] Objective function: (b1) + (b2) + (b3) (c1) Equation (b1) is a formula for improving the efficiency of gantry cranes (cargo handling equipment, for example GC1 and 2 in Figure 2). Ship 1 is moored with the side of its hull alongside the land, and the gantry crane loads containers onto ship 1 while moving in the fore-and-aft direction of ship 1 (bay direction). Here, it is desirable to minimize the movement of the gantry crane in the bay direction as much as possible from the perspective of power energy and movement time. The relationship between the actual amount of movement of the gantry crane and the number of bays used depends on how many gantry cranes are used for loading and unloading work, but it is thought that reducing the number of bays used will contribute to reducing the amount of movement of the gantry crane. Equation (b1) is expressed as the weight W b and the number of Bays used (variable VY bd ) The goal is to minimize the number of Bays used by performing optimization calculations that minimize the objective function.

[0079] Formula (b2) is a formula for moving the center of gravity in the front-back direction as close as possible to the ideal center of gravity position. Formula (b3) is a formula for moving the center of gravity in the left-right direction as close as possible to the ideal center of gravity position. However, the weight W b1 , W b2 , W b3 By appropriately setting the center of gravity, the center of gravity can be adjusted to a desired position.

[0080] The calculation engine 22 calculates the variables VX such that the value of the objective function expressed by the formula (c1) is minimized.brd , V.Y. brd , V.Y. bd Calculate.

[0081] (2) Work plan for cargo handling equipment (Accepting input data) A user may input some or all of the input data for causing calculation engine 22 to calculate the work plan for the cargo handling equipment. In this case, client module 31 may, for example, display a predetermined UI screen on the display unit to accept the input of the input data. Fig. 11 is a diagram showing an example of a UI screen for accepting the input of input data for calculating the work plan for the cargo handling equipment.

[0082] The UI screen 110 shown in FIG. 11 includes radio buttons 111 and 112 for the "sequence of loading and unloading operations." Radio button 111 is used to specify "unload all bays first, then load." When the user wants to calculate a work plan for cargo handling equipment with "unload all bays first, then load" as the first constraint, the user operates radio button 111 to select it. Radio button 111 is selected on the UI screen 110. Note that "unload all bays first, then load" means that containers are loaded after unloading has been completed for all bays.

[0083] On the other hand, radio button 112 is used to specify "repeated unloading and loading on a bay-by-bay basis." If the user wants to calculate a work plan for cargo handling equipment with "repeated unloading and loading on a bay-by-bay basis" as the first constraint, the user can operate radio button 112. Note that "repeated unloading and loading on a bay-by-bay basis" means that after unloading and loading containers for one bay, the process of unloading and loading containers for the next bay is repeated.

[0084] Furthermore, UI screen 110 includes input boxes 113 and 114 for inputting the initial position of each piece of cargo handling equipment, in other words, the cargo handling operation start position of each piece of cargo handling equipment. For example, input box 113 may be for inputting the initial position of GC1 shown in Fig. 2, and input box 114 may be for inputting the initial position of GC2 shown in Fig. 2. Note that it is sufficient to display the same number of input boxes for inputting initial positions as the number of cargo handling equipment.

[0085] The UI screen 110 also includes an input box 115 for inputting the safety interval between the cargo handling equipment, in other words, the minimum interval between the cargo handling equipment. For example, the input box 115 may be for inputting the safety interval between GC1 and GC2 shown in Fig. 2. Note that when only one piece of cargo handling equipment is used, it is not necessary to display the input box 115.

[0086] The UI screen 110 also displays a start button B3 for starting calculation of the work plan for the cargo handling equipment, and a stop button B4 for stopping input of input data. When the start button B3 is operated after input to the UI screen 110, the client module 31 transmits the input content to the server device 2 as a first constraint and starts calculation. On the other hand, when the stop button B4 is operated, the first constraint is not transmitted.

[0087] As described above, the client module 31 may receive input of at least one of the order of container loading and unloading operations, the operation start position of the cargo handling equipment, and the minimum interval between cargo handling equipment units as first constraint conditions for calculating the cargo handling equipment operation plan. When receiving input of such data, the client module 31 transmits the received first constraint conditions to the server device 2. The server module 21 provides the first constraint conditions transmitted from the client module 31 to the calculation engine 22, and the calculation engine 22 calculates an operation plan that satisfies the provided first constraint conditions. This makes it possible to generate an operation plan for cargo handling equipment that satisfies the first constraint conditions input by the user.

[0088] (Presentation of calculation results) The presentation of the work plan for the cargo handling equipment calculated by the calculation engine 22 will be described with reference to Fig. 12. Fig. 12 is a diagram showing an example of a UI screen that presents the work plan for the cargo handling equipment. The UI screen 120 shown in Fig. 12 shows the work order at each work position for each piece of cargo handling equipment. Specifically, the UI screen 120 shows that GC1 will work first at work position "17D", second at work position "17H", and third at work position "19D".

[0089] Note that the numbers in the combination of numbers and letters indicating the work position indicate the bay number. The letter "D" indicates a position on deck D, and "H" indicates a position in the hold (below the deck). Note that the functions of the adopt button B1 and restore button B2 are the same as those in the example of FIG. 5, and therefore will not be described again. The same applies to the explanations of FIGS. 13 and 15 described below.

[0090] The UI screen 120 can also be used as a UI for accepting modifications to the work plan for the cargo handling equipment calculated by the calculation engine 22. That is, the client module 31 may accept modifications to the work plan for the cargo handling equipment via the UI screen 120. For example, the client module 31 may accept a user operation (for example, a right click of the mouse) on a cell on the UI screen 120 displaying a numerical value indicating the work order as an operation to delete the numerical value displayed in the cell. Also, for example, the client module 31 may accept a user operation (for example, a left click of the mouse) on a cell on the UI screen 120 where a numerical value is not displayed, among the input cells indicating the work order, and may display a screen displaying a list of numerical values ​​that can be input into that cell (i.e., numerical values ​​indicating the work order for which assignment has not been determined) before or after the user operation. The client module 31 may then assign a numerical value selected by the user from the listed numerical values ​​to that cell. This allows the user to modify the work plan for the cargo handling equipment to the desired content with a simple operation.

[0091] (Calculation method) Any method can be used to calculate the work plan for the cargo handling equipment. For example, the calculation engine 22 may generate the work plan for the cargo handling equipment by optimization calculation, but here we will explain an example in which the work plan for the cargo handling equipment is generated based on a rule base.

[0092] When generating a work plan for cargo handling equipment, the calculation engine 22 uses predetermined constraints, such as the number of available cargo handling equipment, in addition to the various constraints that can be input or modified by the user as described above, to generate multiple work patterns for cargo handling equipment that satisfy those constraints.The calculation engine 22 then evaluates each of the generated work patterns and determines the work pattern with the best evaluation result as the optimal work plan for the cargo handling equipment.In other words, the rule base used here generates multiple work patterns for cargo handling equipment that satisfy the constraints, and determines the work pattern with the best evaluation result as the optimal work plan for the cargo handling equipment.

[0093] The evaluation criteria are not particularly limited. For example, the calculation engine 22 may evaluate the work pattern based on the loading and unloading time required to perform each task shown in the work pattern. This makes it possible to generate a work plan that enables loading and unloading tasks to be completed in the shortest possible time.

[0094] (3) Unloading plan (Presentation of calculation results) The presentation of the landing plan calculated by the calculation engine 22 will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of a UI screen for presenting the landing plan. As with the UI screen 500 in Fig. 5, the UI screen 130 shown in Fig. 13 shows the arrangement of cells in a cross section of the ship 1 in the yz plane, in other words, the arrangement of each cell in the row direction (y-axis direction) and tier direction (z-axis direction) for each bay.

[0095] On the UI screen 130, the numerical value displayed in each cell indicates the calculation result of the unloading plan, in other words, the order in which unloading will be performed. For example, the numerical value "1" is displayed in cell 131. This numerical value indicates that the container placed in that cell is the first container to be unloaded. Note that cells with an "X" displayed are cells that are not included in the unloading plan. Such cells can be defined in advance in the storage device 4, or can be set by the user.

[0096] When presenting the generated landing plan, various information that can be used as reference for the user to determine the suitability of the landing plan may be displayed. For example, the client module 31 may display each cell with a color or a fill pattern according to attribute information such as the size or type of the container to be placed in that cell. In addition, for example, the client module 31 may display, for each cell, a number indicating the landing order of the container to be placed in that cell, as well as information indicating the cargo handling equipment (e.g., G1 or G2 shown in FIG. 2) to be used when landing that container.

[0097] The UI screen 130 can also be used as a UI for accepting modifications to the landing plan calculated by the calculation engine 22. That is, the client module 31 may accept modifications to the landing plan via the UI screen 130.

[0098] For example, the client module 31 may receive a specification of a stacking frame to be modified on the UI screen 130 and display a new UI screen for modifying the unloading order for the stacking frame. This new UI screen may display each cell included in the specified stacking frame and a numerical value indicating the unloading order for each cell.

[0099] The client module 31 may then accept a user operation (for example, right-clicking the mouse) on a cell in which a numerical value is displayed as an operation to delete the numerical value displayed in that cell. The client module 31 may also accept a user operation (for example, left-clicking the mouse) on a cell in which no numerical value is displayed, and may display a screen displaying a list of numerical values ​​that can be input into that cell (i.e., numerical values ​​indicating work orders for which allocation has not been determined) before or after that operation. The client module 31 may then assign a numerical value selected by the user from the listed numerical values ​​to that cell.

[0100] (Calculation method) The calculation method for the landing plan is arbitrary. For example, the calculation engine 22 may generate the landing plan by optimization calculation, but here, an example in which the landing plan is generated based on a rule base will be described.

[0101] When generating a landing plan, the calculation engine 22 uses various constraints related to the landing plan to generate multiple work patterns for the landing plan that satisfy those constraints.The calculation engine 22 then evaluates each of the generated work patterns and determines the work pattern with the best evaluation result as the optimal landing plan.In other words, the rule base used here generates multiple work patterns for the landing plan that satisfy the constraints, and determines the work pattern with the best evaluation result as the optimal landing plan.

[0102] The evaluation criteria are not particularly limited. For example, the calculation engine 22 may evaluate the work pattern based on the loading and unloading time required to perform each task shown in the work pattern. This makes it possible to generate an unloading plan that enables loading and unloading work to be completed in the shortest possible time.

[0103] (4) Shipping Plan (Accepting input data) A user may input some or all of the input data for causing the calculation engine 22 to calculate the shipping plan. In this case, the client module 31 may, for example, display a predetermined UI screen on the display unit to accept the input of the input data. Fig. 14 is a diagram showing an example of a UI screen for accepting the input of input data for calculating the shipping plan.

[0104] The UI screen 140 shown in Fig. 14 includes radio buttons 141 and 142 for the "ideal position of the center of gravity of the vessel." Radio button 141 is for specifying the "center of gravity at the time of entry into port." If the user wants to calculate a shipping plan with the first constraint being to approximate the center of gravity of the loaded containers at the time of entry into port of the vessel 1, the user can operate radio button 141 to select it.

[0105] The center of gravity of the ship 1 can also be set based on the distance from the "structural center" of the ship 1. The structural center refers to the center of gravity when it is assumed that the same containers are loaded in all stacking frames. In this case, the user operates the radio button 142 to select it. The position of the center of gravity can also be shifted in the front-to-back and up-to-down directions by entering desired numerical values ​​in the input boxes 143 and 144 at a rate corresponding to the numerical values. When the position of the center of gravity is shifted, the shifted position of the center of gravity is reflected on the illustration of the ship 1 on the UI screen 140.

[0106] The UI screen 140 also includes an item called "Yard Handling Efficiency" that accepts input of first constraints related to various items related to the handling efficiency in the yard. This item includes three sub-items: "Reduce Number of Transfers," "Avoid Interference," and "Allow Work in the Same Bay," and each sub-item is associated with check boxes 145 to 147. A slider 148 is also associated with the sub-item "Reduce Number of Transfers."

[0107] For example, when setting the degree of reduction in the number of handovers as the first constraint, the user checks the checkbox 145 and specifies the degree of reduction in the number of handovers using the slider 148. Handover refers to the operation of moving a container in order to transport a container located below the container.

[0108] In addition, check box 146 associated with the sub-item "Avoid Interference" is used to specify whether or not to avoid interference between yard loading / unloading equipment (for example, RTG1-2 shown in Figure 2) that performs loading / unloading work in the yard.

[0109] Also, check box 147 associated with the sub-item "Work allowed in the same bay" is for specifying whether or not multiple yard handling devices are allowed to work in the same bay in the yard. Note that the start button B3 and the stop button B4 are the same as in the example of Figure 11, so their explanation will not be repeated here.

[0110] As described above, the client module 31 may accept input of at least one of the following first constraints for the stowage plan: the center of gravity position of the ship, the degree to which the number of handling operations in the yard is reduced, whether or not interference between yard handling equipment performing cargo handling operations in the yard is avoided, and whether or not multiple yard handling equipment are allowed to operate in the same bay. When the client module 31 accepts the first constraints, it transmits the accepted first constraints to the server device 2. In this case, the calculation engine 22 calculates a stowage plan that satisfies the first constraints. This makes it possible to generate a stowage plan that satisfies the first constraints entered by the user.

[0111] (Presentation of calculation results) The presentation of a shipping plan calculated by the calculation engine 22 will be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of a UI screen presenting a shipping plan. As with the UI screen 500 of Fig. 5, the UI screen 150 shown in Fig. 15 shows the arrangement of cells in a cross section of the ship 1 in the yz plane, in other words, the arrangement of each cell in the row direction (y-axis direction) and tier direction (z-axis direction) for each bay. The UI screen 150 also shows the arrangement of cells in the yard in a similar manner.

[0112] On the UI screen 150, the numerical value displayed in each cell indicates the calculation result of the stowage plan, in other words, the order in which the stowage will be performed. For example, the numerical value "1" is displayed in cell 151 for ship 1 and cell 152 for the yard. This numerical value indicates that the first task to be performed is to load the container placed in cell 152 in the yard to the position of cell 151 on ship 1. Note that cells with an "X" displayed are cells that are not included in the stowage plan. Such cells can be defined in advance in the storage device 4 or can be set by the user.

[0113] When presenting the generated shipping plan, various information that can be used as a reference for the user to determine the appropriateness of the shipping plan may be displayed. For example, the client module 31 may display each cell with a color or a fill pattern according to attribute information such as the POD, size, or type of the container to be placed in that cell. In addition, for example, the client module 31 may display, for each cell, a number indicating the loading order of the container to be placed in that cell, as well as information indicating the cargo handling equipment (e.g., RTG1 or RTG2 shown in FIG. 2) to be used when loading the container.

[0114] The UI screen 150 can also be used as a UI for accepting modifications to the shipping plan calculated by the calculation engine 22. That is, the client module 31 may accept modifications to the shipping plan via the UI screen 150.

[0115] For example, the client module 31 may accept a user operation (for example, a right click of the mouse) on a cell in the UI screen 150 that displays a numerical value indicating the loading order for the ship 1 as an operation to delete the numerical value. Also, for example, the client module 31 may accept a user operation (for example, a left click of the mouse) on a cell in the UI screen 150 that does not display a numerical value (a white cell) as an operation to set the loading order for that cell. In this case, the client module 31 may display a screen that accepts input of a numerical value specifying the loading order for that cell before or after the operation.

[0116] (Input data for shipping plans) Input data for a shipping plan will be described with reference to Figures 16 to 18. Figure 16 is a diagram showing an example of input data for a shipping plan. Figure 17 is a diagram showing an example of the type of containers to be loaded, and Figure 18 is a diagram showing an example of input data related to containers.

[0117] 16 and 18 may be stored in advance in the storage device 4, or may be input by a user via the client device 3. The server module 21 acquires the information exemplified in FIGS. 16 and 18 as input data required to create a shipping plan.

[0118] With reference to FIG. 16, for example, the server module 21 may obtain the weight (CWS) of a container already loaded at a location with coordinates x, y, and z (corresponding to Bay, Row, and Tier, respectively). xyz ), the weight of container i destined for port d (CWL di ), x coordinate (CXC) representing the center of gravity in the front-to-back direction (bay direction) when vessel 1 enters port, y coordinate (CYC) representing the center of gravity in the left-to-right direction (row direction) when vessel 1 enters port, z coordinate (CZC) representing the center of gravity in the top-to-bottom direction (tier direction) when vessel 1 enters port, and the upper limit of the weight of the container that can be loaded in the bay and row of coordinates x and y (CWM xy ), the range in which vessel 1 can load containers destined for port d (the set of locations x, y, and z) (CDd ), a value indicating how far forward the center of gravity of the vessel 1 is to be shifted from the center (CXbias), a value indicating how far to the right the center of gravity of the vessel 1 is to be shifted from the center (CYbias), and a value indicating how far upward the center of gravity of the vessel 1 is to be shifted from the center (CZbias). In addition to this, the server module 21 acquires basic information about the containers to be loaded, such as the ports of call, the number of containers per port of call and the weight of each container, the storage location of the containers to be loaded, the number of cargo handling equipment to be loaded, and the working range of each cargo handling equipment (range of bay numbers).

[0119] As shown in Figure 17, there are various types of containers that can be loaded, including 1) containers requiring power supply equipment, 2) cargo that does not fit into a general dry container (OOG), 3) dangerous goods, 4) containers with designated loading locations such as above or below deck, and 5) dry containers (general containers). 1) Containers requiring power supply equipment must be loaded in a location where power supply equipment can be installed. 2) OOG cargo is subject to restrictions such as being loaded in the top location (external storage) and not being placed next to other containers on either side (internal storage). 3) Dangerous goods are subject to restrictions such as spacing, being away from heat sources, and being away from living quarters. Containers in category 4) must be loaded in a location designated by whether they are placed below deck (Hold designation) or above deck (Deck designation), while containers in category 5) can be loaded in any available location.

[0120] 17, the input data illustrated in FIG. 18 can be used. For example, the server module 21 may select a set of locations with power (CRr), a set of locations on the top floor of a tier (COo), a set of locations on the inside (empty on both sides) (COi), a set of locations where dangerous goods can be placed (CDg), a minimum distance (CDgD) that should be maintained between containers containing dangerous goods type number p and dangerous goods type number q, and a set of locations where dangerous goods can be placed (CDgD). pq), the set of below-deck locations (CHo), the set of above-deck locations (CHe), the x- and y-coordinates of the location where the shift container (a container that needs to be temporarily moved for loading containers) was loaded at the time of port entry (CShX di , C.Sh.Y. di ) Whether container i destined for port d is a refrigerated container or not (CRr di ), whether container i destined for port d is an outside-of-garbage container (COo di ), whether container i destined for port d is an inside OOG container (COi di ), the dangerous goods type number (CDg) of the dangerous goods container of container i destined for port d di ), whether container i destined for port d is a hold designated container (CHo di ), whether container i destined for port d is a deck-designated container (CDe di ), whether container i destined for port d is a shift container or not (CSh di The server module 21 transmits the acquired input data to the calculation engine 22.

[0121] (Variables in Shipment Planning) 19 is a diagram showing an example of variables used in the optimization calculation of the shipping plan. The calculation engine 22 performs the optimization calculation of the shipping plan, which will be described later, and calculates the variables VL shown in FIG. dixyz Calculate the optimal value of the variable VL dixyz is a variable that indicates whether or not container i destined for port d is loaded at the location of coordinates x, y, z.

[0122] Furthermore, although not shown in the figure, variables OX, OY, and OZ related to the center of gravity balance of the vessel 1 are prepared. The variable OX is a variable that represents the distance in the fore-and-aft direction between the center of gravity of the vessel 1 and the ideal center of gravity position. The variable OY is a variable that represents the distance in the left-and-right direction between the center of gravity of the vessel 1 and the ideal center of gravity position. The variable OZ is a variable that represents the distance in the up-and-down direction between the center of gravity of the vessel 1 and the ideal center of gravity position.

[0123] (Constraints on shipping plans) Constraints that can be applied in the optimization calculation of a shipping plan will be explained with reference to Figures 20 and 21. Figures 20 and 21 are diagrams showing examples of constraints for a shipping plan. For example, the following constraint (1) is set as a constraint on the structure of the ship 1. (1) No containers exceeding the upper weight limit may be placed within the range defined by one bay and row. This constraint can be expressed by constraint formula (a1) in FIG.

[0124] For example, the following constraints (2) and (3) are set as constraints regarding the loading request to the ship 1. (2) One container bound for each port of call is loaded at one location. This constraint can be expressed by constraint formula (a2) in Figure 20. (3) Load one container at each location specified in the center plan (a plan instructed by the shipping company to specify the loading locations of containers). This constraint can be expressed by constraint formula (a3) ​​in Figure 20.

[0125] For example, the following constraints (4) to (9) are set regarding the balance of the center of gravity of the vessel 1. (4) The distance by which the center of gravity deviates forward from the center in the longitudinal direction does not exceed OX. This constraint can be expressed by constraint formula (a4) in FIG. (5) The distance that the center of gravity shifts rearward from the center in the fore-and-aft direction does not exceed OX. This constraint can be expressed by constraint formula (a5) in FIG. (6) The distance by which the center of gravity deviates from the center in the left-right direction to the left does not exceed OY. This constraint can be expressed by constraint formula (a6) in FIG. (7) The distance by which the center of gravity deviates from the center in the left-right direction to the right does not exceed OY. This constraint can be expressed by constraint equation (a7) in FIG. (8) The distance by which the center of gravity is shifted upward from the center in the vertical direction does not exceed OZ. This constraint can be expressed by constraint formula (a8) in FIG. (9) The distance by which the center of gravity is shifted downward from the center in the vertical direction does not exceed OZ. This constraint can be expressed by constraint formula (a9) in FIG.

[0126] For example, the following constraints (10) to (17) are set for the special containers to be loaded onto the ship 1. (10) Containers that require power are loaded in locations with power. This constraint can be expressed by constraint equation (a10) in Figure 21. (11) OOG containers designated for external storage are loaded on the top tier. This constraint can be expressed by constraint formula (a11) in FIG. (12) An OOG container specified for inner placement is surrounded by other containers on three sides (top, left, right). This constraint can be expressed by constraint formula (a12) in FIG. (13) Hazardous items are spaced apart by a fixed distance m. This constraint can be expressed by constraint equation (a13) in Figure 21. (14) Hazardous items should not be placed near heat sources such as the main engine or auxiliary boilers. This constraint can be expressed by constraint equation (a14) in Figure 21. (15) After a temporary movement, the shift container is returned to the same bay and row as the location where it was originally loaded. This constraint can be expressed by constraint formula (a15) in FIG. (16) Containers designated for Hold are placed on the tier below the deck. This constraint can be expressed by constraint formula (a16) in FIG. (17) Deck-specified containers are placed on the upper tier of the deck. This constraint can be expressed by constraint formula (a17) in FIG.

[0127] (Objective function in shipping planning) Figures 22 and 23 are diagrams showing examples of objective functions for a shipping plan. Prior to the optimization calculation of a shipping plan by the calculation engine 22, an objective function composed of equations (b1) to (b8) shown in Figures 22 and 23 is set. The objective function is set, for example, by the following equation (c1).

[0128] Objective function: (b1) + (b2) + (b3) + W rtg2 ×Formula (b4)+W rg3 ×Formula (b5)+W rtg4 ×Formula (b6)+W rtg5 ×Formula (b7)+W rtg6 ×Formula (b8)...(c1) Equations (b1) to (b3) in FIG. 8A are equations for bringing the center of gravity of the vessel 1 as close as possible to the ideal center of gravity position (for example, the center of gravity position when entering port). By appropriately adjusting the center of gravity of the vessel 1, it is possible to expect effects such as maintaining the balance of the vessel 1, ensuring visibility, facilitating acceleration, stabilizing the hull, and reducing rolling. Equation (b1) is an equation for bringing the longitudinal position of the center of gravity of the vessel 1 closer to the target. When prioritizing the longitudinal direction for center of gravity balance, the weight W x Similarly, equation (b2) is an equation for moving the horizontal position of the center of gravity of the vessel 1 closer to the target, and equation (b3) is an equation for moving the vertical position of the center of gravity of the vessel 1 closer to the target. x , W y , W z By appropriately setting the center of gravity, the center of gravity can be adjusted to a desired position.

[0129] The formulas (b4) to (b8) in FIG. 8B are intended to improve the work efficiency of the cargo handling equipment (RTG1-2, GC1-2) on the container yard side.

[0130] Equation (b4) is a function aimed at reducing the amount of handling by cargo handling equipment at the container yard. In equation (b4), GC1 = GC2 indicates that one gantry crane will load container 1 and container 2. t1 > t2 indicates that container 1 is placed above container 2. s1 > s2 indicates that container 1 will be loaded later than container 2. The entire equation (b4) indicates how many combinations of the locations of container 1 and container 2 on ship 1 satisfy the conditions that container 1 is placed above container 2 and container 2 is loaded first. In other words, this equation indicates how many pairs of containers will need to be handled at the yard among the group of containers to be loaded. This is used as the objective function, and the container loading location VL that is minimized through optimization calculations is calculated. xyz By calculating this, the location of the container that does not need to be re-handled can be calculated. By including such an equation in the objective function, the location after loading that does not need to be re-handled can be calculated according to the position of the stored container, thereby (indirectly) improving the work efficiency of the cargo handling equipment (GC1-2).

[0131] Equation (b5) is a function designed to reduce interference between cargo-handling equipment in a container yard. In equation (b5), GC1 ≠ GC2 indicates that two RTGs (RTGs 1 and 2) are working together. b1 ≒ b2 indicates that the bays being worked on are adjacent. s1 ≒ s2 indicates that the loading order of containers 1 and 2 is close. Equation (b5) as a whole indicates how many combinations of the locations of containers 1 and 2 on ship 1 satisfy the conditions that containers 1 and 2 are close in storage location and loading order, and container 1 is loaded by GC1 and container 2 is loaded by GC2. By including equation (b5) in the objective function and performing an optimization (minimization) calculation, the likelihood of container 1 and container 2 being located in a way that satisfies these conditions is reduced, thereby improving the work efficiency of the cargo-handling equipment (RTGs 1 and 2 or GCs 1 and 2).

[0132] Equation (b6) is a formula for ensuring that the bays of the containers being worked on are the same as much as possible to reduce RTG movement. b1 ≠ b2 in equation (b6) indicates that the bays where containers 1 and 2 being worked on are not the same are stored. s1 + 1 = s2 indicates that container 2 is loaded after container 1. The entire equation (b6) indicates how many combinations of locations for containers 1 and 2 satisfy the condition that containers 1 and 2 are loaded by a single GC1, where the bay numbers of the storage locations in the yard for containers 1 and 2 are not the same and the loading order is consecutive. By including equation (b6) in the objective function and performing optimization (minimization) calculations, the possibility of container 1 and container 2 being located on vessel 1 in a way that satisfies this condition is reduced, thereby improving the work efficiency of the cargo handling equipment.

[0133] Equation (b7) is a function aimed at allocating one piece of cargo handling equipment to one bay in a container yard. Equation (b7) shows how many combinations of container 1 and container 2 there are that satisfy the condition that two GCs, GC1 and GC2, work in the same bay (b1 = b2). By reducing the possibility of the locations of container 1 and container 2 occurring that would cause this condition to be met, the number of times that cargo handling equipment needs to be moved can be reduced, thereby improving work efficiency.

[0134] Equation (b8) is a function that aims to create a sequence in which loaded containers are loaded together as much as possible. In equation (b8), f1 ≠ f2 indicates that the container types (whether loaded or empty) are different, and equation (b8) as a whole indicates the number of combinations of the locations of container 1 and container 2 that result in different types of container 1 and container 2 being loaded consecutively. By reducing the possibility of the locations of container 1 and container 2 satisfying this condition, it is possible to avoid situations such as loading an empty container, followed by a loaded container, and then loading an empty container again.

[0135] As shown in Figures 22 and 23, weighting coefficients can be set arbitrarily in the above equations (b1) to (b8), so the desired location can be calculated by assigning a larger weight to the item that is more important.

[0136] The calculation engine 22 calculates the variable VL such that the value of the objective function expressed by the formula (c1) is minimized. dixyz Then, the calculation engine 22 calculates the variable VL by applying a predetermined rule for determining the loading order (for example, in one bay, loading is performed in order from the row on the sea side, in an area determined by one bay and one row, containers are loaded in order from the empty location on the bottom, etc.). dixyz The loading order of each container can be calculated from

[0137] [Processing flow (client device side)] The flow of processing executed by the client device 3 will be described with reference to Fig. 24. Fig. 24 is a flowchart showing an example of processing executed by the client device 3. This flowchart includes each step of a cargo handling planning support method executed by the client device 3 according to this embodiment.

[0138] In S1, the client module 31 acquires input data via the user interface 32. The input data acquired here is data that is required for calculating the cargo handling plan and that the user needs to enter. The client module 31 may acquire the input data, for example, by displaying a predetermined UI screen on the display unit and accepting user operations on the UI screen (for example, the UI screen 110 in FIG. 11 or the UI screen 140 in FIG. 14).

[0139] In S2, the client module 31 accepts input of a calculation instruction for a cargo handling plan. As described above, the cargo handling plan that is the target of the calculation instruction is any one of (1) a loading slot plan, (2) a cargo handling equipment work plan, (3) a cargo unloading plan, and (4) a shipping plan. For example, when generating (2) a cargo handling equipment work plan, the client module 31 may accept an input operation on the start button B3 on the UI screen 110 of FIG. 11 as a calculation instruction.

[0140] In S3, the client module 31 transmits a request to calculate a cargo handling plan to the server device 2. At this time, the client module 31 also transmits the input data acquired in S1 to the server device 2. As a result, the server device 2 calculates the cargo handling plan based on the input data. As described above, the server device 2 calculates the cargo handling plan using a mathematical optimization method for (1) the loading quota plan or (4) the shipping plan.

[0141] Here, the input data transmitted by the client module 31 to the server device 2 will be further explained with reference to Fig. 25. Fig. 25 is a diagram showing an example of input data transmitted by the client module 31 to the server device 2. The input data shown in Fig. 25 includes, as an example, a total of 23 data items from No. 01 to No. 23.

[0142] For example, the client module 31 may reflect the content entered by the user in one or more input data files including each of the 23 data items, and transmit the input data files including the content entered by the user to the server device 2. As will be described in detail below, the data items shown in Fig. 25 include data items that are commonly used regardless of the type of cargo handling plan, and data items that are used only in specific types of cargo handling plans. For data items that are used only in specific types of cargo handling plans, the user's input content only needs to be entered when instructing that cargo handling plan.

[0143] Data items No. 01 to No. 05 are data items that are commonly used regardless of the type of cargo handling plan. No. 01 "Calculation start date and time" indicates the date and time to start calculating the cargo handling plan, No. 02 "Vessel ID" indicates the identification information of vessel 1 that is the subject of the cargo handling plan, No. 03 "Unloading ID" indicates the identification information of the unloading work of vessel 1, No. 04 "Loading ID" indicates the identification information of the loading work of vessel 1, and No. 05 "Calculation mode" indicates the type of cargo handling plan.

[0144] Data items No. 06 to No. 11 are data items used in the work plan for cargo handling equipment. Data for each of these data items can be entered via UI screen 110 shown in FIG. 11. Specifically, the selection result of radio button 111 or 112 is reflected in No. 06, "Loading and Unloading Work Sequence." Similarly, the values ​​entered in input boxes 113 to 115 are reflected in No. 07, No. 08, and No. 11, "Initial Position of Cargo Handling Equipment," respectively. Note that if there is a third cargo handling equipment and the initial position of that equipment is entered, the entered initial position is reflected in No. 09; if there is a fourth cargo handling equipment and the initial position of that equipment is entered, the entered initial position is reflected in No. 10.

[0145] Data items No. 12 to No. 23 are data items used in the shipping plan. The data for each of these data items can be input, for example, via the UI screen 140 shown in FIG. 14. Specifically, the selection result of radio button 141 or 142 is reflected in No. 15, "Select ideal center of gravity position." Furthermore, the numerical value input in input box 143 is reflected in No. 12, "X-direction distance between center of gravity position and structure center," and the numerical value input in input box 144 is reflected in No. 14, "Z-direction distance between center of gravity position and structure center." Data for a data item whose value is determined based on a user input can be said to be data indicating a first constraint. In other words, the client module 31 may acquire the first constraint as input data.

[0146] Note that the user may also be prompted to input "distance in y direction between center of gravity position and structural center" in No. 13, but it is preferable to set "distance in y direction between center of gravity position and structural center" to a fixed value (typically 0). This prevents the generation of a shipping plan in which the center of gravity position and the structural center are shifted in the y direction. In this way, the client module 31 may transmit input data to the server device 2 that includes data of a predetermined value, which is not input by the user.

[0147] Additionally, the data items No. 16 to No. 23 for "Objective Function Weighting" are used to specify weights included in the objective function used in the optimization calculation of the shipping plan. For example, the degree of "Reduction of Number of Transfers," the necessity of "Avoiding Interference," and the possibility of "Allowing Work in the Same Bay," which are specified on the UI screen 140 shown in FIG. 14, are reflected in the corresponding data items for "Objective Function Weighting." Note that it is not necessary to determine all weights based on user input, and some weight values ​​may be fixed values ​​that are not dependent on user input.

[0148] Returning now to the explanation of the flowchart in Fig. 24, in S4, the client module 31 receives a cargo handling plan from the server device 2. The client module 31 also displays the cargo handling plan received from the server device 2 on the display unit. As explained with reference to Figs. 5, 12, 13, and 15, it is preferable to display the cargo handling plan in a manner appropriate to its type. Note that if the calculation instruction received in S2 targets (1) a stacking frame plan and a center plan exists, the processing in S3 may be omitted, and the stacking frame plan shown in the center plan may be displayed in S4.

[0149] In S5, the client module 31 determines whether the cargo handling plan displayed in S4 has been adopted. For example, the client module 31 may accept an input operation on the Adopt button B1 shown in Figures 5, 12, 13, and 15 as an input indicating the adoption of the cargo handling plan. In this case, in S5, the client module 31 determines YES if an input operation on the Adopt button B1 is detected, and NO if another input operation (for example, an input operation on the Restore button B2) is detected. If the determination in S5 is YES, the process proceeds to S6, and if the determination in S5 is NO, the process proceeds to S7.

[0150] In S6, the client module 31 transmits an instruction to register the cargo handling plan to the server device 2. As a result, the cargo handling plan received in S4 is stored in the storage device 4 by the server device 2. After S6 ends, the process proceeds to S8.

[0151] In S7, the client module 31 determines whether an operation to restore the cargo handling plan received in S4 has been performed. For example, the client module 31 may accept an input operation to the restore button B2 as an input indicating that the cargo handling plan should be restored. In this case, in S7, the client module 31 determines YES if an input operation to the restore button B2 has been detected, and NO if another input operation (for example, an operation to modify the cargo handling plan) has been detected. If the determination in S7 is YES, the process proceeds to S11, and if the determination in S7 is NO, the process proceeds to S8.

[0152] In S8, the client module 31 determines whether an operation to modify the cargo handling plan received in S4 has been performed. If the determination in S8 is NO, the illustrated processing ends. On the other hand, if the determination in S8 is YES, the processing proceeds to S9.

[0153] In S9, the client module 31 reads out the cargo handling plan to be corrected, i.e., the cargo handling plan stored in the storage device 4 by the server device 2. The client module 31 may have the server device 2 read out the cargo handling plan and acquire the cargo handling plan from the server device 2. The client module 31 may also accept correction input for the cargo handling plan that was received in S4 but not determined to be adopted in S5, i.e., the cargo handling plan before being stored in the storage device 4. In this case, after the determination of YES in S8 is made, S9 is omitted and the processing of S10 is performed.

[0154] In S10, the client module 31 accepts input for correction to the cargo handling plan read out in S9. As described with reference to Figures 5, 12, 13, and 15, the client module 31 may accept input for correction via a UI screen that displays the cargo handling plan.

[0155] In S11, the client module 31 updates the display content of the cargo handling plan. Specifically, in S11 after transition from S10, the client module 31 reflects the content of the correction input received in S10 in the display of the cargo handling plan. On the other hand, in S11 after transition from S7, the client module 31 returns the cargo handling plan to the display content before S4. Furthermore, when transitioning from S7 to S11 after receiving a correction, the client module 31 may return the display content of the cargo handling plan to the content before the correction.

[0156] As described above, the cargo handling plan support method according to this embodiment is a cargo handling plan support method executed by the client device 3, and includes a step (S2) of accepting input of a calculation instruction for a cargo handling plan, which is either a stacking quota plan for planning the stacking quota of containers on the ship 1 or a shipping plan for planning the order in which containers are to be loaded onto the ship 1, and transmitting a calculation request to the server device 2 upon accepting the input, a step (S4) of the server device 2 receiving the cargo handling plan calculated by a mathematical optimization technique, and a step (S5) of accepting input indicating whether the received cargo handling plan is adopted or rejected. This makes it possible to generate a highly accurate stacking quota plan or shipping plan that is in line with the user's intentions.

[0157] The client module 31 included in the client device 3 can also be realized by a program. The program causes a computer (for example, the client device 3 or any other information processing device) to execute the above steps. This program can provide the same effects as the cargo handling planning support method executed by the client module 31.

[0158] [Processing flow (server device side)] The flow of processing executed by the server device 2 will be described with reference to Fig. 26. Fig. 26 is a flowchart showing an example of processing executed by the server device 2. This flowchart includes each step of a cargo handling planning support method executed by the server device 2 according to this embodiment.

[0159] In S21, the server module 21 receives a calculation request for a cargo handling plan from the client device 3. This calculation request is transmitted in S3 of Fig. 24 and requests the generation of any one of (1) a loading slot plan, (2) a cargo handling equipment operation plan, (3) a cargo unloading plan, and (4) a shipping plan. In S21, the server module 21 also receives input data such as the first constraint condition input by the user along with the calculation request.

[0160] In S22, the server module 21 reads data for calculating a cargo handling plan from the storage device 4. The data for calculating a cargo handling plan may include parameters used in optimization calculations (for example, information about the ship 1, parameters set by the user, etc.). The data may also include the scheduled arrival of the ship 1 in port (the start date and time of cargo handling, the start and end dates and times of work for each cargo handling equipment, etc.), compartments on the ship, weight limits for each row, information indicating the bay structure, information indicating the hatch structure within the bay, attributes of each cell (whether hazardous materials can be loaded, whether there is power, etc.), information about the tier of each bay, information about usable cargo handling equipment, and information about the containers to be loaded.

[0161] As described above, the user may specify the initial positions and safety distances of the cargo handling equipment, the position of the center of gravity of the ship 1, the degree to which the number of handling operations in the yard is reduced, whether or not to avoid interference between yard cargo handling equipment, whether or not to allow multiple yard cargo handling equipment to work in the same bay, etc. When such specifications are made, the server module 21 identifies the specified contents from the input data received from the client device 3.

[0162] In S23, the server module 21 instructs the calculation engine 22 to calculate a cargo handling plan. At this time, the server module 21 transmits to the calculation engine 22 various data necessary for calculating the cargo handling plan, such as the data read in S22 and the input data received from the client device 3.

[0163] In S24, the calculation engine 22 calculates a cargo handling plan in accordance with the instructions in S23. The calculation method for the cargo handling plan may be predetermined depending on the type of cargo handling plan. For example, the calculation engine 22 may calculate (1) the loading slot plan and (4) the shipping plan using a mathematical optimization method. On the other hand, the calculation engine 22 may calculate (2) the cargo handling equipment work plan and (3) the unloading plan using a rule base.

[0164] In S25, the server module 21 acquires the cargo handling plan calculated in S24 from the calculation engine 22. Subsequently, in S26, the server module 21 transmits the cargo handling plan acquired in S25 to the client device 3. The step in which the client module 31 receives the cargo handling plan transmitted in this manner is S4 in Fig. 24. As described above, in S5 following S4 in the flow shown in Fig. 24, it is determined whether the cargo handling plan is adopted, and if it is adopted (YES in S5), a registration instruction is transmitted to the server device 2 in S6.

[0165] In S27, the server module 21 determines whether the cargo handling plan transmitted in S26 has been adopted. For example, the server module 21 may determine that the cargo handling plan has been adopted when it receives an instruction to register the cargo handling plan from the client device 3. If the determination in S27 is YES, the process proceeds to S28, and if the determination in S27 is NO, the illustrated process ends.

[0166] In S28, the server module 21 stores the cargo handling plan acquired in S25 in the storage device 4. This ends the illustrated processing.

[0167] As described above, the cargo handling plan support method according to this embodiment is a cargo handling plan support method executed by the server device 2 (more precisely, the server module 21), and includes the steps of: receiving a cargo handling plan calculation request from a client device (S21); reading data for calculating the cargo handling plan from the storage device 4 that stores the data upon receiving the calculation request (S22); instructing the calculation engine 22, which calculates the cargo handling plan by a mathematical optimization method using the read data, to calculate the cargo handling plan (S23); and acquiring the cargo handling plan calculated by the calculation engine 22 and transmitting the acquired cargo handling plan to the client device 3 (S26). This makes it possible to present a highly accurate loading quota plan or shipping plan to the user.

[0168] The server module 21 can also be realized by a program. The program causes a computer (for example, the server device 2 or any other information processing device) to execute the above steps. This program can provide the same effects as the cargo handling planning support method executed by the server module 21.

[0169] 26, the server module 21 acquires the cargo handling plan calculated by the calculation engine 22 and transmits the acquired cargo handling plan to the client device 3. Then, as described with reference to Fig. 24, when the client module 31 receives the cargo handling plan from the server module 21, it displays the cargo handling plan on the display unit and accepts an input indicating whether or not to adopt the cargo handling plan. This allows the user to confirm the cargo handling plan calculated by the calculation engine 22 and further enables the user to specify whether or not to adopt the cargo handling plan.

[0170] Furthermore, when the client module 31 receives an input indicating the adoption of a cargo handling plan, it transmits an instruction to the server device, and when the server module 21 receives the instruction, it stores the adopted cargo handling plan in the storage device 4. This allows only the cargo handling plan calculated by the calculation engine 22 that the user adopts to be stored in the storage device 4.

[0171] The client module 31 also accepts input for modifying information included in the cargo handling plan calculated by the calculation engine 22, and stores the modified cargo handling plan in the storage device 4. This makes it possible to create a cargo handling plan that is in line with the user's intentions down to the smallest detail, and also makes it possible to easily generate a cargo handling plan that can accommodate irregular changes in conditions.

[0172] [Software implementation example] As described above, the functions of the server module 21 and the client module 31 (hereinafter simply referred to as "modules") can be realized by a program that causes a computer to function as the module, and that causes a computer to execute the processes shown in Figures 24 and 26. Similarly, the functions of the calculation engine 22 can be realized by a program that causes a computer to execute the processes that the calculation engine 22 executes.

[0173] In this case, the server device 2 and the client device 3 are equipped with a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., a memory) as hardware for executing the above programs. The functions of the above modules are realized by executing the above programs using the control device and storage device.

[0174] The program may be stored non-transitory on one or more computer-readable storage media. The server device 2 and the client device 3 may or may not have these storage media. In the latter case, the program may be supplied to the server device 2 or the client device 3 via any wired or wireless transmission medium.

[0175] Furthermore, some or all of the functions of the above modules can be realized by logic circuits. For example, an integrated circuit in which a logic circuit that executes each process shown in Figures 24 and 26 is formed is also included in the scope of the present invention. In addition, the functions of each of the above modules can also be realized by, for example, a quantum computer.

[0176] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of symbols]

[0177] 2. Server device 21 Server Module 22 Calculation Engine 3. Client Device 31 Client Module 4 Storage device 7. Cargo handling planning support system 100 Container Terminal Operation System

Claims

1. A cargo handling plan support system including a client device, a server device, and a storage device that stores data for calculating a cargo handling plan, The cargo handling plan is either a stacking plan for planning a stacking frame of containers on a ship, or a shipping plan for planning the order in which containers are loaded onto a ship, the client device comprises a client module; the client module receives an input of a calculation instruction for the cargo handling plan, and upon receiving the input, transmits a calculation request to the server device; the server device includes a server module and a calculation engine; When the server module receives the calculation request, it reads the data from the storage device and instructs the calculation engine to calculate the cargo handling plan; the calculation engine calculates the cargo handling plan by a mathematical optimization method using the read data in accordance with the instruction; Cargo handling planning support system.

2. the client module accepts input of a first constraint condition for calculating the loading and unloading plan, and transmits the accepted first constraint condition to the server device; the server module provides the first constraint sent from the client module to the calculation engine; The calculation engine calculates the loading and unloading plan that satisfies the provided first constraint condition. The cargo handling planning support system according to claim 1.

3. the data includes a predetermined second constraint for calculating the loading plan; The cargo handling plan support system according to claim 2 , wherein the calculation engine calculates the cargo handling plan that satisfies the second constraint condition.

4. The cargo handling plan support system according to claim 3 , wherein the calculation engine calculates the cargo handling plan that satisfies both the first constraint condition and the second constraint condition.

5. the client module receives input of at least one of the following as the first constraint condition for the shipping plan: the position of the center of gravity of the ship; the degree to which the number of handling operations in the yard is reduced; whether or not interference between yard handling equipment performing loading and unloading operations in the yard is avoided; and whether or not multiple yard handling equipment are allowed to work in the same bay; and transmits the received first constraint condition to the server device; the calculation engine calculates the shipping plan that satisfies the first constraint condition; The cargo handling planning support system according to claim 2.

6. the server module acquires information indicating a progress status of the calculation of the cargo handling plan from the calculation engine, and transmits the acquired information indicating the progress status to the client device; 2. The cargo handling planning support system according to claim 1, wherein, upon receiving the information, the client module causes a display unit to display the progress status based on the information.

7. The server module acquires the cargo handling plan calculated by the calculation engine and transmits the acquired cargo handling plan to the client device; When the client module receives the cargo handling plan, the client module displays the cargo handling plan on a display unit and accepts an input indicating whether or not the cargo handling plan is adopted. The cargo handling planning support system according to claim 1.

8. When the client module receives an input indicating adoption of the loading and unloading plan, the client module transmits an instruction to the server device; 8. The cargo handling plan support system according to claim 7, wherein, when the server module receives the instruction, the server module stores the adopted cargo handling plan in the storage device.

9. The client module Accepting input of corrections to information included in the loading and unloading plan calculated by the calculation engine; 2. The cargo handling plan support system according to claim 1, wherein the modified cargo handling plan is stored in the storage device.

10. The client module further requests the server device to calculate a loading plan for planning the order in which containers are to be unloaded from the ship; Upon receiving the request, the server module reads the data from the storage device and instructs the calculation engine to calculate the unloading plan; The cargo handling planning support system according to claim 1 , wherein the calculation engine calculates the cargo unloading plan using a rule base with the read data as an input in accordance with the instruction.

11. The client module further requests the server device to calculate a work plan for loading and unloading equipment for loading containers onto a ship; Upon receiving the request, the server module reads the data from the storage device and instructs the calculation engine to calculate the work plan; 2. The cargo handling planning support system according to claim 1, wherein the calculation engine calculates the work plan using a rule base with the read data as an input in accordance with the instruction.

12. the client module receives input of at least one of the order of container loading and unloading operations, the operation start positions of the cargo handling equipment, and the minimum interval between the cargo handling equipment as first constraint conditions for calculating the work plan, and transmits the received first constraint conditions to the server device; the server module provides the first constraint sent from the client module to the calculation engine; the calculation engine calculates the work plan that satisfies the provided first constraint condition; The cargo handling planning support system according to claim 11.

13. In response to the client module receiving an input indicating adoption of the stacking frame plan calculated by the calculation engine, the server module stores the stacking frame plan in the storage device, and then: In response to the client module receiving an input indicating adoption of the work plan calculated by the calculation engine, the server module stores the work plan in the storage device, and then:

13. The cargo handling planning support system according to claim 11, wherein the server module stores the shipping plan in the storage device in response to the client module receiving an input indicating adoption of the shipping plan calculated by the calculation engine.

14. The client module In response to receiving an input indicating adoption of the stacking frame plan calculated by the calculation engine, the server module reads out the stacking frame plan stored in the storage device; Accepting input to correct information included in the read-out stacking plan; storing the modified stack plan in the storage device; The calculation engine 13. The cargo handling planning support system according to claim 11, wherein the data read from the storage device in which the corrected loading slot plan is stored is used in calculating the work plan and the shipping plan.

15. The client module reading out the work plan stored in the storage device by the server module in response to receiving an input indicating adoption of the work plan calculated by the calculation engine; Accepting input to correct information included in the read work plan; storing the modified work plan in the storage device; 13. The cargo handling planning support system according to claim 11, wherein the calculation engine uses the data read from the storage device in which the modified work plan is stored when calculating the shipping plan.

16. 2. The cargo handling plan support system according to claim 1, wherein the client device is a device that is included in a container terminal operation system and that manages the cargo handling plan.

17. On the computer, receiving an input of a calculation instruction for a cargo handling plan, which is either a loading quota plan for planning a container loading quota on a ship or a shipping plan for planning the order in which containers are loaded onto a ship, and transmitting a calculation request to a server device upon receiving the input; receiving the cargo handling plan calculated by the mathematical optimization method by the server device; and receiving an input indicating whether or not the received cargo handling plan is adopted.

18. On the computer, receiving, from a client device, a calculation request for a cargo handling plan, which is either a stacking plan for planning a container stacking frame on a ship or a shipping plan for planning the order in which containers are loaded onto a ship; When receiving the calculation request, reading the data for calculating the loading and unloading plan from a storage device that stores the data; instructing a calculation engine that calculates the cargo handling plan by a mathematical optimization method using the read data to calculate the cargo handling plan; and a program for executing a step of acquiring the cargo handling plan calculated by the calculation engine and transmitting the acquired cargo handling plan to the client device.

Images