Method and system for recording the appearance of containers in a container terminal

Abstract

This invention provides a method and system for recording the appearance of containers at a container terminal, enabling the construction of a database that can more accurately grasp the status of ensuring the integrity of a container by tracing the changes in its appearance at the container terminal over time. [Solution] In the collection step S100, multiple image data (D1 to D4) are acquired by multiple cameras (21 to 24), and the crane calculation device 25 transmits the multiple image data and completion report data C2 as pairs of data to the management calculation device 26. In the construction step S200, the management calculation device 26 adds a group of data 31 for container identification information, and constructs an appearance record database 30 in which a group of data 31 is stored for each container identification information for a large number of containers 2 that have entered and left the container terminal 1 in the past but do not currently exist, and a large number of containers 2 that currently exist in the container terminal 1.

Description

Technical Field

[0001] The present invention relates to a method and system for recording the appearance of containers at a container terminal. More specifically, it relates to a method and system for recording the appearance of containers at a container terminal that can construct a database capable of more faithfully grasping the status of ensuring the soundness of a container by tracing the transition of the appearance of a desired container at the container terminal.

Background Art

[0002] In containers used for maritime or land transportation, the appearance state is checked to ensure their soundness, and appropriate repairs are made when injuries or the like are found on the appearance. In this regard, a system has been proposed that acquires an image of the appearance of a container by a camera installed in a container terminal and examines the state of the container by grasping container identification information (for example, container number) and the physical characteristics of the container by analyzing the acquired image (see Patent Document 1).

[0003] When damage is detected in a container shipped from a container terminal, the owner of the container or the owner of the goods stored in the container needs to trace the transition of the appearance of the container at the container terminal in order to investigate the cause of the damage to the container. However, the shipping container database constructed by the system proposed in Patent Document 1 only accumulates indicators for inspecting the state of the container. Even if the owner accesses the shipping container database, only the indicators for inspection can be obtained. Therefore, there is room for improvement in constructing a database that can more faithfully grasp the status of ensuring the soundness of a container by tracing the transition of the appearance of a desired container at the container terminal.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

[0005] The object of the present invention is to provide a method and system for recording the appearance of containers in a container terminal that can build a database that allows for a more accurate understanding of the status of ensuring the integrity of a container by tracing the changes in the appearance of a desired container at the container terminal. [Means for solving the problem]

[0006] The present invention provides a method for recording the appearance of containers in a container terminal that achieves the above objective, comprising a collection step and a construction step, wherein the method includes a collection step and a construction step, and in the collection step, which is performed each time the containers are loaded or unloaded by the numerous cranes, when the containers are loaded or unloaded by the cranes based on loading or unloading command data transmitted from the management computer to the crane computer, the multiple cameras of the crane that performed the loading or unloading acquire multiple image data of the containers to be loaded or unloaded in that loading or unloading, taken from different directions, and after the loading or unloading is completed, the crane computer processes the multiple cameras. In the construction step, a management computing device is created to construct an appearance record database using the pair of data collected in the collection step. In this step, the management computing device adds a group of data for each of the container identification information in the pair of data, and for each of the containers that have entered and left the container terminal in the past but are no longer present, and for each of the containers that are currently present in the container terminal, a group of data for each of the container identification information is stored in the appearance record database.

[0007] The container terminal appearance recording system of the present invention comprises a plurality of cameras and a crane computing device, each of a plurality of cranes, and a management computing device that issues cargo handling command data to the crane computing device and manages the cargo handling of a plurality of containers present in the container terminal, wherein image data of the container acquired by the plurality of cameras is transmitted from the crane computing device to the management computing device and recorded by the management computing device, and the crane computing device records a plurality of image data acquired by the plurality of cameras of the crane that performed the cargo handling, which are images of the container to be handled in that cargo handling, taken from different directions, and the cargo handling The system performs data processing to transmit a pair of data, consisting of completion report data including the date and time of the operation, unique container identification information of the container subject to handling, and unique crane identification information of the crane that performed the handling, to the management computing device. The management computing device receives the pair of data collected each time the container is handled for each of the numerous cranes and performs data processing to add a group of data comprising the image data and the respective data for the container identification information in the pair of data. This constructs an appearance record database in which a large number of group data for each container identification information is stored for a large number of containers that have entered and left the container terminal in the past but are not currently present, and a large number of containers that are currently present in the container terminal. [Effects of the Invention]

[0008] According to the present invention, the constructed appearance record database records the appearance of containers currently under the management of the container terminal, as well as containers that were under its management in the past, as a set of data. Since each set of data includes multiple image data acquired during the handling of containers by cranes, it accurately represents the appearance of that container. Furthermore, the set of data for each container identification information represents the changes in the appearance of the container at the container terminal. Therefore, by accessing the appearance record database, it is possible to trace back the actual changes in the appearance of a desired container at the container terminal and to more accurately grasp the status of ensuring the integrity of the container at that terminal. As a result, this greatly contributes to investigating the causes of container damage. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the configuration of a container terminal. [Figure 2] This is an explanatory diagram illustrating a transfer crane. [Figure 3] This is an explanatory diagram illustrating a gantry crane. [Figure 4] This is an explanatory diagram illustrating cargo handling instruction data. [Figure 5] This is an explanatory diagram illustrating the completion report data. [Figure 6] This is an explanatory diagram illustrating an example of a container appearance recording system at a container terminal. [Figure 7] This flowchart illustrates the procedure for an embodiment of a method for recording the appearance of containers at a container terminal. [Figure 8] This is an entity-relationship diagram illustrating an example of an appearance record database. [Figure 9] This is an illustrative diagram showing the output screen of the appearance record database. [Figure 10] This is an explanatory diagram illustrating a container appearance recording system at a container terminal in a modified example (1). [Figure 11] This is an explanatory diagram illustrating a container appearance recording system at a container terminal in a modified example (2). [Figure 12] This is an explanatory diagram illustrating transit report data. [Modes for carrying out the invention]

[0010] The method and system for recording the appearance of containers in a container terminal according to the present invention will be described below based on the embodiments shown in the figures.

[0011] First, let's explain the details of Container Terminal 1 and Crane 10.

[0012] The container terminal 1 illustrated in Figure 1 can utilize various known container terminals that serve as logistics hubs by temporarily storing containers 2. In container terminal 1, containers 2 are temporarily stored in storage lane 3.

[0013] Container Terminal 1 is divided into a container yard 4 and a vessel handling area 5. Container yard 4 has multiple gates 6 that serve as entrances and exits to the outside. Container yard 4 also has multiple storage lanes 3 where containers 2 are stored, and a transfer crane 10A that runs along the longitudinal direction of the storage lanes 3. Within the vicinity of the gates 6 of container yard 4 is an administration building 7, which houses a management computing device 26, described later. Vessel handling area 5 is the area where vessels 8 are docked and has multiple gantry cranes 10B for loading and unloading containers 2 onto those vessels 8.

[0014] The transport vehicles (9A, 9B) are container trailers on which the driver rides. The transport vehicle 9A is an external vehicle that travels between the outside and the container yard 4 via the gate 6. The transport vehicle 9B travels between the container yard 4 and the ship cargo handling area 5. The transport vehicle 9B is not particularly limited as long as it can horizontally transport the container 2, and for example, a known automated guided vehicle (AGV) or a straddle carrier can also be used. Hereinafter, the crane 10 shall represent both the transfer crane 10A and the gantry crane 10B.

[0015] The transfer crane 用演算装置 10A and the gantry crane 10B illustrated in FIGS. 2 and 3 respectively have some differences in their respective configurations but most of their respective configurations are common, so they will be described together. The transfer crane 10A can use a known transfer crane (yard crane), and the gantry crane 10B can use a known gantry crane. The crane 10 includes a girder (girder or girder and cantilever) 11, a trolley 12, a spreader 13, a leg structure 14, a number of cameras (21 to 24), and a crane arithmetic unit 25.

[0016] The girder 11 extends in one direction (the Y direction in FIG. 2, the X direction in FIG. 3). The girder 11 of the transfer crane 10A crosses above the storage lane 3 and the travel paths of the transport vehicles 9A and 9B extending along the storage lane 3. The girder 11 of the gantry crane 10B projects from both sides of the leg structure 14 in the X direction, and one end crosses above the upper deck of the ship 8 not shown in FIG. 3. The trolley 12 is supported by the girder 11 and travels along the girder 11. The spreader 13 is suspended from the trolley 12 via a wire rope and moves up and down in the Z direction.

[0017] The leg structure 14 supports the girder 11 at the upper part. The leg structure 14 has four legs 15, a plurality of beams (16a in FIG. 2, 16a to 16d in FIG. 3), and four traveling devices 17. The legs 15 are erected in the Z direction. The sill beam 16a extends in the traveling direction (X direction in FIG. 2, Y direction in FIG. 3) and connects the lower ends of the legs 15 facing each other in the traveling direction. The horizontal member 16b extends in the X direction and connects the middle parts of the legs 15 facing each other in the X direction. The diagonal member 16c is arranged obliquely and connects the legs 15 facing each other in the X direction. The tie beam 16d extends in the Y direction and connects the upper ends of the legs 15 facing each other in the Y direction.

[0018] The traveling device 17 is installed at the lower end of each leg 15. The traveling device 17 of the transfer crane 10A has a plurality of rubber tires as wheels 18. The traveling device 17 of the gantry crane 10B has a plurality of steel wheels as wheels 18. The crane 10 travels by this traveling device 17. The transfer crane 10A travels in the X direction along the storage lane 3. The gantry crane 10B travels in the Y direction along the rails laid in the ship's cargo handling area 5. Similar to the gantry crane 10B, the transfer crane 10A may also have a plurality of steel wheels as wheels 18 and travel in the X direction along the rails laid along the storage lane 3.

[0019] Each of the transfer crane 10A and the gantry crane 10B performs cargo handling between the container 2 connected to the lifting device 13 and the transport vehicles 9A and 9B parked at a predetermined storage location and a predetermined position. Specifically, the transfer crane 10A performs cargo handling of the container 2 between the storage lane 3, which is a predetermined storage location, and the transport vehicles 9A and 9B parked at a predetermined position. The gantry crane 10B performs cargo handling of the container 2 between the ship 8, which is a predetermined storage location, and the transport vehicle 9B parked at a predetermined position. The predetermined positions where the transport vehicles 9A and 9B stop can be arbitrarily set. For example, they are inside the leg structure 14 of each crane.

[0020] Each crane 10's cargo handling operation is controlled by its own crane calculator 25 based on cargo handling command data C1 transmitted from the management calculator 26. Once cargo handling is completed by the crane 10, the management calculator 26 updates the management data for the numerous containers 2 at the container terminal 1 based on completion report data C2 transmitted from each crane calculator 25. In this way, at the container terminal 1, the numerous containers 2 are managed by the crane calculator 25 of each crane 10 and the management calculator 26 exchanging cargo handling command data C1 and completion report data C2.

[0021] The cargo handling command data C1 illustrated in Figure 4 is generated by the management computing unit 26 and transmitted to the crane computing unit 25. The cargo handling command data C1 contains various data about the cargo handling to be performed by the crane 10. The cargo handling identification information indicates a unique identification information assigned to each cargo handling operation by the crane 10 at the container terminal 1, for example, a sequential number. The cargo handling status indicates the type of cargo handling, for example, loading onto storage lane 3. Other classifications of cargo handling status include loading onto transport vehicles 9A and 9B, and loading onto ships 8. The crane identification information indicates the unique identification information of the crane 10 that will be performing the cargo handling, for example, crane number X. The cargo handling destination indicates the destination of the container 2 to be handled, for example, storage lane 3, which is lane number m, bay number n, row number i, and tier number j. The origin of the cargo handling indicates the location of container 2 being handled; for example, in the case of transport vehicle 9A, it is the vehicle number, which is the unique vehicle identification information of transport vehicle 9A. The origin and destination of the cargo handling may also be ship 8 or transport vehicle 9B. The container identification information indicates the unique identification information of container 2 being handled; for example, it is the container number.

[0022] The completion report data C2, illustrated in Figure 5, is generated by the crane calculation unit 25 and transmitted to the management calculation unit 26. In addition to the cargo handling command data C1 shown in Figure 4, the completion report data C2 includes the actual date and time (YYYY-MM-DD HH) of the cargo handling performed by the crane 10. The date and time can be any date and time between the start and end times of the cargo handling performed by the crane 10. In Figure 5, "YYYY-MM-DD HH" is written as the date and time, but in reality, the year, month, day, and time are written. If the contents of the cargo handling command data C1 differ from the contents of the actual cargo handling performed, the completion report data C2 will be corrected to reflect the contents of the actual cargo handling.

[0023] The same container 2 may be loaded and unloaded multiple times on the same day, and may even be loaded and unloaded multiple times consecutively. Therefore, it is advisable to aggregate the execution date and time added to the completion report data C2 in seconds. By aggregating the execution date and time in seconds, it becomes possible to handle information about each individual loading and unloading operation, even if container 2 is loaded and unloaded multiple times consecutively.

[0024] Next, we will describe the details of the appearance recording system 20.

[0025] A method for recording the appearance of a container 2 at a container terminal 1 is implemented using an embodiment of the appearance recording system 20 illustrated in Figure 6. This appearance recording system 20 and method are used by the owner of a container 2 or the cargo stored in a container 2 to investigate the cause of damage to a container 2 that has been shipped from a container terminal 1 or a container 2 that is currently at a container terminal 1. Specifically, in this embodiment, as will be described later, an appearance recording database 30 is constructed, and the owner can access the appearance recording database 30 from a client computer 40 to understand the changes in the status of a desired container 2 at the container terminal 1.

[0026] This visual recording method has a collection step (collection step S100, described later) and a construction step (construction step S200, described later). To give an overview of each step, the collection step S100 is performed for each of the many cranes 10 each time a container 2 is loaded or unloaded. In the collection step S100, first, multiple image data (D1 to D4) are acquired by multiple cameras (21 to 24) on the crane 10 that is performing the loading or unloading. Next, the crane calculation unit 25 transmits the multiple image data and completion report data C2 as pairs of data to the management calculation unit 26. In the construction step S200, the management calculation unit 26 constructs a visual recording database 30 using the pairs of data collected in the collection step S100. In the construction step S200, the management calculation unit 26 adds a group of data 31 containing each piece of data from the pair of data to the container identification information in the received pair of data, and constructs a visual recording database 30 in which a group of data 31 is stored for each piece of container identification information.

[0027] The visual recording system 20 comprises multiple cameras (21-24), a crane calculation unit 25, and a management calculation unit 26. The management calculation unit 26 receives and stores various data, and performs data processing using this data. The management calculation unit 26 can use various known computers. The management calculation unit 26 has a central processing unit (CPU), main memory, auxiliary storage (e.g., HDD), and input / output unit (network adapter, etc.).

[0028] The management computing unit 26 manages the handling of containers 2 located in container terminal 1 and issues handling command data C1 for containers 2 to each of the numerous crane computing units 25 for the cranes 10. Specifically, the management computing unit 26 generates handling command data C1 based on the scheduled arrival and departure dates of ships 8 and transport vehicles 9A, the number of containers 2 entering and leaving storage lane 3, etc., transmits the generated handling command data C1 to each crane computing unit 25, and receives completion report data C2 transmitted from the crane computing unit 25 when handling based on the handling command data C1 is completed. In container terminal 1, the management computing unit 26 has multiple programs, including a program to manage the handling of containers 2 to ships 8, a program to manage containers 2 in storage lane 3, and a program to transmit handling command data C1 as work instructions to the numerous cranes 10 and transport vehicles 9B. The management computing unit 26 is not limited to a single computer, but may be composed of multiple computers, each dedicated to a specific program.

[0029] Each camera (21-24) can be any known type of camera. Each camera is electrically connected to and controlled by the crane calculation unit 25. The image data acquired by each camera (image data D1-D4 described later) may be still images or moving images. Each camera may have a configuration that allows the zoom magnification (enlargement or reduction of image data) and the direction of the optical axis to be adjusted by the control of the crane calculation unit 25.

[0030] The crane computing device 25 can use various known computers. The crane computing device 25 comprises a processing unit (CPU), a main memory unit (memory), an auxiliary storage unit (e.g., HDD), and an input / output unit (e.g., a network interface). The auxiliary storage unit stores the image data acquired by each camera (21-24), which will be described later. The crane computing device 25 is connected to the management computing device 26 installed in the management building 7 so as to be able to communicate with each other, and transmits each stored image data paired with completion report data C2 to the management computing device 26.

[0031] Next, with reference to Figures 2 and 3, we will describe the details of each camera (21-24) and the acquired image data (D1-D4). In the following, each face of the container 2 will be assigned a corresponding letter to distinguish between the bottom surface 2A, side 2B and side 2C (faces facing the shorter side of the container 2), and the top surface 2D, front surface 2E and rear surface 2F (faces facing the longer side of the container 2). A door is formed on either the front surface 2E or the rear surface 2F.

[0032] The underside camera 21, illustrated in Figures 2 and 3, acquires underside image data D1, including the underside 2A of the container 2 during loading and unloading. The underside camera 21 is installed in the shaded area of ​​the leg structure 14, which is lower than the minimum heights HA and HB shown by the dotted lines in Figures 2 and 3. The installation locations for the underside camera 21 include, for example, the lower part of the legs 15 in the shaded area, the sill beam 16a, the horizontal member 16b (excluding the transfer crane 10A), and the traveling device 17. By installing the underside camera 21 in the lower part of the leg structure 14, which is lower than the minimum heights HA and HB, the underside camera 21 will generally be positioned below the underside 2A of the container 2 during the loading and unloading process. Therefore, the underside camera 21 makes it possible to acquire underside image data D1, including the underside 2A of the container 2.

[0033] During the loading and unloading of container 2 by crane 10, the trolley 12 moves horizontally, and the height (distance in the Z direction) of the underside 2A of the container 2 being loaded, which is connected to the lifting device 13, from the ground (yard surface) changes according to the loading and unloading situation, but this height is maintained above the minimum height HA (see Figure 2) and HB (see Figure 3). In other words, during the loading and unloading of container 2 by crane 10, the container 2 is lifted until the height of the underside 2A of the container 2 from the ground reaches at least the minimum height HA and HB. The minimum height HA is set based on a manned transport vehicle (9A, 9B), and is set to the height of the chassis head of that transport vehicle (e.g., 3m to 5m). The minimum height HB is set based on a ship 8, and is set to the height of the upper deck of the ship 8. The height of the upper deck of the ship 8 varies depending on the specifications of the ship 8, the draft, and the wave conditions. For example, if the minimum height HB is the height of the upper deck + 3m to 5m or more, it is considered to be effective for most types of ships 8. Thus, during the handling of container 2 by crane 10, the container 2 is lifted to a minimum height of HA, HB or higher. Therefore, by installing the underside camera 21 at the bottom of the leg structure 14, which is lower than the minimum height of HA, HB, the underside camera 21 can always photograph the underside 2A of container 2 during handling.

[0034] Each crane may have only one underside camera 21, but it is preferable for the underside cameras 21 to be in pairs. The pair of underside cameras 21 are installed in the center of the upper surface of each of the two sill beams 16a. If the stopping position of the visiting vehicle 9A or the yard vehicle 9B is a fixed position closer to one side of the two sill beams 16a, the underside camera 21 may be installed only on the sill beam 16a closer to that stopping position. In addition, the underside camera 21 may be installed on the underside of the sill beam 16a, or it may be installed closer to the legs 15 of the sill beam 16a.

[0035] The sylbeam 16a is a member that connects the legs 15 facing each other in the longitudinal direction (X direction in Figure 2, Y direction in Figure 3) of the container 2. In other words, in a plan view, the center of the container 2 and the center of the sylbeam 16a are aligned in a straight line. Therefore, by installing the bottom camera 21 in the center of the upper surface of the sylbeam 16a, it becomes possible to photograph the bottom surface 2A from an angle closer to the center of the container 2. This makes it easier to adjust for distortion in the bottom image data D1 acquired by the bottom camera 21.

[0036] The silbeam 16a is less likely to interfere with the loading and unloading of container 2, and provides ample space for installing the underside camera 21. In addition, the silbeam 16a is easily accessible to workers. Therefore, by installing the underside camera 21 on the silbeam 16a, the degree of freedom in installation location is increased, the routing of wiring and piping becomes easier, and maintenance is also easier.

[0037] Furthermore, the sylbeam 16a exhibits less structural deformation compared to other parts of the leg structure 14 (legs 15 and running gear 17). Therefore, it is advantageous in suppressing vibrations caused by this structural deformation. As described above, by installing the bottom camera 21 in the center of the upper surface of the sylbeam 16a, the bottom surface 2A of the container 2 is more clearly visible in the bottom image data D1 acquired by the bottom camera 21.

[0038] The underside camera 21 is directed towards the area above the transport vehicles 9A and 9B that have transported or are transporting the container 2 to be handled, which is to be stored in a predetermined storage location. More specifically, when the transport vehicles 9A and 9B stop at a predetermined stopping position inside the leg structure 14, the underside camera 21 is positioned to face the area above that stopping position, i.e., towards the inside and above the leg structure 14. The underside camera 21 may also be positioned to face the area above the stopping position, i.e., towards the outside and above the leg structure 14 (towards the cantilever), when the transfer crane 10A has a cantilever that extends outward from the leg structure 14, and the transport vehicles 9A and 9B stop outside the leg structure 14 (the trolley 12 moves along the cantilever to handle the container 2). Furthermore, the underside camera 21 may also be positioned facing upward and outward from the leg structure 14 when the gantry crane 10B is loading and unloading cargo onto the transport vehicle 9B using the girder back reach 11 that extends outward from the leg structure 14.

[0039] The underside 2A of container 2 is in shadow even in relatively bright daylight conditions. Therefore, it is preferable that each crane equipped with an underside camera 21 be equipped with a lighting device 27 to illuminate the underside 2A of container 2. The lighting device 27 only needs to be able to illuminate the entire underside 2A of container 2 at the time the underside camera 21 acquires the underside image data D1, and its installation position is not particularly limited. In addition to illuminating the underside 2A of container 2, this lighting device 27 can also be used as nighttime lighting.

[0040] The side cameras 22 only need to be able to acquire image data D2 that includes either side 2B or 2C of the container 2 during loading and unloading, and known cameras installed on the trolley 12 can be used. The side cameras 22 are paired, and a pair of side cameras 22 are installed at each end of the trolley 12 in the traverse direction. The pair of side cameras 22 acquire two image data D2s: one image data D2 that includes side 2B of the container 2 during loading and unloading, and another image data D2 that includes side 2C.

[0041] The top-mounted camera 23 only needs to be able to acquire image data D3 including the top surface 2D of the container 2 before or after loading / unloading, and can use a well-known camera installed on the lifting device 13. For example, the top-mounted camera 23 comes in a set of four, each installed at one of the four corners of the lifting device 13. The set of four top-mounted cameras 23 combine the image data each has acquired to acquire a single image data D3 including the top surface 2D of the container 2 being loaded / unloaded. Alternatively, the top-mounted cameras 23 come in pairs, with the pair installed at each end of the lifting device 13 in the lateral direction. The pair of top-mounted cameras 23 combine the image data each has acquired to acquire a single image data D3 including the top surface 2D of the container 2 being loaded / unloaded. Note that if a single top-mounted camera 23 can acquire image data D3, it is not necessary to have multiple top-mounted cameras 23. Furthermore, the top camera 23 can also acquire image data D3 including the top surface 2D of the container 2 to be loaded onto the ground.

[0042] The front and rear cameras 24 differ between the transfer crane 10A and the gantry crane 10B. The front and rear camera 24 of the transfer crane 10A acquires image data D4 that includes either the front 2E or the rear 2F of the container 2 to be handled, which is placed on the loading platform of the transport vehicles 9A and 9B before or after handling. The front and rear camera 24 of the gantry crane 10B acquires image data D4 that includes either the front 2E or the rear 2F of the container 2 during handling.

[0043] The front and rear cameras 24 of the transfer crane 10A are paired, and the pair of front and rear cameras 24 are installed under the respective travel devices 17 and legs 15 on the front and rear sides of the transfer crane 10A in the direction of travel. One of the pair of front and rear cameras 24 is pointed forward in the direction of travel, and the other front and rear camera 24 is pointed rearward in the direction of travel. The pair of front and rear cameras 24 acquire image data D4 including either the front 2E or the rear 2F of the container 2 when the transport vehicles 9A and 9B, on which the container 2 to be handled is loaded, enter the inside of the leg structure 14 or exit from the inside. The entry and exit of the transport vehicles 9A and 9B into and from the leg structure 14 is caused by the difference in the travel speeds of the crane 10A and the transport vehicles 9A and 9B, respectively. The entry of transport vehicles 9A and 9B into the leg structure 14 occurs, for example, when the crane 10A has stopped moving first, and the transport vehicles 9A and 9B enter and stop inside the leg structure 14 of the crane 10A that has stopped moving.

[0044] The front and rear cameras 24 of the gantry crane 10B are paired, and the pair of front and rear cameras 24 are installed in the center of the upper surface of each of the two horizontal members 16b. The front and rear cameras 24 may also be installed on the underside of the horizontal members 16b, or closer to the legs 15 of the horizontal members 16b. Alternatively, the front and rear cameras 24 may be installed on the legs 15. Each front and rear camera 24 is directed towards the area inside the leg structure 14. Each front and rear camera 24 may be directed downwards or upwards inside the leg structure 14, as long as it is inside the leg structure 14. One front and rear camera 24 acquires image data D4 including the front 2E of the container 2 being handled, and the other acquires image data D4 including the rear 2F.

[0045] Each camera's timing for acquiring image data (shooting timing) is controlled by the crane calculation unit 25. The shooting timing of each camera is different. Based on the position information of the container 2 to be handled, the crane calculation unit 25 causes each camera (21-24) to acquire its respective image data at a predetermined shooting timing. Alternatively, instead of controlling the shooting timing of each camera by the crane calculation unit 25, the shooting timing of each camera may be generated continuously using a predetermined cycle to acquire a large number of continuous image data. If the image data is video, each camera may continuously acquire image data. In this way, when each camera continuously or continuously acquires image data, the crane calculation unit 25 performs data processing to extract image data showing the target surface from the large number of image data, and only the extracted image data is stored in the auxiliary storage unit.

[0046] The position information of the container 2 to be handled can be acquired using each camera (21-24). This position information can also be acquired via a control system that controls the trolley 12, lifting device 13, and running device 17. The control system acquires the position information of the container 2 using various sensors. For example, the approximate position of the container 2 can be calculated using the distance from the center point of the image data D1 acquired by the bottom camera 21 to the container 2 in the image data D1. Alternatively, the position information of the container 2 can be calculated via the control system by calculating the amount of movement of the container 2 based on the traverse amount of the trolley 12 and the winding and unwinding amounts of the wire rope by the drum, as acquired by sensors.

[0047] The timing of the bottom camera 21's shooting can be arbitrarily set as long as the container 2 being loaded and unloaded is in the area above the transport vehicles 9A and 9B, and the height of its underside 2A from the ground is higher than the installation location of the bottom camera 21. Regardless of the loading and unloading situation, the container 2 being loaded and unloaded always reaches the minimum heights HA and HB above the transport vehicles 9A and 9B. Therefore, it always passes through the area below these minimum heights HA and HB. Thus, the timing when the container 2 being loaded and unloaded is in that area can be used as the shooting timing for the bottom camera 21. For example, the shooting timing for the bottom camera 21 is when the container 2 being loaded and unloaded is in the area above the transport vehicle 9, and the height of its underside 2A from the ground reaches the minimum heights HA and HB.

[0048] The timing of the side camera 22's shooting is not particularly limited as long as it occurs during the loading and unloading of the container 2 being handled. Ideally, the side camera 22 should be shooting when it is in close proximity to the container 2 being loaded and unloaded. Therefore, the optimal timing for shooting is while the trolley 12 is moving.

[0049] The timing of the top camera 23's shooting is at least one of the following times: before and after the handling of the container 2 to be handled. Preferably, both of these timings are used. Specifically, the shooting timing is when the lifting device 13 reaches the area above the container 2 when it is stored in a designated storage location, or when the lifting device 13 reaches the area above the container 2 when it is loaded onto the loading platform of transport vehicles 9A and 9B. Preferably, the top camera 23 is closer to the container 2. Another timing for the top camera 23's shooting is when the container 2 is being loaded onto the container 2 to be placed on top of it during the handling of the container 2 to be handled. The image data D3 acquired at this timing captures the top surface 2D of the container 2 to be placed on top of it.

[0050] The timing of the front and rear cameras 24 varies depending on their installation location. For front and rear cameras 24 installed on the underside of the running gear 17 or legs 15, the timing of the shots is before the transport vehicles 9A and 9B enter the inside of the leg structure 14, or after the transport vehicles 9A and 9B exit the inside of the leg structure 14, and it is desirable that the front and rear cameras 24 and the containers 2 loaded on the cargo beds of the transport vehicles 9A and 9B are in close proximity. For front and rear cameras 24 installed on the horizontal members 16b, the timing of the shots is when the containers 2 being loaded are in the area inside the leg structure 14, and it is desirable that the front and rear cameras 24 and the containers 2 being loaded are in close proximity.

[0051] Next, we will explain in detail how to record the appearance of container 2 at container terminal 1.

[0052] In the procedure of the embodiment of the appearance recording method illustrated in Figure 7, the appearance recording database 30 is constructed by performing the collection process S100 and the construction process S200. In the collection process S100, first, multiple image data (D1 to D4) are acquired by multiple cameras (21 to 24) (S110). Next, the crane calculation device 25 sends the multiple image data and completion report data C2 as pairs to the management calculation device 26 (S120). In the construction process S200, the management calculation device 26 adds a group of data 31 based on the received pairs of data (S210, S220), and the appearance recording database 30 is constructed. The details of each step of the collection process S100 (S110, S120) and each step of the construction process S200 (S210, S220) are described below.

[0053] The collection process S100 is executed for each of the many cranes 10 each time a container 2 is loaded or unloaded. The collection process S100 is executed by the crane calculation unit 25 of the crane 10 when a container 2 is loaded or unloaded by the crane 10 based on the loading or unloading command data C1. In other words, the collection process S100 is executed simultaneously for each crane 10 whose loading or unloading timings overlap. Because the collection process S100 is executed each time a container 2 is loaded or unloaded by the crane 10, the collection process S100 is executed at least three times for a single container 2 from the time it is received at the container terminal 1 until it is released.

[0054] Specifically, the collection process S100 for containers 2 transported to container terminal 1 by an external vehicle 9A and shipped by ship 8 is executed at the timing when the containers are loaded from the external vehicle 9A to storage lane 3 by a transfer crane 10A, when the containers are loaded from storage lane 3 to in-house vehicle 9B by a transfer crane 10A, and when the containers are loaded from in-house vehicle 9B to ship 8 by a gantry crane 10B. The collection process S100 for containers 2 transported to container terminal 1 by ship 8 and shipped by external vehicle 9A is executed at the timing when the containers are loaded from ship 8 to in-house vehicle 9B by a gantry crane 10B, when the containers are loaded from in-house vehicle 9B to storage lane 3 by a transfer crane 10A, and when the containers are loaded from storage lane 3 to external vehicle 9A by a transfer crane 10A.

[0055] In this way, the collection process S100 is executed for each of the numerous cranes 10, each time a container 2 is loaded or unloaded by a crane 10. As a result, multiple image data (D1 to D4) showing the state of container 2 can be periodically acquired from the time container 2 is brought into container terminal 1 until it is released. Therefore, this is advantageous for understanding the changes in the appearance of container 2 at container terminal 1.

[0056] In step (S110), when the crane 10 loads and unloads container 2, multiple image data (D1-D4) of the container 2 being loaded and unloaded are acquired by multiple cameras (21-24) on the crane 10, capturing the container 2 from different directions. Transfer crane 10A acquires one bottom image data D1, two side image data D2 (image data of both sides), one top image data D3, and at least one front and rear image data D4. Gantry crane 10B acquires one bottom image data D1, two side image data D2 (image data of both sides), one top image data D3, and two front and rear image data D4 (image data of the front and rear). The acquisition timing for each camera (21-24) is different, as described above.

[0057] In step (S120), after the completion of cargo handling based on the cargo handling command data C1, the crane calculation unit 25 performs data processing in which it transmits multiple image data (D1~D4) and completion report data C2 as pairs of data to the management calculation unit 26. By pairing the multiple image data (D1~D4) and the completion report data C2, the management calculation unit 26 that receives the pair of data can process them as a one-to-one relationship. Cranes 10 whose cargo handling timings overlap also overlap in the timing of transmitting their respective data. Therefore, transmitting the cargo handling command completion report data C2 and multiple image data (D1~D4) as pairs of data to the management calculation unit 26 is advantageous in maintaining a one-to-one relationship between each of the data.

[0058] Paired data refers to data in which multiple image data (D1-D4) and completion report data C2 are linked to each other. Known linking methods, such as methods using common data or methods using time data, can be used to link the data. Since multiple image data (D1-D4) are acquired each time container 2 is loaded or unloaded, the loading / unloading identification information described in the loading / unloading command data C1, which is the instruction for that loading / unloading, can be attached, and this loading / unloading identification information can be used as common data. Furthermore, since the acquisition of multiple image data (D1-D4) and the generation of completion report data C2 occur roughly at the same time, multiple image data (D1-D4) acquired within a timeframe that can be considered to be the same time can be linked to the generated completion report data C2.

[0059] The construction process S200 is executed by the management arithmetic unit 26 each time it receives a pair of data. The management arithmetic unit 26 executes the construction process S200 based on the received pair of data. If multiple pairs of data are received simultaneously, the management arithmetic unit 26 may execute multiple construction processes S200 in parallel, or it may execute multiple construction processes S200 sequentially in a predetermined order.

[0060] In step (S210), the management calculation unit 26 receives the pair of data transmitted from the crane calculation unit 25. The received pair of data is stored in the auxiliary storage unit of the management calculation unit 26, while maintaining the one-to-one relationship between multiple image data (D1 to D4) and completion report data C2.

[0061] In step (S220), the management computing unit 26 performs data processing to add a group of data 31, which contains each piece of data from the pair of received data, to the appearance record database 30. A group of data 31 is added to the appearance record database 30 each time the construction process S200 is executed. The group of data 31 contains each piece of data from the pair of data, including at least the date of implementation, crane identification information, cargo handling status, and multiple image data (D1 to D4), for the container identification information. In other words, in the group of data 31, the container identification information, date and time of implementation, crane identification information, and cargo handling status are linked to each other and to the multiple image data (D1 to D4).

[0062] The appearance record database 30 constructed using the appearance recording method described above is stored in the auxiliary storage unit of the management computing unit 26. This appearance record database 30 stores a group of data 31 for each container identification information for a large number of containers 2 that have entered and left the container terminal 1 in the past but are no longer present, and a large number of containers 2 that are currently present in the container terminal 1. More specifically, for the large number of containers 2 that have entered and left the container terminal 1 in the past but are no longer present, the appearance record database 30 contains at least three groups of data 31 for each container identification information. In addition, for the large number of containers 2 that are currently present in the container terminal 1, the appearance record database 30 contains a number of groups of data 31 for each container identification information corresponding to the number of times they have been handled.

[0063] In the entity relationship diagram (ER diagram) of the appearance record database 30 illustrated in Figure 8, there are at least three entities: a container table, a cargo handling table, and image data. The container table entities have container identification information as a primary key and management period at container terminal 1 as attributes. The cargo handling table entities have cargo handling identification information as a primary key and container identification information, execution date and time, crane identification information as attributes. Container identification information in the cargo handling table is also a foreign key. The image data entities have one bottom image data D1, two side image data D2 (image data for both sides), one top image data D3, and at least one front and rear image data D4. There is a one-to-many relationship between the container table entities and the cargo handling table entities. That is, one container identification information is linked to multiple cargo handling identification information (execution date and time, crane identification information, etc.). There is a one-to-one relationship between the cargo handling table entities and the image data entities. In other words, one cargo handling identification piece of information is associated with one set of image data (D1-D4). The entities in the cargo handling table and the entities in the image data correspond to a group of data 31.

[0064] The owner accesses the appearance record database 30 using a client computer 40 and performs a search using the container identification information of the desired container 2. The appearance record database 30 then presents a group of data 31 associated with that container identification information. If multiple groups of data 31 are associated with the container identification information, multiple groups of data 31 are presented. It is preferable that the group of data 31 presented to the owner displays a list of thumbnail images of multiple image data (D1-D4). Furthermore, if multiple groups of data 31 are presented to the owner, it is preferable that the multiple groups of data 31 are displayed chronologically.

[0065] Figure 9 shows the screen data output to the client computer 40 when the owner accesses the appearance record database 30 from the client computer 40 and enters the desired container identification information. The screen data displays the desired container identification information and the management period (existence period) at container terminal 1 at the top outside the table. The screen data is arranged in order from the top to the bottom of the table, with multiple data sets 31 arranged in chronological order of implementation date and time. The leftmost column of the table in the data set 31 displays the implementation date and time, crane identification information, and cargo handling status. The rightmost column of the table in the data set 31 displays thumbnail images of multiple image data (D1~D4). In Figure 9, the top data set 31 was collected during cargo handling by transfer crane 10A, and the bottom data set 31 was collected during cargo handling by gantry crane 10B.

[0066] As described above, according to this embodiment, the constructed appearance record database 30 records not only the appearance of containers 2 currently under the management of container terminal 1, but also the changes in the appearance of containers 2 that were under management in the past, as a set of data sets 31. Since each data set 31 includes multiple image data (D1 to D4) acquired when the container 2 is loaded or unloaded by the crane 10, it accurately represents the appearance of that container 2. Furthermore, the set of data sets 31 for each container identification information represents the changes in the appearance of the container 2 at container terminal 1. Therefore, by accessing the appearance record database 30, it is possible to trace back the actual changes in the appearance of a desired container 2 at container terminal 1 and more accurately grasp the status of ensuring the integrity of the container 2 at that container terminal 1. As a result, this greatly contributes to investigating the cause of damage to the container 2.

[0067] Furthermore, the appearance record database 30 links multiple image data (D1-D4) and completion report data C2 as a group of data 31 in a one-to-one relationship. In other words, the appearance record database 30 records the handling status of container 2 by crane 10 in more detail and adheres more closely to data integrity. Therefore, the changes in the appearance of container 2 at container terminal 1 that can be grasped using the appearance record database 30 are highly reliable. Thus, constructing a highly reliable appearance record database 30 can also serve as proof that the integrity of container 2 is ensured at container terminal 1.

[0068] A group of data 31 in the appearance record database 30 includes multiple image data, specifically bottom image data D1 showing the bottom surface 2A of container 2. Conventional cranes did not have an underside camera 21 to acquire bottom image data D1 showing the bottom surface 2A of container 2 during cargo handling. According to this embodiment, the underside camera 21 functions as a dedicated camera to acquire bottom image data D1 including the bottom surface 2A of container 2 during cargo handling of container 2, so that the bottom surface 2A of container 2 is more clearly visible in the bottom image data D1 acquired each time container 2 is handled. In addition, the underside camera 21 can reliably acquire bottom image data D1 including the bottom surface 2A of container 2 each time the bottom surface 2A of container 2 is exposed. As a result, there is no need to install a large number of cameras in the container yard 4 or the ship's cargo handling area 5 to acquire bottom image data D1, and there is no need for workers at the container terminal 1 to take photographs. Therefore, the cost at the container terminal 1 for constructing the appearance record database 30 can be significantly reduced.

[0069] Next, a modified example 1 of an embodiment of the container appearance recording method and appearance recording system 20 at a container terminal will be described.

[0070] In Modification 1 illustrated in Figure 10, a cloud server 50 is added to the configuration shown in Figure 1 above. That is, in the appearance recording system 20 of Modification 1, the appearance recording database 30 is built on the cloud server 50. Various known cloud servers can be used as the cloud server 50.

[0071] As described above, according to Modification 1, by constructing the appearance record database 30 on the cloud server 50, the convenience of access to the appearance record database 30 by the owner of container 2 is increased. Furthermore, by constructing the appearance record database 30 on an external cloud server 50, it is also possible to integrate the appearance record databases 30 of multiple container terminals 1 into one. In this way, by integrating the appearance record database 30 of each container terminal 1 into a single database, the owner of container 2 can access the integrated appearance record database 30 and understand the appearance of numerous containers 2 across multiple container terminals 1.

[0072] Next, a modified example of an embodiment of the container appearance recording method and appearance recording system 20 at a container terminal will be described.

[0073] In the modified example 2 shown in Figure 11, a gate system 60 that manages multiple gates 6 of the container terminal 1 is added to the configuration of Figure 10 described above. That is, the gate system 60 is incorporated into the appearance recording system 20 in modified example 2. Therefore, in modified example 2, a group of gate data 32 is added to the appearance recording database 30 by the gate system 60.

[0074] The gate system 60 can utilize various known systems for managing multiple gates 6. The gate system 60 includes multiple gate cameras 61 and a gate processing unit 62. The gate system 60 manages the entry and exit of visiting vehicles 9A to and from the container terminal 1, as well as the entry and exit of containers 2 transported by visiting vehicles 9A to and from the container terminal 1. The management in the gate system 60 also includes the inspection of the containers 2 transported by visiting vehicles 9A. Therefore, when a visiting vehicle 9A passes through one of the multiple gates 6 that serve as entrances and exits to the container terminal 1, the gate system 60 acquires multiple gate image data from multiple gate cameras 61, capturing the containers 2 transported by the visiting vehicle 9A from different directions.

[0075] The multiple gate cameras 61 may be cameras installed at each gate 6, or cameras held by workers at gate 6. The multiple gate image data acquired by the multiple gate cameras 61 captures the remaining surfaces of the container 2, excluding the bottom surface.

[0076] When an external vehicle 9A passes through gate 6, the gate calculation unit 62 transmits a passage completion report data C3 to the management calculation unit 26. The passage completion report data C3 includes the date and time of passage through gate 6, the container identification information of the container 2 that passed through, and the unique vehicle identification information of the external vehicle 9A that passed through.

[0077] The passage completion report data C3, illustrated in Figure 12, is generated by the gate calculation unit 62 and transmitted to the management calculation unit 26. The passage completion report data D3 contains various data regarding passage through gate 6. The passage identification information indicates a unique identification number assigned to each visitor vehicle 9A that passes through multiple gates 6. For example, it is a sequential number. The gate passage status indicates the entry or exit status (ingress or egress) to and from container terminal 1. The vehicle identification information indicates the unique vehicle identification information of the visitor vehicle 9A, for example, the vehicle number of the visitor vehicle 9A. The container identification information indicates the unique identification information of the container 2 subject to loading and unloading, for example, the container number. The passage date and time indicates the date and time when the visitor vehicle 9A actually passed through gate 6.

[0078] The gate processing unit 62 performs data processing to add a gate group data 32, which includes multiple gate image data and the respective data from the passage completion report data C3, to the appearance record database 30 based on the container identification information. Each time an outside vehicle 9A passes through gate 6 and enters container terminal 1, a gate group data 32 is added to the appearance record database 30. The gate group data 32 includes, for the container identification information, data from the passage completion report data C3, which includes at least the date and time of passage, vehicle identification information, gate passage status, and multiple gate image data. In other words, in the gate group data 32, the container identification information, date and time of passage, vehicle identification information, and gate passage loading / unloading status are linked to each other and to the multiple gate image data.

[0079] In the appearance record database 30 to which the gate group data 32 has been added, for the numerous containers 2 that have entered and exited container terminal 1 in the past but are not currently present, there are at least four data sets for each container identification information: at least three group data sets 31 and one gate group data set 32. In addition, in the appearance record database 30, for the numerous containers 2 that are currently present in container terminal 1, there are a number of group data sets 31 corresponding to the number of times they have been handled, and a number of gate group data sets 32 corresponding to their passage status, for each container identification information.

[0080] As described above, in Modification 2, by adding a group of gate data 32 to the appearance record database 30, the changes in the appearance of container 2 from its arrival to departure at container terminal 1 can be grasped more accurately. Conventionally, gate image data in the gate system 60 was only used to confirm when an outside vehicle 9A passed through gate 6. In Modification 2, the appearance record database 30 is further expanded by making effective use of this gate image data.

[0081] The image data (D1-D4) and gate image data in the embodiments and modifications 1 and 2 described above may be given a timestamp or NFT (non-fungible token) to prove the date and time of acquisition. Adding a timestamp or NFT to each image data is advantageous in improving the reliability of each image data.

[0082] On the underside 2A of container 2, numerous channel steel sections extending in the short direction of container 2 are arranged at intervals in the long direction. Damage checks of the underside 2A of container 2 using underside image data D1 allow for the detection of bending, detachment, and the presence or absence of holes in the bottom surfaces of these channel steel sections. This damage check of the underside 2A can also be performed using machine learning classification with numerous underside image data D1 as training data to determine the presence or absence of damage. Damage checks of container 2 can be performed similarly on surfaces other than the underside 2A. The determined presence or absence of damage to container 2 can then be added to the appearance record database 30.

[0083] Although embodiments of the present invention have been described above, the container terminal appearance recording method and system of the present invention are not limited to specific embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

[0084] While the present invention is suitable for recording the appearance of containers 2 at a container terminal 1, it can also be applied to warehouse facilities that serve as logistics hubs by temporarily storing cargo other than containers 2, and to manufacturing facilities that manufacture and ship multiple types of steel plates, etc. Furthermore, the crane 10 is not limited to transfer cranes 10A or gantry cranes 10B, but can be any other crane (such as a stacker crane or jib crane) except for overhead cranes that do not have a configuration equivalent to the leg structure 14, and the cargo to be handled can be anything other than containers 2. [Explanation of symbols]

[0085] 1 Container Terminal 2 containers 10 Cranes 21. Bottom camera 22 Side-mounted cameras 23 Top-mounted camera 24 Front and rear camera 25 Crane calculation device 26 Management computing unit D1 Bottom Image Data D2 Side Image Data D3 Top View Image Data D4 Front and rear image data 30. Appearance Record Database 31 Group of Data C1 Cargo handling command data C2 Completion report data C3 passage completion report data

Claims

1. In a method for recording the appearance of containers at a container terminal, in which image data of the containers acquired by multiple cameras, each of the numerous cranes, is transmitted from a crane computing device, each of the numerous cranes, to a management computing device, and recorded by the management computing device, It has a collection process and a construction process, In the collection process, which is performed each time the container is loaded or unloaded by a cranes, when the crane loads or unloads the container based on the loading / unloading command data transmitted from the management computing unit to the crane computing unit, multiple images of the container being loaded or unloaded are acquired by multiple cameras on the crane that performed the loading or unloading, capturing the container being loaded or unloaded from different directions. After the loading or unloading is completed, the crane computing unit transmits to the management computing unit, as a pair of data, the multiple images acquired by the multiple cameras, and completion report data including the date and time of the loading or unloading, the unique container identification information of the container being loaded or unloaded, and the unique crane identification information of the crane that performed the loading or unloading. A method for recording the appearance of containers in a container terminal, wherein in the construction step, an appearance record database is constructed using the pair of data collected in the collection step, the management computing device adds a group of data comprising the image data and each of the data in the pair of data to the container identification information in the pair of data, thereby constructing the appearance record database in which a large number of the group of data for a large number of containers that have entered and left the container terminal in the past but are not currently present, and a large number of the containers that are currently present in the container terminal, are stored for each of the container identification information.

2. The method for recording the appearance of a container in a container terminal according to claim 1, wherein the appearance recording database is constructed on a cloud server by the management computing device.

3. A method for recording the appearance of a container at a container terminal according to claim 1 or 2, wherein the plurality of image data in the group of data capture at least five surfaces of the container to be handled: the top surface, the bottom surface, both sides, and one of the front and back surfaces.

4. The numerous cranes include gantry cranes for loading and unloading containers between on-site vehicles and ships, and transfer cranes for loading and unloading containers between storage lanes and on-site vehicles, and between storage lanes and outside vehicles. The method for recording the appearance of containers at a container terminal according to claim 1 or 2, wherein for a large number of containers that have entered and left the container terminal in the past but are not currently present, there are at least three of the aforementioned group data for each container identification information, and for a large number of containers that are currently present at the container terminal, there are a number of the aforementioned group data corresponding to the number of times they have been handled for each container identification information.

5. When the aforementioned visiting vehicle passes through one of the multiple gates that serve as entrances and exits to the container terminal, multiple gate cameras located at the gate acquire multiple gate image data, each capturing the container being transported by the visiting vehicle from a different direction. A method for recording the appearance of a container at a container terminal according to claim 4, wherein, after the visiting vehicle passes through the gate, the gate calculation device adds to the appearance recording database a group of gate data comprising the container identification information of the container being transported by the visiting vehicle, a plurality of gate image data acquired by a plurality of gate cameras, the date and time of passage through the gate, and unique vehicle identification information of the visiting vehicle that passed through.

6. A container terminal container appearance recording system comprising multiple cameras and a crane computing device, each of which is a crane, and a management computing device that issues cargo handling command data to the crane computing device and manages the cargo handling of a large number of containers present in the container terminal, wherein image data of the containers acquired by the multiple cameras is transmitted from the crane computing device to the management computing device and recorded by the management computing device, When the crane performs cargo handling operations on the container based on cargo handling command data from the management computing device, the crane performs data processing to transmit to the management computing device, as a pair of data, the following: multiple image data obtained by multiple cameras on the crane that performed the cargo handling, showing the container being handled from different directions; and completion report data including the date and time of the cargo handling, unique container identification information of the container being handled, and unique crane identification information of the crane that performed the cargo handling. The management computing unit receives the pair of data collected each time the container is loaded or unloaded for each of the numerous cranes, and performs data processing to add a group of data comprising the image data and the respective data in the pair of data to the container identification information in the pair of data. A container appearance recording system in a container terminal in which an appearance recording database is constructed in which a large number of the aforementioned containers, each containing a large number of the aforementioned containers that have entered and left the container terminal in the past but are no longer present, and a large number of the aforementioned containers that are currently present in the container terminal, are stored for each of the aforementioned container identification information.

Images