Container terminal maintaining and managing system and method thereof

Abstract

To provide a system for maintaining and managing a container terminal and a method thereof which can grasp priority of maintenance at a container terminal in advance.SOLUTION: Relationship between an operation status of a container terminal 1 including an operation state of each facility 3 and in-coming and out-going numbers of the containers 2 and an income summary at the container terminal 1 is acquired in advance. An arithmetic processing unit 12 of a maintenance and management system 10 executes a step of, with reference to income summary of a state in which a maintenance and an entry / exit are carried out as scheduled in accordance with maintenance plan data D1 and entry and exit plan data D2 and the previously acquired relationship, carrying out data processing for predicting income summary in a state in which any maintenance is not carried out with respect to each of the maintenance processing scheduled in the maintenance plan data D1, and a step of carry out a maintenance approved based on each of predicted income summaries as an index as scheduled in the maintenance plan data D1.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a container terminal maintenance management system and method, and more particularly to a container terminal maintenance management system and method that can grasp in advance the advantages of maintenance planned at a container terminal. [Background technology]

[0002] A maintenance management system has been proposed that determines maintenance and inspection schedules based on the operating status and operating schedule of equipment in a container terminal (see Patent Document 1). In this way, the introduction of predictive maintenance (condition-based maintenance) and periodic maintenance (time-based maintenance) is being promoted in container terminals. However, container terminals have traditionally implemented periodic inspections (pre-use inspections, monthly inspections, annual inspections, etc.) in accordance with regulations such as the Industrial Safety and Health Act and the Crane Safety Regulations. Therefore, if the invention proposed in Patent Document 1 is applied to a container terminal, the costs required for maintenance at the container terminal will increase due to the combined use of conventional inspections and the newly introduced predictive maintenance and periodic maintenance.

[0003] Maintenance at a container terminal is ultimately approved and implemented by the user who operates the container terminal. Some users have a target budget for maintenance at a container terminal within a specified period, and if the budget exceeds the target, the planned maintenance may not be approved. For such users, by showing in advance the advantages of implementing maintenance that would cause the budget to exceed the target, it is possible to effectively encourage the implementation of maintenance even if the budget exceeds the target. Therefore, there is a need to predict improvements in order to understand the advantages of maintenance at a container terminal in advance. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-7597 A Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to provide a container terminal maintenance management system and method that can grasp the advantages of maintenance in a container terminal in advance. [Means for solving the problem]

[0006] The container terminal maintenance management system of the present invention for achieving the above object includes an auxiliary memory unit storing maintenance plan data in which a large number of maintenances are planned for a large number of types of equipment in the container terminal, and inbound / outbound plan data in which a large number of container inbound / outbound numbers are planned for the container terminal, an arithmetic processing unit, and an output unit, and the auxiliary memory unit is configured to store a relationship between the operating status of the container terminal, including the operating status of each of the equipment and the number of inbound / outbound containers, and the profit and loss of the container terminal, as a relationship that is grasped in advance, and the maintenance of each of the maintenance plan data is approved. When approving, the calculation processing unit executes data processing for predicting the profit and loss for each of the maintenance planned in the maintenance plan data when the operation situation is a situation in which the maintenance is not performed, based on the profit and loss in the case where the maintenance plan data and the incoming / outgoing plan data are respectively performed as scheduled, based on the maintenance plan data, the incoming / outgoing plan data, and the relationship that was input in advance, and outputs the predicted profit and loss to the output unit, and the approved maintenance is performed as scheduled in the maintenance plan data by using the respective profit and loss output from the output unit as indexes.

[0007] The container terminal maintenance management method of the present invention uses maintenance plan data in which maintenance is planned for many types of equipment in the container terminal, and inventory entry / exit plan data in which the number of containers entering and leaving the container terminal is scheduled, characterized in that the relationship between the operational status of the container terminal, including the operating status of each of the equipment and the number of containers entering and leaving the container terminal, and the profit and loss at the container terminal is grasped in advance, and when approving each of the maintenance of the maintenance plan data, a calculation device predicts the profit and loss for each of the maintenance planned in the maintenance plan data in a case where the maintenance is not performed in the operating status, based on the maintenance plan data and the inventory entry / exit plan data and the previously grasped relationship, using as a standard the profit and loss in a case where the operational status is a situation in which the maintenance plan data and the inventory entry / exit plan data are each performed as scheduled, and determines whether to approve or reject the implementation of each of the maintenance described in the maintenance plan data using each of the predicted profit and loss as an index, and performs the approved maintenance as scheduled in the maintenance plan data. Effect of the Invention

[0008] According to the present invention, by using the relationship previously grasped by regarding the maintenance plan data and the inbound / outbound plan data as the operating status, it is possible to accurately predict the profit and loss of the container terminal in various situations depending on whether or not the maintenance scheduled in the maintenance plan data is performed. This profit and loss is due to the time required to complete the number of loading and unloading operations based on the container inbound and outbound schedule in the inbound and outbound plan data (loading and unloading efficiency), and varies depending on the type and number of equipment in operation. Therefore, by predicting the profit and loss of the container terminal in various situations, such as a situation where the equipment to be maintained does not break down or a situation where it breaks down depending on whether or not the maintenance is performed, and using the predicted profit and loss as an index, it is possible to grasp in advance the advantages of each maintenance scheduled in the maintenance plan data. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram illustrating a container terminal. [Diagram 2] FIG. 1 is an explanatory diagram illustrating an embodiment of a maintenance management system for a container terminal. [Diagram 3] FIG. 2 is an explanatory diagram illustrating an example of maintenance plan data. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of maintenance plan reference data. [Diagram 5] FIG. 2 is an explanatory diagram illustrating an example of inventory planning data. [Figure 6] FIG. 1 is a flow diagram illustrating the steps of an embodiment of a method for managing security in a container terminal. [Figure 7] FIG. 1 is an explanatory diagram illustrating an example of a prediction model showing the relationship between the operational status and profit and loss of a container terminal. [Figure 8] 4 is an explanatory diagram illustrating an example of maintenance plan data in which approval or denial of each maintenance in FIG. 3 has been decided. [Figure 9] FIG. 11 is an explanatory diagram illustrating an example of user inventory data. [Figure 10] FIG. 11 is an explanatory diagram illustrating an example of service provider inventory data. [Figure 11] FIG. 11 is a flow diagram illustrating the procedure of a container terminal security management method in the first modified example. [Figure 12] FIG. 11 is an explanatory diagram illustrating an example of a target value. [Figure 13] FIG. 2 is an explanatory diagram illustrating an example of budget data. [Figure 14] FIG. 11 is a flow diagram illustrating the procedure of a container terminal security management method in the second modified example. [Figure 15] FIG. 11 is an explanatory diagram illustrating an example of budget data in the second modification example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A container terminal maintenance management system and method according to the present invention will be described below based on an embodiment shown in the drawings.

[0011] First, a container terminal 1 illustrated in FIG. 1 will be described.

[0012] The container terminal 1 serves as a logistics hub by temporarily storing containers 2. Many types of equipment 3 are operated in the container terminal 1. The equipment 3 is composed of a single or multiple parts 4. The equipment 3 is, for example, various known cranes and on-site chassis that handle the containers 2. The equipment 3 is, for example, power supply equipment that supplies power to reefer containers, lighting equipment installed in various places in the container terminal 1, and gate devices installed at the entrances and exits of the container terminal 1. The equipment 3 may also include storage areas such as storage lanes.

[0013] In the container terminal 1, an inventory of parts 4 used for maintenance work in each facility 3 is managed. The inventory of parts 4 is stored, for example, in a storehouse inside the administration building 7 or in containers 2a that are not shipped from the container terminal 1. That is, in the container terminal 1, there are containers 2 that are treated as baggage and containers 2a that are not treated as baggage and in which the inventory of each part 4 is stored. The containers 2a are transported by equipment 3 such as cranes and on-site chassis to the location where maintenance is to be performed. Therefore, the containers 2a are scattered throughout the container terminal 1.

[0014] Containers 2 are brought into the container terminal 1 from the outside by ships 5 or foreign chassis 6, and are taken out from the container terminal 1 to the outside. Therefore, the number of containers 2 entering and leaving the container terminal 1 depends on the arrival and departure status of the ships 5 and foreign chassis 6.

[0015] A maintenance management system 10 and a cargo handling management system 11 of this embodiment are installed in the management building 7. Details of each system will be described later, but the maintenance management system 10 manages maintenance at the container terminal 1, and the cargo handling management system 11 manages the cargo handling of containers 2 at the container terminal 1.

[0016] The container terminal 1 is managed and operated by a user. The user is an organization that manages and operates the container terminal 1. The same user may manage and operate multiple different container terminals 1, or multiple different users may manage and operate each of the multiple container terminals 1 individually. Various services (such as manufacturing and selling the equipment 3 and preparing for maintenance of the equipment 3) at the container terminal 1 are provided by a service provider. The service provider is an organization that carries out the manufacturing and selling of the equipment 3. The maintenance management system 10 and the cargo handling management system 11 are manufactured and sold by the service provider. Maintenance of the container terminal 1 is approved by the user and carried out by a maintenance worker who is requested by the user. The maintenance workers are composed of personnel from a maintenance company with which the user has a contract, personnel organized by the service provider, and personnel from a manufacturer that manufactures and sells each part 4. For example, in inspection, the maintenance workers are composed of personnel from a maintenance company, and in post-maintenance, the maintenance workers are composed of personnel from a maintenance company, a service provider, and a manufacturer.

[0017] Next, a maintenance management system 10 illustrated in FIG. 2 will be described.

[0018] A container terminal maintenance management method is implemented using an embodiment of the maintenance management system 10. The maintenance management system 10 and the maintenance management method are used by a user who manages and operates the container terminal 1 to carry out maintenance at the container terminal 1. That is, according to this embodiment, the user uses the maintenance plan data D1 illustrated in FIG. 3 and the loading / unloading plan data D2 illustrated in FIG. 5, which will be described later, to decide whether to approve or disapprove each maintenance scheduled in the maintenance plan data D1. At the container terminal 1, the approved maintenance is carried out as scheduled in the maintenance plan data D1.

[0019] Maintenance at the container terminal 1 includes inspection, preventive maintenance (predictive maintenance, periodic maintenance), post-fault maintenance, corrective maintenance, etc. Inspections are carried out based on predetermined rules such as the Industrial Safety and Health Act and the Crane Safety Regulations. Inspections include periodic inspections such as pre-use inspections, monthly inspections, and annual inspections, as well as post-disaster (earthquake) inspections. Preventive maintenance includes periodic maintenance (time-based maintenance) and predictive maintenance (condition-based maintenance). Periodic maintenance is carried out when a predetermined period or number of uses (for example, 3 months, 1 year, 5 years, or 100,000 loading / unloading operations) has elapsed for each piece of equipment 3. Predictive maintenance is carried out by monitoring the condition of each piece of equipment 3, predicting signs of failure, and carrying out the maintenance before the failure occurs. Post-fault maintenance is carried out unexpectedly for equipment 3 that has actually failed. Corrective maintenance is design improvement or equipment improvement such as preventing deterioration of equipment 3 or repairing deterioration in order to maintain the performance of equipment 3, and is carried out in conjunction with other maintenance such as periodic maintenance, predictive maintenance, and corrective maintenance, or alone.

[0020] The maintenance management system 10 is configured with a computer, and various data are input and stored, and data processing is performed using these data. The maintenance management system 10 can use various known computers. As the computer, various known servers such as physical servers and virtual servers can also be used. The maintenance management system 10 may be installed in the container terminal 1, or may be installed outside the container terminal 1. The maintenance management system 10 has a processing unit (CPU) 12, a main storage unit (memory) 13, an auxiliary storage unit (e.g., HDD) 14, an input unit (keyboard, mouse) 15, and an output unit (display) 16. The auxiliary storage unit 14 stores maintenance plan data D1 illustrated in FIG. 3 and warehousing / receiving data D2 illustrated in FIG. 5, which will be described later. Although not shown in the figure, the auxiliary storage unit 14 also stores maintenance plan reference data D0, user inventory data D3, and service provider inventory data D4 illustrated in FIG. 4, FIG. 9, and FIG. 10, which will be described later.

[0021] The maintenance management system 10 manages the maintenance of each facility 3 in the container terminal 1. The maintenance management system 10 creates maintenance plan data D1 and executes data processing to carry out, as scheduled, the maintenance items approved by the user from among the maintenance items described in the created maintenance plan data D1. Details of the maintenance plan data D1 and the method for creating it will be described later.

[0022] The cargo handling management system 11 manages the containers 2 and each facility 3 in the container terminal 1. The cargo handling management system 11 may use a known computer, such as a terminal operation system. The cargo handling management system 11 creates warehousing / receiving plan data D2 by using various known methods for planning the warehousing / receiving of containers 2.

[0023] The maintenance management system 10 and the cargo handling management system 11 are connected to each other so that they can communicate with each other. The maintenance management system 10 and the cargo handling management system 11 may be connected to each other via the same network (LAN), may be connected to each other via a wide area network (WAN) in which multiple networks are connected to each other via an Internet router, or may be connected to each other via the Internet. It is preferable that the maintenance management system 10 and the cargo handling management system 11 are separate computers, but they can also be integrated into a single computer.

[0024] The maintenance plan data D1 shown in Fig. 3 is created by the maintenance management system 10 and stored in the auxiliary storage unit 14. The maintenance plan data D1 includes plans for maintenance of many types of facilities 3 in the container terminal 1. While the actual maintenance plan data D1 includes plans for implementation dates and implementation periods several years in the future, Fig. 3 shows a schedule of maintenance that includes implementation dates and implementation periods within one month.

[0025] In more detail, the maintenance plan data D1 accumulates the maintenance schedule for each piece of equipment 3 (Crane No. 1, Crane No. 2, . . ., Crane No. n, . . ., In-house chassis No. m, . . ., Lighting device No. i, . . ., Storage lane No. j, . . .) listed in the leftmost column of the table in FIG. 3. The maintenance schedule includes the contents of each maintenance (inspection, periodic maintenance, predictive maintenance, corrective maintenance, etc.), the implementation date and implementation period (YYYY / MM / DD, etc.), and the planned end of use date (YYYY / MM / DD) of the equipment 3 or part 4 to be maintained. The details of the maintenance contents are written in parentheses in FIG. 3, and it is sufficient to understand the work contents when the maintenance is performed. For example, the name of the equipment 3 or part 4 to be maintained is written. The contents of the inspection are different for each preset period (for example, before use, monthly (one month), annual (one year)), so the period is written. For details related to predictive maintenance, scheduled maintenance, corrective maintenance, and corrective maintenance, the name of the equipment 3 or part 4 that will be the target of the work is listed. The planned end of service life date is not listed for maintenance other than predictive maintenance and scheduled maintenance, as indicated by "-" in Figure 3. The implementation date and implementation period for each maintenance item are listed as "YYYY / MM / DD" or "YYYY / MM / DD~YYYY / MM / DD," but in reality, the implementation date and the start and end dates of the implementation period are listed.

[0026] The schedule for each maintenance in the maintenance plan data D1 is determined by the maintenance management system 10, but may also be determined manually by a user or a service provider, or a combination of determination by the maintenance management system 10 and manual determination may be used. For example, schedules for inspection, predictive maintenance, and periodic maintenance are determined by the maintenance management system 10 according to previously set criteria for implementation dates and implementation periods. The criteria for implementation dates and implementation periods can be set arbitrarily depending on each type of maintenance. In addition, schedules for corrective maintenance and corrective maintenance are determined by manually inputting equipment 3 and parts 4 that have broken down or are scheduled to be improved into the maintenance management system 10.

[0027] The maintenance plan reference data D0 illustrated in FIG. 4 is used to determine schedules for inspection, predictive maintenance, and periodic maintenance. The maintenance plan reference data D0 is stored in the auxiliary storage unit 14 of the maintenance management system 10. The maintenance plan reference data D0 has thresholds left blank for a period only the first time, and is created by manually inputting these blanks using the input unit 15 of the maintenance management system 10. Input into these blanks is basically performed by the user, but predictive maintenance and periodic maintenance may be performed by a service provider. The maintenance plan reference data D0 accumulates the maintenance content, the period and threshold as a standard for each part 4 of each facility 3. The period and threshold of the maintenance plan reference data D0 can be changed as appropriate.

[0028] In detail, the maintenance plan standard data D0 is classified into inspection, predictive maintenance, and periodic maintenance for the equipment 3 (crane, yard chassis, lighting equipment, ..., storage lane, etc.) and parts 4 (wire rope, motor, ..., etc.) in the two left columns of the table in Fig. 4, and the period and threshold (before use, monthly (1 month), annually (1 year), number of loading and unloading times: XX times, etc.) for each maintenance content are accumulated. The period for inspection is based on predetermined rules such as the Industrial Safety and Health Act and the Crane Safety Regulations. The threshold for periodic maintenance is different for each part 4, and for example, the number of loading and unloading times is used for wire ropes, and the running time is used for motors of running gears. Regarding the threshold for periodic maintenance, values ​​based on the knowledge that users and service providers have cultivated over the years can be used based on the values ​​recommended by the manufacturers who manufacture and sell the parts 4. The threshold for predictive maintenance can be set arbitrarily. Regarding the threshold value of predictive maintenance, for example, if the deterioration level of part 4 when it is new is 0 and the deterioration level of part 4 when it has reached its usage limit is 100, then the deterioration level is approximately 80. In other words, the deterioration level of equipment 3 or part 4 used in equipment 3 is predicted based on the operating status of that equipment 3, and the date and time when the predicted deterioration level is predicted to exceed the set threshold becomes the planned usage limit date.

[0029] For inspection, it is necessary to set a period, but for periodic maintenance and predictive maintenance, the deadline and threshold can be set arbitrarily. That is, the user can select whether to perform only periodic maintenance, only predictive maintenance, both periodic maintenance and predictive maintenance, or neither, as the maintenance of each facility 3 in accordance with the inspection. To operate the container terminal 1 more stably, it is desirable to perform both periodic maintenance and predictive maintenance in addition to inspection, but performing both periodic maintenance and predictive maintenance increases the cost required for operating the container terminal 1. Therefore, each maintenance scheduled in the maintenance plan data D1 includes inspection, corrective maintenance, and corrective maintenance, and it is preferable to select in advance before creating the maintenance plan data D1 whether to include predictive maintenance and / or periodic maintenance in each maintenance. This allows the user to select the content of the maintenance, increases the degree of freedom of maintenance in the container terminal 1, and allows the user to create a maintenance plan that takes into account the operating costs of the user.

[0030] The schedule for predictive maintenance and periodic maintenance using the maintenance plan reference data D0 is determined, for example, as follows. First, the operating status of each facility 3 (or part 4) is acquired. The operating status is acquired by a sensor installed in each facility 3 of the container terminal 1, accumulated in the cargo handling management system 11, and transmitted to the maintenance management system 10. If each sensor is electrically connected to the maintenance management system 10, the operating status may be acquired directly by the maintenance management system 10 without going through the cargo handling management system 11. The operating status may be finally stored in the auxiliary storage unit 14 of the maintenance management system 10, or may be accumulated in a computer other than the cargo handling management system 11 using each sensor and transmitted to the maintenance management system 10. The operating status may also be manually input to the maintenance management system 10. To acquire the operating status manually, a daily work report at the container terminal 1 and an inspection result of each facility 3 are used. Next, the maintenance management system 10 determines a schedule for predictive maintenance and periodic maintenance based on the acquired operating status of each facility 3 and the maintenance plan reference data D0. Specifically, the maintenance management system 10 predicts the planned end of life date of the equipment 3 or the part 4 based on the acquired operating state and the period and threshold of the maintenance plan reference data D0, and sets the implementation date and implementation period before the predicted end of life date. Various known prediction models using machine learning can be used to set the schedule for predictive maintenance and periodic maintenance.

[0031] As described above, the maintenance plan data D1 describes the schedule for maintenance of each piece of equipment 3 in the container terminal 1. The equipment 3 for which maintenance has been performed cannot operate during the period in which the maintenance is being performed. In other words, the maintenance plan data D1 can be considered to indicate the operating status of each piece of equipment 3 on a daily basis in the container terminal 1 in the future.

[0032] 5 is created by the cargo handling management system 11, and is used for managing the containers 2 in the cargo handling management system 11, and is also stored in the auxiliary storage unit 14 of the maintenance management system 10. In the cargo handling plan data D2, the number of containers 2 to be loaded and unloaded from the container terminal 1 is scheduled for each day.

[0033] More specifically, the warehousing / returning plan data D2 is expressed as a frequency distribution with the horizontal axis representing date and time and the vertical axis representing the number of warehousing / returns. In FIG. 5, the open bars indicate the number of warehousing / returns by ship 5, and the diagonal bars indicate the number of warehousing / returns by external chassis 6. The number of warehousing / returns is expressed as a plus for the entry of containers 2 into the container terminal 1 and a minus for the departure of containers 2 from the container terminal 1. The total number of warehousing / returns per day is roughly proportional to the number of cargo handling operations at the container terminal 1 (the number of operations by container handling equipment 3 such as cranes). In other words, the warehousing / returning plan data D2 represents the number of cargo handling operations (the number of operations by cargo handling equipment such as cranes) predicted for each day at the container terminal 1.

[0034] The number of incoming and outgoing cargoes per day depends on the arrival and departure status of ships 5 and foreign chassis 6, and increases as the number of arrivals and departures increases and decreases as the number of arrivals and departures decreases. The number of incoming and outgoing cargoes depends mainly on the arrival and departure status of ships 5. This number of incoming and outgoing cargoes is predicted by the cargo handling management system 11 based on the arrival and departure status of ships 5 and foreign chassis 6. The incoming and outgoing cargoes planning data D2 is not limited to frequency distribution, and may be, for example, management data that accumulates various data related to the management of containers 2 at the container terminal 1.

[0035] Next, a method for maintaining and managing the container terminal will be described.

[0036] FIG. 6 shows an example of the procedure of an embodiment of the maintenance management method. In this procedure, first, the relationship between the operating status of the container terminal 1, including the operating status of each facility 3 and the number of containers 2 entering and leaving the warehouse, and the profit and loss at the container terminal 1 is acquired in advance (S110). Next, the calculation processing unit 12 predicts the profit and loss for each maintenance in the maintenance plan data D1 based on each data and the previously acquired relationship (S120). Next, approval or rejection of each maintenance is determined using each predicted profit and loss as an index (S130). Finally, the approved maintenance is performed as scheduled in the maintenance plan data D1 (S140). The contents of each step (S110 to S140) are described in detail below.

[0037] In step (S110), the relationship between the operational status of the container terminal 1, including the operating status of each piece of equipment 3 and the number of containers 2 entering and leaving the warehouse, and the profit and loss at the container terminal 1 is acquired in advance during the course of operating the container terminal 1. This step (S110) can be executed at any timing before deciding whether to approve or reject each piece of maintenance in the maintenance plan data D1. Also, this step (S110) can be omitted because once the relationship between the operational status and the profit and loss is acquired and the relationship is stored in the auxiliary storage unit 14 of the maintenance management system 10, the stored relationship can be used from the next time onwards.

[0038] The profit and loss indicates the degree of profit and loss (the degree of loss against the standard) based on the situation where the loading and unloading plan data D2 is performed as scheduled. The loading and unloading plan data D2 indicates an ideal operating situation where there is no delay in the arrival and departure of the ships 5 and the external chassis 6, and each piece of equipment 3 in the container terminal 1 can be used. In the container terminal 1, all pieces of equipment 3 may not be available due to the implementation of maintenance. Therefore, the actual profit and loss in the container terminal 1 is generally a loss against the loading and unloading plan data D2. The longer it takes to complete the number of loading and unloading operations based on the loading and unloading data D2 (the lower the loading and unloading efficiency in the container terminal 1), the larger the loss, and the shorter the time it takes to complete the number of loading and unloading operations, the smaller the loss. The unit of time and date for the profit and loss can be set arbitrarily, for example, daily, weekly, monthly, etc.

[0039] Profit and loss can be expressed as the difference between the time required to complete the same number of cargo handling operations in a standard situation and the time required to complete the same number of cargo handling operations in a specified situation. Profit and loss can also be expressed as the difference between the cargo handling efficiency in a standard situation and the cargo handling efficiency in a specified situation for the same period. Furthermore, profit and loss can be converted into a monetary value. The profit and loss amount can include various types of amounts and can be set appropriately. Examples of the profit and loss amount include the mooring fee of the ship 5 and the cost required for the foreign chassis 6 to temporarily store the container 2 in a temporary storage facility outside the container terminal 1 and to enter the temporarily stored container 2 into the container terminal 1. The temporary storage facility is a facility installed near the container terminal 1 to ease the congestion of the foreign chassis 6 that cannot enter the container terminal 1 due to a delay in work at the container terminal 1. The container 2 temporarily stored in the temporary storage facility needs to be stored in the container terminal 1 using another chassis, which incurs the transportation cost of the other chassis and the maintenance and management cost of the temporary storage facility. Furthermore, the profit and loss amount can be calculated by converting a situation that cannot actually be calculated into a profit and loss amount, for example, a loss in reliability due to irregular operation of the ship 5 can be converted into a profit and loss amount. In this way, it is preferable to express profit and loss in monetary terms, and for example, the time required to complete the number of cargo handling operations or the difference in cargo handling efficiency can be converted into a monetary value. Expressing profit and loss in monetary terms is more advantageous in understanding the cost-effectiveness of maintenance. Note that the profit and loss may include, but does not have to include, the costs required for maintenance scheduled in the maintenance plan data D1.

[0040] Profit and loss varies depending on the operational status of the container terminal 1. More specifically, profit and loss varies in a complex relationship between the operational status of each piece of equipment 3 at the container terminal 1 and the number of containers 2 being loaded and unloaded. For a given number of containers 2 being loaded and unloaded (number of loading and unloading operations), the fewer the number of operable pieces of equipment 3, the greater the loss, and vice versa. In this way, profit and loss at the container terminal 1 is intricately influenced by the operational status of the container terminal 1, which includes the operational status of each piece of equipment 3 and the number of containers 2 being loaded and unloaded.

[0041] The prediction model 18 illustrated in FIG. 7 is constructed by machine learning using teacher data 19, and represents the relationship between the operation status and profit and loss of the container terminal 1. The prediction model 18 is a type of computer program that predicts the profit and loss of the container terminal 1 based on the operation status of the container terminal 1. Various known machine learning techniques can be used to construct the prediction model 18. Examples of machine learning algorithms include logistic regression, support vector machine, decision tree, random forest, neural network (convolutional neural network, recurrent neural network, residual network, etc.), simple Bayes, k-nearest neighbor method, etc. Also, ensemble learning using multiple algorithms is exemplified.

[0042] In constructing the prediction model 18, teacher data 19 is used, and as the teacher data 19, either labeled or unlabeled teacher data can be used. As the labeled teacher data 19, for example, an influence degree set for each facility 3 is used. The influence degree indicates the degree of influence on the change in the time required to complete the number of loading and unloading operations at the container terminal 1 (loading and unloading efficiency). In a situation where a facility 3 with a low influence degree is not in operation, the time required to complete the number of loading and unloading operations at the container terminal 1 (loading and unloading efficiency) changes little, but in a situation where a facility 3 with a high influence degree is not in operation, the time required to complete the number of loading and unloading operations at the container terminal 1 (loading and unloading efficiency) changes greatly (decreases greatly). Facilities 3 with a high influence degree are, for example, cranes and storage lanes. The degree of influence degree is roughly grasped by the huge amount of data obtained in the course of the operation of the container terminal 1 accumulated by users and service providers, the accumulation of results of experiments, tests, computer simulations, etc. Therefore, the impact level set for each facility 3 using the above-mentioned knowledge of users and service providers can be used as labeled teacher data 19. As the unlabeled teacher data 19, the huge amount of data obtained in the course of operation of the container terminal 1 accumulated by the above-mentioned users and service providers, the accumulated results of experiments, tests, computer simulations, etc. are used. When expressing profit and loss in monetary terms, it is advisable to convert the change in the time required to complete the number of loading and unloading operations at the container terminal 1 (loading and unloading efficiency) into a monetary value in the teacher data 19. In this way, the prediction model 18 constructed by machine learning using the teacher data 19 predicts the change in the time required to complete the number of loading and unloading operations at the container terminal 1 (loading and unloading efficiency) according to the operation status as profit and loss.

[0043] The profit and loss predicted by the prediction model 18 is influenced in a complex manner by the operating status of the container terminal 1 according to the operating status of each facility 3 and the number of containers 2 entering and leaving the warehouse. The constructed prediction model 18 is constructed by machine learning using training data 19 conforming to the actual situation of the container terminal 1, so the relationship between the operating status of the container terminal 1 and the profit and loss is linked, and the influence of the operating status of the container terminal 1 on the profit and loss is in a state where it has been analyzed and evaluated. Therefore, each profit and loss output from the prediction model 18 to which different operating statuses are inputted represents with high accuracy the change in the time required to complete the number of loading and unloading operations (loading and unloading efficiency) in each case of the degree of difference in the operating status of the container terminal 1 due to differences in the operating status of each facility 3 and the number of containers 2 entering and leaving the warehouse.

[0044] The relationship between the operational status and profit and loss of the container terminal 1 is not limited to the prediction model 18 constructed by machine learning. The relationship can also be obtained by a simulation in which the container terminal 1 is modeled.

[0045] In step (S120), the calculation processing unit 12 executes data processing to predict profit and loss in the case where the operation status is a situation where each maintenance in the maintenance plan data D1 is not performed, based on the previously acquired relationship (prediction model 18) between the maintenance plan data D1 and the incoming / outgoing plan data D2. Specifically, the calculation processing unit 12 predicts profit and loss by regarding each data of the maintenance plan data D1 and the incoming / outgoing plan data D2 as the operation status of the container terminal 1. In predicting profit and loss, the calculation processing unit 12 predicts profit and loss in the case where the operation status is a situation where each maintenance scheduled in the maintenance plan data D1 is not performed, based on the profit and loss in the case where the operation status is a situation where each maintenance is performed as scheduled in the maintenance plan data D1.

[0046] The situation in which maintenance is not performed differs depending on the type of maintenance. Since inspection is always performed, there is no situation in which inspection is not performed. In a situation in which predictive maintenance or periodic maintenance is not performed, there is a high possibility that the equipment 3 targeted by the predictive maintenance or periodic maintenance will break down on the planned end of service life date. Therefore, in a situation in which predictive maintenance or periodic maintenance is not performed, a situation in which the target equipment 3 breaks down on the planned end of service life date in the maintenance plan data D1 is used as the operation situation. In an operation situation in which predictive maintenance or periodic maintenance is not performed, corrective maintenance is scheduled and performed after the target equipment 3 breaks down on the planned end of service life date. Therefore, the period in which the equipment 3 targeted by the maintenance cannot be used in an operation situation in which predictive maintenance or periodic maintenance is not performed is longer than the period in which the equipment 3 targeted by the maintenance cannot be used in an operation situation in which predictive maintenance or periodic maintenance is performed. In this way, the profit and loss predicted in a situation in which predictive maintenance or periodic maintenance is not performed varies depending on the equipment 3 targeted by the predictive maintenance or periodic maintenance, but the loss is larger than the profit and loss predicted in a situation in which predictive maintenance or periodic maintenance is performed.

[0047] In a situation where corrective maintenance is not performed, the broken equipment 3 cannot be operated. Therefore, in a situation where corrective maintenance is not performed, a situation where the target equipment 3 is not in operation is used as the operating situation. Therefore, the profit and loss predicted in a situation where corrective maintenance is not performed will be larger than the profit and loss predicted in a situation where corrective maintenance is performed.

[0048] Even if corrective maintenance is not performed, there is a low possibility of a sudden breakdown occurring in the equipment 3 that is the target of corrective maintenance. A situation in which corrective maintenance is not performed is used as an operating situation in which the target equipment 3 does not break down, just like a situation in which regular maintenance is not performed. In other words, performing corrective maintenance prevents the target equipment 3 from operating, and not performing corrective maintenance allows the target equipment 3 to operate, so the loss predicted in a situation in which corrective maintenance is not performed is smaller than the loss predicted in a situation in which corrective maintenance is performed.

[0049] As described above, the circumstances in which each maintenance item in the maintenance plan data D1 is not performed vary depending on the type of maintenance, and the profit and loss predicted in each situation also differs. Since inspections are required by rule, there is no need to predict profit and loss. Therefore, in this step (S120), it is advisable to predict profit and loss for the remaining maintenance items excluding inspections from the maintenance plan data D1. Also, in this step (S120), it is possible to predict only profit and loss for predictive maintenance and periodic maintenance, for which profit and loss changes more significantly between a situation in which maintenance is not performed and a situation in which maintenance is performed.

[0050] In step (S130), the predicted profit and loss is used as an index to determine whether to approve or reject each maintenance item in the maintenance plan data D1. Specifically, the maintenance plan data D1a shown in FIG. 8, which will be described later, is output to the output unit 16 of the maintenance management system 10. The output maintenance plan data D1a has a field for inputting approval or rejection of each maintenance item. Approval or rejection is input into that field by the input unit 15.

[0051] The maintenance plan data D1a illustrated in FIG. 8 includes the profit and loss predicted in the above-mentioned step (S120) for each maintenance of the maintenance plan data D1 in FIG. 3. The maintenance plan data D1a also reflects the results of step (S130). In detail, the maintenance plan data D1a includes the maintenance schedule for each piece of equipment 3 in the leftmost column of the table in FIG. 8, the profit and loss predicted by the prediction model 18 in a situation where the maintenance is not performed, and approval or rejection. In FIG. 8, each profit and loss is omitted by "···", but the amount converted from the profit and loss is actually listed. The profit and loss due to the breakdown of the equipment 3 in a situation where maintenance is not performed is the profit and loss that occurs until the equipment 3 becomes usable.

[0052] In step (S140), the maintenance approved in the maintenance plan data D1a is carried out according to the schedule in the maintenance plan data D1. The implementation of the maintenance includes preparations that are made before the implementation of the maintenance. In the preparations, the maintenance management system 10 procures the parts 4 and maintenance workers related to the maintenance.

[0053] To describe the preparation in detail, the parts 4 are procured in the following procedure. First, the arithmetic processing unit 12 executes data processing to identify the parts 4 required for the approved maintenance and to check the stock of the identified parts 4. Next, the arithmetic processing unit 12 executes data processing to procure the parts 4 using electronic commerce (EC). The maintenance contents of the maintenance plan data D1a are used to identify the parts 4. The stock of the parts 4 is checked using user parts data D3 exemplified in FIG. 9 and service provider parts data D4 exemplified in FIG. 10, which will be described later. Various known electronic commerce such as BtoB-EC and BtoC-EC can be used for the electronic commerce. The data processing to procure the parts 4 by the arithmetic processing unit 12 is not limited to the one using electronic commerce. For example, the data processing may be data processing in which the arithmetic processing unit 12 creates an estimate or purchase order and outputs the created estimate or purchase order to the output unit 16.

[0054] The user parts data D3 illustrated in FIG. 9 is stored in the auxiliary memory unit 14 of the maintenance management system 10. The user parts data D3 has the inventory status of many types of parts 4 held by the user. In detail, the user parts data D3 accumulates the inventory quantity and storage location of each part 4 (motor, ..., wire rope, ...) listed in the leftmost column of the table in FIG. 9. In FIG. 9, some parts 4, inventory quantity, and storage locations are abbreviated with "...", but in reality the name, quantity, and location coordinates (or address in the container terminal 1) of the parts 4 are listed.

[0055] The stock quantity of the user parts data D3 may be directly input by the user to the maintenance management system 10 through the input unit 15 based on the history of arrival and use of the parts 4, or may be reflected by the calculation processing unit 12 in the results of maintenance work based on the maintenance plan data D1a or the results of electronic commerce. Some parts 4 may be stored for a long period of time, and the durability and performance of the parts 4 may be reduced. Therefore, it is advisable to record the storage period in the user parts data D3. To record the storage period, a unique identification number that the parts 4 have is required, so the identification number is also recorded. By recording the storage period in the user parts data D3, it becomes possible to select parts 4 with a longer storage period as parts to be used for maintenance, and it is possible to effectively avoid prolonged storage periods.

[0056] The storage location can be directly input by the user to the maintenance management system 10 through the input unit 15, or can be automatically acquired by the arithmetic processing unit 12. In the container terminal 1 of FIG. 1 described above, the parts 4 owned by the user are stored in the container 2b in which the inventory of each part 4 is stored, in addition to the storage in the management building 7, without being treated as luggage. The location of the parts 4 stored in the storage in the management building 7 can be easily identified. In order to identify the location of the container 2b by the arithmetic processing unit 12, various known radio wave positioning devices such as the global navigation satellite system (GNSS), beacon positioning, ultra-wideband (UWB) positioning, and indoor positioning systems (IPS) such as wireless LAN positioning according to the IEEE802.11 standard, and RFID can be used. For example, a pallet with a built-in antenna of the global navigation satellite system is used, and the container 2b is stored on this pallet. If the parts 4 stored in the container 2b are identified, the arithmetic processing unit 12 can automatically acquire the storage location of the parts 4 by acquiring the position coordinates received by the antenna. The container 2b containing the parts 4 will move when maintenance is performed, and it would be time-consuming for the user to directly input the location of the parts 4 one by one into the maintenance management system 10. By having the calculation processing unit 12 automatically acquire the storage location of the parts 4 using a radio wave positioning device, it becomes possible to constantly grasp the storage location of the parts 4 in the container terminal 1. This allows the parts 4 to be quickly prepared when maintenance is performed.

[0057] The service provider parts data D4 illustrated in Fig. 10 is stored in the auxiliary memory unit 14 of the maintenance management system 10. The service provider parts data D4 has the inventory status of many types of parts 4 held by the service provider. In detail, the service provider parts data D4 accumulates the stock quantity, delivery date, and cost for each of the parts 4 (motor, ..., wire rope, ...) listed in the leftmost column of the table in Fig. 10. In Fig. 10, some of the parts 4, stock quantity, delivery date, and cost are abbreviated with "...", but in reality the name, quantity, period, and amount of the part 4 are listed.

[0058] The stock quantity, delivery date, and cost in the parts data D4 are directly input by the service provider into the maintenance management system 10 using the input unit 15. The delivery date and cost are those when the parts 4 are delivered from the service provider to the user. The parts 4 include general-purpose parts 4 manufactured and sold by manufacturers, as well as specialized parts 4 that are processed from those general-purpose parts 4. The delivery date and cost of specialized parts 4 take into account the procurement situation of general-purpose parts 4 from the manufacturer. Therefore, for specialized parts 4, the delivery date and cost may be listed even if they are not in stock.

[0059] In addition to the above-mentioned user parts data D3 and service provider parts data D4, manufacturer parts data having the inventory status of parts 4 held by a manufacturer can also be used to check the inventory of parts 4. The manufacturer parts data accumulates the inventory quantity, delivery time, and cost of general-purpose parts 4 held by a manufacturer.

[0060] In electronic commerce, quotations and orders for parts 4 are output to the output unit 16 of the maintenance management system 10, and the user inputs them through the input unit 15, thereby trading parts 4. External EC sites can also be used in electronic commerce. With regard to quotations and orders for parts 4 in electronic commerce, multiple quotations can be output depending on the stock situation. For example, the cost of parts 4 held by a manufacturer may be cheaper than the cost of parts 4 held by a service provider, but the delivery date of parts 4 held by the service provider may be earlier than the delivery date of parts 4 held by the manufacturer. In such a case, both quotations can be presented to the user.

[0061] The procurement of maintenance workers is performed in the following procedure. First, the calculation processing unit 12 executes data processing to identify the number of maintenance workers required for the approved maintenance work. Next, the calculation processing unit 12 executes data processing to notify a maintenance worker dispatch company that the identified number of service personnel will be secured. The maintenance content in the maintenance plan data D1a is used to identify the number of people. A publicly known communication means such as e-mail can be used to notify the dispatch company.

[0062] As described above, according to this embodiment, the maintenance plan data D1 and the loading / unloading plan data D2 are regarded as the operating status of the container terminal 1, and the prediction model 18 showing the relationship between the operating status and profit and loss obtained in advance is used, so that the profit and loss in the container terminal 1 in various situations depending on whether or not the maintenance scheduled in the maintenance plan data D1 is performed can be accurately predicted. This profit and loss is caused by the time required to complete the number of loading and unloading operations of the container 2 in the container terminal 1 (loading and unloading efficiency), and varies depending on the type and number of the equipment 3 in operation. Therefore, by predicting the profit and loss of the container terminal 1 in various situations, such as a situation in which the equipment 3 to be maintained does not break down or a situation in which it breaks down depending on whether or not the maintenance is performed, and using the predicted profit and loss as an index, the advantages of each maintenance scheduled in the maintenance plan data D1 can be grasped in advance. As a result, when the choice of performing the maintenance is advantageous, the maintenance is approved and performed as scheduled, so that losses that may be predicted in a situation in which the maintenance is not performed can be effectively avoided.

[0063] The profit and loss for each predicted maintenance will generally be a loss compared to the standard. This loss can be regarded as the profit gained by implementing the planned maintenance and avoiding a breakdown in the equipment 3 that is the target of that maintenance. Therefore, by using the loss as an index, even if the introduction of predictive maintenance exceeds the user's desired budget, the validity of the cost-effectiveness of the excess budget can be judged, which greatly contributes to risk avoidance.

[0064] In addition, by providing an option to reject scheduled maintenance and not carry out the maintenance as scheduled in the maintenance plan data D1, the degree of freedom in scheduling maintenance at the container terminal 1 is increased. For example, a crane used at the container terminal 1 has multiple motors for the traveling gear. Even if one of the multiple motors suddenly breaks down, the crane does not stop traveling, and although the loading and unloading efficiency is reduced compared to a normal state, it does not mean that the container 2 cannot be loaded or unloaded at all. Therefore, depending on the loading and unloading status of the container 2, it may be advantageous to use the crane that is the target of maintenance without carrying out the maintenance as scheduled in order to improve the loading and unloading efficiency at the container terminal 1. According to this embodiment, the profit and loss predicted by the prediction model 18 is in accordance with the actual situation of the container terminal 1. Therefore, when predictive maintenance is scheduled for the motor of the traveling gear of the crane, the profit and loss predicted for the predictive maintenance is estimated to be small. In this way, it is possible to determine whether or not maintenance is to be carried out based on the profit and loss at the container terminal 1, which greatly contributes to the management of the container terminal 1.

[0065] The rejected maintenance may be carried out by changing the schedule described in the maintenance plan data D1 in FIG. 3 described above. The schedule of the rejected maintenance may be changed by the user as appropriate. However, depending on the type of maintenance, there may be cases where the schedule cannot be changed, and the maintenance for which the schedule cannot be changed may be forcibly approved by the calculation processing unit 12 in the above-mentioned step (S130). For example, inspections must be carried out at preset intervals, and the schedule cannot be changed significantly. Corrective maintenance is maintenance for equipment 3 that has already broken down, and the longer it is left unattended, the greater the loss due to the inability to use the broken equipment 3 increases. On the other hand, depending on the equipment 3, postponing corrective maintenance may suppress the decrease in the loading efficiency of the container terminal 1. For example, corrective maintenance of a crane is better to be carried out promptly, and corrective maintenance of a lighting device is not urgent. While corrective maintenance contributes to improving the loading efficiency of the container terminal 1 by carrying it out, in the case of major renovations, there is a risk that the efficiency of loading and unloading of the container terminal 1 may be significantly decreased by carrying out corrective maintenance.

[0066] The risk of the predicted profit or loss occurring increases as the planned end of service life date for predictive maintenance or scheduled maintenance approaches, and further increases after the planned end of service life date. Therefore, the number of days until the planned end of service life date may be used in addition to the predicted loss as an index for deciding whether to approve or reject the implementation of predictive maintenance or scheduled maintenance. In this way, by using the number of days until the planned end of service life date as an index, predictive maintenance or scheduled maintenance that has a higher risk of reaching the end of service life can be performed as scheduled, and predictive maintenance or scheduled maintenance that has a lower risk of occurring can be postponed.

[0067] The maintenance plan data D1 and the storage and retrieval plan data D2 are stored in the auxiliary storage unit 14 of the maintenance management system 10 as mutually independent data, but the maintenance plan data D1 and the storage and retrieval plan data D2 may be linked. Specifically, the calculation processing unit 12 of the maintenance management system 10 executes data processing to change each maintenance scheduled in the maintenance plan data D1 so that the storage and retrieval plan data D2 can be carried out as scheduled. For example, in a period in which an increase in the number of containers 2 being stored and retrieved due to the arrival and departure of ships 5 is predicted, among the maintenance scheduled for that period, a maintenance whose schedule can be changed is identified, and the schedule of the identified maintenance is changed to outside the range of that period. This change makes it easier for the fluctuation in the actual number of containers 2 being stored and retrieved at the container terminal 1 to approximate the fluctuation in the number of containers 2 being stored and retrieved at the container terminal 1 scheduled in the storage and retrieval plan data D2. In this way, the maintenance plan data D1 may be prepared by taking into consideration the influence on the number of cargo handling operations at the container terminal 1 based on the storage and retrieval plan data D2.

[0068] Next, a first modified example of the container terminal maintenance management system and method shown in FIG. 11 will be described.

[0069] In the procedure of the maintenance management method in the first modification, other steps (S210, S220) are added to the procedure of Fig. 6 described above. That is, in the procedure of the first modification, first, a target value D5 of a budget to be spent on maintenance scheduled for a predetermined period is input in advance to the maintenance management system 10 (S210). Next, based on the maintenance plan data D1, the calculation processing unit 12 identifies an excess budget that exceeds the target value D5 in the budget for each predetermined period, and outputs the identified excess budget to the output unit 16 (S230). Therefore, in the first modification, the user grasps the excess budget and compares the excess budget with the profit and loss described in the maintenance plan data D1a, thereby deciding whether to approve or reject the maintenance incorporated in the excess budget (S130).

[0070] In step (S210), a target value D5 is input to the maintenance management system 10 by a user. Specifically, the calculation processing unit 12 executes data processing to output an input screen for the target value D5 to the output unit 16, and the input unit 15 inputs a desired period and amount as the target value D5 on the input screen. The desired period can be input as any number of days, but for example, one year, the first half, and the second half are input so as to include multiple months with one month as the input unit. The desired amount is a target value of the budget that can be spent on the maintenance of the container terminal 1 for each desired period, and any amount can be input. The amount for a predetermined period is not limited to a single combination of period and amount, and for example, two types of periods, one year and three months, may be input as the desired period, and the desired amount for each period may be input. In addition, the amount can be made different depending on the time even for the same period, for example, the amount for each of the first three months and the second three months may be made different. In this way, the target value D5 may be input according to the circumstances of the user.

[0071] The target value D5 illustrated in FIG. 12 is input by the user to the maintenance management system 10. The target value D5 is an accumulation of combinations of periods and amounts desired by the user. In FIG. 12, two types of periods, one year and three months, are input, and amounts for each input period are input. In FIG. 12, amounts are omitted with "...", but the desired amounts are actually input. Note that when multiple periods are input as periods, the amount for the shortest period among the multiple input periods may be input, and amounts for the other periods may be calculated based on the input amount.

[0072] In step (S220), data processing is executed to calculate a budget for each desired period input by the calculation processing unit 12 based on the maintenance plan data D1, identify an excess budget that exceeds the target value D5 within the calculated budget, and output the identified excess budget. The calculated budget is the total of the costs of each maintenance planned in the maintenance plan data D1 within the period input as the target value D5. The maintenance cost includes the cost required for the performed maintenance, and also includes the costs required in the preparation stage for the maintenance (the cost of procuring parts 4 and maintenance workers).

[0073] The excess budget is a budget calculated based on the maintenance plan data D1 that is deemed to exceed the amount entered as the target value D5. The calculated budget may differ from the cost required in the actual preparation stage because it uses the user parts data D3, service provider parts data D4, and the manufacturer's delivery date and cost at the time of the budget calculation. Therefore, the excess budget should include not only the calculated budget that exceeds the amount entered as the target value D5, but also the budget that falls within a preset allowable range for the amount. The allowable range is, for example, about ±5% of the entered amount.

[0074] The budget data D6 illustrated in FIG. 13 is output to the output unit 16 of the maintenance management system 10. The budget data D6 has the budget required for maintenance of the container terminal 1 for each period input as the target value D5. In detail, the budget data D6 accumulates the budget for each three-month period (P1, P2, . . ., Pn) and the budget for each yearly period (P1 to P4, . . ., P(n-4) to Pn), and in the leftmost column of the table in FIG. 13, the surplus budget that exceeds the amount input as the target value D5 is marked as "excess." In FIG. 13, the budget for the period P2 and the budget for the periods P1 to P4 are surplus budgets.

[0075] In the first modification, the maintenance plan data D1a in FIG. 8 and the budget data D6 in FIG. 13 are output by the output unit 16, so that the user can compare the respective data. For example, the profit and loss of the maintenance carried out in the period P2 in which the budget is exceeded can be confirmed by the maintenance plan data D1a, and it can be determined whether or not to approve the maintenance that is the cause of the budget exceedance. As described above, in the first modification, the excess budget that exceeds the target value D5 is identified, and the identified excess budget is output, so that the user can be informed in advance of the advantages of carrying out the maintenance that is the cause of the exceedance. This makes it possible to effectively encourage the user to carry out the maintenance even if the budget exceeds the target value D5.

[0076] In the first modification, by identifying the maintenance included in the surplus budget, in step (S120), the calculation processing unit 12 can execute data processing to predict profit and loss in a situation where each maintenance included in the surplus budget is not implemented. That is, in the first modification, only the profit and loss for the maintenance included in the surplus budget is predicted, and approval or denial of the maintenance included in the surplus budget may be determined based on the predicted profit and loss.

[0077] In the first modification, if the budget for carrying out all the maintenance work scheduled in the maintenance plan data D1 as scheduled falls within the range of the amount desired by the user, all the maintenance work scheduled in the maintenance plan data D1, including the preparatory stages, is automatically carried out without the user having to make any decisions one by one. This can significantly reduce the burden on the user of the work related to maintenance at the container terminal 1.

[0078] In addition, in the first modification, if there is no excess budget, data processing for predicting losses in the calculation processing unit 12 is not necessary, and even if there is an excess budget, only profit and loss in a situation where maintenance included in the excess budget is not performed is predicted, so that the load of data processing in the calculation processing unit 12 can be reduced. In predictive maintenance and periodic maintenance, the planned end date of use of the equipment 3 is predicted based on the operating status of the equipment 3, and the planned end date of use may be several years in the future. For example, the life of electronic components such as inverters and programmable logic controllers is approximately 7 to 12 years. Therefore, the maintenance plan data D1 may include plans for predictive maintenance and periodic maintenance several years to several decades in the future. It is also possible to predict profit and loss for each predictive maintenance and periodic maintenance of the maintenance plan data D1, but in that case, the load of data processing in the calculation processing unit 12 becomes excessive. Therefore, by limiting the maintenance for predicting profit and loss to that included in the excess budget as in the first modification, it is advantageous to reduce the load of data processing in the calculation processing unit 12.

[0079] Next, a second variation of the container terminal maintenance management system and method will be described.

[0080] In the procedure of the maintenance management method in the modified example 2 shown in Fig. 14, another step (S310) is added to the procedure in Fig. 11 described above. That is, in the procedure in the modified example 2, the calculation processing unit 12 averages the budget for each predetermined period based on the maintenance plan data D1 (S310). Therefore, in the modified example 2, the budget data D6a shown in Fig. 15 described later is output, and the budget for each predetermined period of this budget data D6a is averaged compared to the budget data D6 in Fig. 13 described above.

[0081] In step (S310), the calculation processing unit 12 calculates a budget for each desired period based on the maintenance plan data D1, and performs data processing to level the calculated budget. In leveling the budget, the amount input as the target value D5 is used as a reference, and the maintenance plan data D1 is updated so that the budget for each period approaches that amount. Specifically, the calculation processing unit 12 identifies an excess budget that exceeds the target value D5 and a deficit budget that is insufficient for the target value D5 in the calculated budget. Next, the calculation processing unit 12 identifies maintenance that can be included in the deficit budget (maintenance whose schedule can be changed) from among the maintenance included in the excess budget, changes the schedule of the identified maintenance, and updates the maintenance plan data D1. The updated maintenance plan data D1 is used in subsequent data processing.

[0082] Whether or not a maintenance schedule can be changed and the extent to which it can be changed differs depending on the type of maintenance. Inspections only need to be carried out within a preset period, and can be changed to a certain extent (for example, by a few days or a few weeks). Predictive maintenance and periodic maintenance are subject to a higher risk of failure of the target equipment 3 as the planned end of service life approaches, but can also be carried out earlier, making them changeable. Corrective maintenance can be carried out at any time, and its schedule can be changed freely.

[0083] Budget data D6a shown in FIG. 15 is output to the output unit 6 of the maintenance management system 10. In the budget data D6a, the budget for each period is leveled with respect to the budget data D6 in FIG. 13 described above. Specifically, in the leveled budget data D6a, the excess budget for period P2 is smaller and the budgets for periods P(n-4) to Pn are larger than those in the budget data D6. Therefore, the budget for each period in the leveled budget data D6a is closer to the target value D5 input by the user.

[0084] As described above, in the second modification, budget excesses are less likely to occur by leveling out the budget in the maintenance plan data D1 based on the target value D5 input by the user. This makes it possible to propose a medium- to long-term maintenance plan for the container terminal 1 that is more satisfactory to the user. In addition to using the target value D5 as the basis for leveling out the budget in the maintenance plan data D1, a preset amount may also be used as the basis. Also, a representative value (average value, mode, median) of the budget for each predetermined period in the maintenance plan data D1 may be used as the basis.

[0085] In the second modification, based on the budget-leveled maintenance plan data D1, an annual maintenance plan, a medium-term maintenance plan of about 3 to 5 years, and a long-term maintenance plan of 10 years or more can be presented to the user. By leveling the budget required for the maintenance of the container terminal 1, it is possible to make the budget closer to fixed costs as much as possible, rather than variable costs. This makes it possible to grasp the operating costs of the container terminal 1 over the long term.

[0086] Although an embodiment of the present invention has been described above, the container terminal maintenance management system and method of the present invention are not limited to the specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention.

[0087] In the embodiment and modified examples 1 and 2 described above, the user makes the decision in step (S130) in Fig. 5 described above, but by inputting a decision criterion in advance into the maintenance management system 10, the decision can also be made by the calculation processing unit 12 using the input criterion. This decision criterion can be set arbitrarily, but it can also be set based on a decision made by the user in the process of repeatedly performing the embodiment and modified examples 1 and 2.

[0088] The maintenance plan data D1 and the incoming / outgoing plan data D2 are not limited to maintenance schedules and incoming / outgoing schedules of containers 2 at one container terminal 1, but may include maintenance schedules and incoming / outgoing schedules of containers 2 at multiple container terminals 1. The maintenance management system 10 functions as a common system for multiple container terminals 1, thereby strengthening cooperation among the multiple container terminals 1. For example, it becomes possible to adjust the inventory of parts 4 and the schedules of maintenance workers among the multiple container terminals 1, which is advantageous for eliminating dead stock of parts 4 and leveling out the work schedules of maintenance workers. [Explanation of symbols]

[0089] 1. Container Terminal 2. Container 3 Equipment 4 parts 10 Maintenance Management System 11 Cargo handling management system 12 Processing unit 13 Main memory 14 Auxiliary storage 15 Input section 16 Output section 18 Predictive Models 19 Teacher Data D0 Maintenance plan reference data D1, D1a Maintenance plan data D2 Stock entry / outgoing planning data D3 User inventory data D4 Service provider inventory data D5 Target Value D6, D6a Budget Data

Claims

1. A container terminal maintenance management system including an auxiliary memory unit storing maintenance plan data in which a large number of maintenance operations are scheduled for a large number of types of equipment in the container terminal, and inventory / shipment plan data in which a large number of containers are scheduled to be imported and shipped from the container terminal, a calculation processing unit, and an output unit, The relationship between the operation status of the container terminal, including the operation status of each of the facilities and the number of containers entering and leaving the container terminal, and the profit and loss at the container terminal is input in advance to the auxiliary storage unit, When approving the maintenance of each of the maintenance plan data, the calculation processing unit executes data processing to predict the profit and loss for each of the maintenance planned in the maintenance plan data in a case where the maintenance is not performed as the operating situation, based on the profit and loss in a case where the maintenance plan data and the incoming / outgoing plan data are performed as scheduled as the operating situation, based on the relationship between the maintenance plan data and the incoming / outgoing plan data that was input in advance, and outputs the predicted profit and loss to the output unit; A container terminal maintenance management system in which the profit and loss values ​​output from the output unit are used as indicators and the approved maintenance is carried out as scheduled in the maintenance plan data.

2. 2. A container terminal maintenance management system as described in claim 1, wherein when the maintenance is approved, before the approved maintenance is carried out, the calculation processing unit executes data processing to procure the parts of the equipment required for the maintenance and the maintenance workers who will perform the maintenance in preparation for the maintenance.

3. The container terminal maintenance management system according to claim 2, wherein electronic commerce is used for procuring the parts in the preparation.

4. A target value of a budget required for the maintenance for a predetermined period is input in advance into the auxiliary storage unit, 2. The container terminal maintenance management system according to claim 1, wherein the calculation processing unit executes data processing for calculating the budget for each of the predetermined periods based on the maintenance plan data, and data processing for identifying an excess budget that exceeds the input target value within each of the calculated budgets, and outputting the identified excess budget to the output unit.

5. A container terminal maintenance management system as described in claim 4, wherein, when the excess budget does not exist, the calculation processing unit executes data processing in which the maintenance of each of the maintenance plan data is deemed to have been approved without predicting the profit and loss.

6. 6. A container terminal maintenance management system according to claim 4 or 5, wherein the calculation processing unit executes data processing for calculating the budgets, and then executes data processing for leveling out the respective budgets based on the target value.

7. 2. A container terminal maintenance management system as described in claim 1, wherein each of the maintenance activities scheduled in the maintenance plan data includes inspection, corrective maintenance, and corrective maintenance, and whether or not each of the maintenance activities includes predictive maintenance and / or periodic maintenance is selected in advance before the maintenance plan data is created.

8. A method for managing maintenance of a container terminal using maintenance plan data in which maintenance of a large number of types of facilities of the container terminal is scheduled, and inventory / shipment plan data in which the number of containers to be imported and shipped to the container terminal is scheduled, comprising: A relationship between the operation status of the container terminal, including the operation status of each of the facilities and the number of containers entering and leaving the container terminal, and profit and loss at the container terminal is grasped in advance; When approving the maintenance of each of the maintenance plan data, a calculation processing unit predicts the profit and loss when the operation status is a situation in which the maintenance is not performed for each of the maintenance planned in the maintenance plan data, based on the relationship between the maintenance plan data and the incoming / outgoing plan data that has been grasped in advance, using as a standard the profit and loss when the operation status is a situation in which the maintenance plan data and the incoming / outgoing plan data are performed as scheduled, A container terminal maintenance management method that uses each of the predicted profits and losses as an indicator to determine whether to approve or reject the implementation of each of the maintenance operations described in the maintenance plan data, and carries out the approved maintenance operations as scheduled in the maintenance plan data.

Images