Information processing system, information processing method, and program

Abstract

[Problem] To provide an information processing system and the like that make it possible to more accurately ascertain a voyage schedule of a ship. [Solution] One embodiment of the present invention provides an information processing system equipped with at least one processor. The processor: executes, in a first display step, a first display process for displaying an itinerary reflecting an inputted schedule of a ship in which the schedule shows a first voyage schedule including a voyage duration of the ship in association with the ship; acquires, in an automatic identification system (AIS) acquisition step, AIS information from the ship in which the AIS information includes a departure schedule and an arrival schedule of the ship; and executes, in a second display step, a second display process for displaying an itinerary in which a second voyage schedule including a voyage duration of the ship indicated by the acquired AIS information is shown separately from the first voyage schedule in association with the ship.

Description

Information processing system, information processing method and program

[0001] The present invention relates to an information processing system, an information processing method, and a program.

[0002] Patent Document 1 discloses a technique for planning the route of a moving object on a nautical chart according to the positions of waypoints already set on the route and the positions of temporary potential waypoints.

[0003] Japanese Patent Application Laid-Open No. 2022-191051

[0004] When displaying the sailing schedule of a ship on a schedule table, there is a need to know the sailing schedule more accurately in order to, for example, operate and manage the ship appropriately.

[0005] In view of the above circumstances, the present invention provides an information processing system and the like that can more accurately grasp the sailing schedule of a ship.

[0006] According to one aspect of the present invention, there is provided an information processing system having one or more processors, wherein the processor executes a first display process in a first display step to display a schedule reflecting the inputted schedule of a ship, the schedule showing a first navigation schedule including the ship's voyage period associated with the ship, an AIS acquisition step to acquire AIS (Automatic Identification System) information from the ship, the AIS information including the ship's departure and arrival schedules, and a second display step to execute a second display process to display a schedule showing a second navigation schedule including the ship's voyage period indicated by the acquired AIS information associated with the ship and displayed separately from the first navigation schedule.

[0007] According to this embodiment, the ship's sailing schedule can be more accurately determined.

[0008] 1 is a diagram showing the overall configuration of the ship management system 1. FIG. 1 is a diagram showing the hardware configuration of the server device 10. FIG. 1 is a diagram showing the hardware configuration of the user terminal 20. FIG. 2 is a diagram showing the functional configuration of the control unit of each device. FIG. 2 is a diagram showing an example of a displayed schedule. FIG. 3 is a diagram showing an example of a schedule with a schedule input. FIG. 3 is a diagram showing an example of a schedule with the voyage period of a ship indicated by AIS information displayed. FIG. 4 is a diagram showing an example of the timing at which the AIS voyage period is displayed. FIG. 4 is an activity diagram showing an example of a schedule display process. FIG. 5 is a diagram showing an example of an input screen for schedule information. FIG. 6 is a diagram showing an example of a displayed route image. FIG. 5 is a diagram showing the overall configuration of the ship management system 1a. FIG. 6 is a diagram showing an example of a template for a report to be made by a crew member. FIG. 7 is a diagram showing another example of a displayed route image. FIG. 7 is a diagram showing an example of a displayed shipping plan. FIG. 8 is a diagram showing an example of a candidate port for recommended refueling displayed.

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the accompanying drawings. Various features shown in the following embodiments can be combined with each other.

[0010] Incidentally, a program for realizing the software appearing in one embodiment may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer and its functions are realized on a client terminal (so-called cloud computing).

[0011] Furthermore, various information processing according to an embodiment may realize input and output corresponding to the input. Here, the form of information referenced in such information processing (hereinafter referred to as reference information) is not limited as long as an output is obtained as a result of the input. The reference information may be, for example, rule-based information such as a database, a lookup table, or a predetermined function (including a decision formula such as a regression formula constructed using a statistical method), a trained model that has previously trained the correlation between input and output, or a large-scale language model that can output a desired result by inputting a prompt.

[0012] In one embodiment, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In one embodiment, various information is handled, and this information is represented, for example, by physical values ​​of signal values ​​representing voltage or current, high or low signal values ​​as a binary bit set consisting of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculations can be performed on the circuit in the broad sense.

[0013] Furthermore, a circuit in a broad sense is a circuit realized by at least an appropriate combination of a circuit, circuitry, a processor, a memory, etc. The processor may be a general-purpose processor or a dedicated circuit. That is, it includes application specific integrated circuits (ASICs), programmable logic devices (e.g., simple programmable logic devices (SPLDs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs)), etc.

[0014] 1. Hardware Configuration In this section, the hardware configuration of the construction support system according to this embodiment will be described.

[0015] Fig. 1 is a diagram showing the overall configuration of a ship management system 1. Fig. 1 shows an overview of each device provided in the ship management system 1 and the users who use those devices. Each overview will be explained as needed, with reference to other figures.

[0016] The ship management system 1 is an information processing system that executes processes to support ship management. The ship management system 1 includes a communication line 2, a ship 3, an AIS device 4, a satellite 5, an AIS land station 6, a server device 10, and a user terminal 20. The communication line 2 includes the Internet and mediates the exchange of data between devices connected to the communication line. The server device 10 and the AIS land station 6 are connected to the communication line 2 by wire, and the user terminal 20 is connected to the communication line 2 by wireless. Note that communication with the communication line 2 may be wired or wireless.

[0017] The ship 3 is a vessel that mainly sails on the sea carrying people and cargo, and is equipped with an AIS device 4. The AIS (Automatic Identification System) is a system that automatically transmits and receives information (hereinafter referred to as "AIS information") such as a call sign, ship name, position information, ground course, ground speed, departure port, arrival port, departure date and time (or scheduled departure date and time), and arrival date and time (or scheduled arrival date and time) using VHF (Very High Frequency) radio waves, and exchanges information between ship stations and between ship stations and land stations. The radio waves emitted by the AIS device 4 reach a range of several tens of kilometers in the direction of the ground and reach the height of satellites 5 in the direction toward the sky.

[0018] When satellite 5 receives radio waves transmitted from AIS device 4, it forwards the radio waves to the ground. AIS land station 6 receives the radio waves transmitted from AIS device 4 directly or via satellite 5 and acquires AIS information. AIS land station 6 provides the acquired AIS information to an external device, for example, via communication line 2. Server device 10 acquires AIS information from AIS device 4 directly, via satellite 5, or via AIS land station 6. Server device 10 stores an AIS information DB (database) and stores the acquired AIS information in the AIS information DB.

[0019] 1, the user terminal 20 is a terminal whose user is an employee on land who performs work related to the ship. The user terminal 20, for example, accepts input of the schedule of the ship 3 (such as the voyage period, dock period, and standby period) by the user, and transmits schedule information indicating the input schedule to the server device 10. The schedule here refers to a summary by date of what will be done using the ship 3 (such as the voyage) and what will be done to the ship 3 (such as inspection at the dock).

[0020] A schedule is usually created for a future plan, but when the scheduled date and time arrives, it becomes the current situation, and when that date and time passes, it becomes past actual results. In the ship management system 1, a schedule includes not only future plans, but also past actual results and current situations. The server device 10 stores a schedule information DB that stores schedule information, and stores, for example, schedule information transmitted from the user terminal 20. Based on the stored schedule information, the server device 10 executes a display process to display a schedule showing the schedule of each ship 3 on the user terminal 20.

[0021] 2 is a diagram showing the hardware configuration of the server device 10. The server device 10 includes a control unit 11, a storage unit 12, a communication unit 13, and a bus 14. The bus 14 electrically connects the various units included in the server device 10.

[0022] (Control Unit 11) The control unit 11 is, for example, a central processing unit (CPU) not shown. The control unit 11 is a computer that implements various functions related to the ship management system 1 by reading out predetermined programs stored in the storage unit 12. In other words, information processing by software stored in the storage unit 12 is specifically implemented by the control unit 11, which is an example of hardware, and can be executed as each functional unit included in the control unit 11. These will be described in further detail in the next section. Note that the control unit 11 is not limited to being single, and the system may be implemented with multiple control units 11 for each function. A combination of these may also be used.

[0023] (Memory unit 12) The memory unit 12 stores various information defined above. This may be implemented, for example, as a storage device such as a solid state drive (SSD) that stores various programs related to the ship management system 1 executed by the control unit 11, or as a memory such as a random access memory (RAM) that stores temporarily required information (arguments, arrays, etc.) related to program calculations. The memory unit 12 stores various programs, variables, etc. related to the ship management system 1 executed by the control unit 11.

[0024] (Communication Unit 13) The communication unit 13 is configured to be able to transmit various electrical signals from the server device 10 to external components. The communication unit 13 is also configured to be able to receive various electrical signals from the external components to the server device 10. More preferably, the communication unit 13 has a network communication function, which may enable communication of various information between the server device 10 and external devices via the communication line 2.

[0025] 3 is a diagram showing the hardware configuration of the user terminal 20. The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a bus 26. The bus 26 electrically connects the various units included in the user terminal 20. The control unit 21, the storage unit 22, and the communication unit 23 are similar hardware to the control unit 11, the storage unit 12, and the communication unit 13 shown in FIG. 2, although the specifications, model, etc. may differ.

[0026] (Input unit 24) The input unit 24 has one or more input interfaces of keys, buttons, a touch screen, a mouse, etc., and receives input from the user. (Output unit 25) The output unit 25 has output devices such as a display and a speaker, and displays visual information generated in a manner that is visible to the user, such as a screen, an image, an icon, text, etc., on the display surface, and outputs sound including voice.

[0027] 2. Functional Configuration This section describes the functional configuration of this embodiment. As described above, information processing by software stored in the storage unit of each device is specifically realized by a control unit, which is an example of hardware, and each functional unit included in the control unit can be executed.

[0028] Fig. 4 is a diagram showing the functional configuration of the control unit of each device. The control unit 11 of the server device 10 includes a server display unit 111, a user authentication unit 112, an AIS processing unit 113, a schedule processing unit 114, and a notification processing unit 115. The control unit 21 of the user terminal 20 includes a user display unit 211 and an operation reception unit 212. Note that the functions shown in Fig. 4 are only a part of the functions, and other functions may also be included.

[0029] The server display unit 111 executes processing for displaying on each terminal a system screen related to the ship management system 1. The server display unit 111 performs processing such as generating and transmitting an HTML (Hyper Text Markup Language) file, and displays a web page showing the system screen on the user terminal 20. The server display unit 111 may also perform processing such as generating and transmitting display data for an application for using the ship management system 1.

[0030] The user authentication unit 112 authenticates a user who logs in via the user terminal 20 based on authentication information such as a registered user ID (Identification) and password. This authentication allows the server device 10 to process data exchanged with the user terminal 20 in association with the user associated with the data. The AIS processing unit 113 executes processing related to the AIS information. For example, the AIS processing unit 113 executes processing to store AIS information obtained directly or indirectly from the AIS device 4 in the AIS information DB.

[0031] The schedule processing unit 114 executes processing related to the schedule of the ship 3. For example, the schedule processing unit 114 executes processing to store schedule information transmitted from the user terminal 20 in the schedule information DB. The notification processing unit 115 executes processing related to notifications to the user. For example, when there is a difference between the schedule input by the user and the schedule indicated by the AIS information, the notification processing unit 115 executes processing to notify the user of this fact.

[0032] The user display unit 211 of the user terminal 20 controls the display on a display, which is a display means of the user terminal 20. The user display unit 211 displays, for example, a web page or an application screen transmitted from the server display unit 111 on the display means. The operation accepting unit 212 of the user terminal 20 accepts operations performed by the user.

[0033] 3. Information Processing This section describes the information processing that the program causes the computer to execute in this embodiment. The ship management system 1 executes a schedule display process that displays the ship's sailing schedule. First, the following describes the screen displayed on the user terminal 20 by the schedule display process.

[0034] The server display unit 111 executes a first display process to display a schedule that reflects the input ship schedule. In this case, the server display unit 111 is an example of a first display unit. The ship schedule displays a first sailing schedule that includes the ship's sailing period in association with the ship. The ship schedule is input, for example, by a user operating the user terminal 20. The server display unit 111 transmits screen data showing the schedule to the user terminal 20, and the user terminal 20 displays the schedule shown in the transmitted screen data on the user display unit 211.

[0035] Figure 5 is a diagram showing an example of a displayed schedule. The user display unit 211 displays a ship management system screen G1 including a schedule tab TB1 and a location information tab TB2. The schedule tab TB1 is a tab for displaying the ship's schedule. The location information tab TB2 is a tab for displaying the ship's location on a map. In the example of Figure 5, the schedule tab TB1 is selected, and a schedule list C1 and a year / month designation image B11 are displayed.

[0036] The schedule list C1 includes a schedule C11 for vessel A, a schedule C12 for vessel B, a schedule C13 for vessel C, and a schedule C14 for vessel D. In the example of FIG. 5, no schedules for any vessels have yet been input into the schedule list C1. The year and month designation image B11 is an operation image for designating the year and month of the schedule to be displayed, and in the example of FIG. 5, August 2023 is selected. When the operation acceptance unit 212 accepts the schedule input by the user, the user display unit 211 displays the input schedule.

[0037] Figure 6 is a diagram showing an example of a schedule table with schedules entered. In the example of Figure 6, the sailing period, docking period, and waiting period are entered as the ship's schedule. The sailing period is the period during which the ship mainly sails at sea. The docking period is the period during which the ship is docked for maintenance. The waiting period is the period during which the ship waits in port or offshore. Schedule information showing these schedules is stored in association with the ship in the schedule information DB shown in Figure 1, and can be read out and displayed at any time.

[0038] The schedule C11 for vessel A has a waiting period D11 and a voyage period D12 entered therein, and the schedule C12 for vessel B has a voyage period D21, a waiting period D22, and a docking period D23 entered therein. Furthermore, the schedule C13 for vessel C has a docking period D31 and a voyage period D32 entered therein, and the schedule C14 for vessel D has a voyage period D41 and a docking period D42 entered therein. Of these, the voyage periods D12, D21, D32, and D41 are each an example of a first voyage period. Note that these schedules are merely examples, and each period may be longer or shorter than the example shown in FIG. 6 , and the period between each period may also be longer or shorter than the example shown in FIG. 6 .

[0039] Next, the server device 10 (AIS processing unit 113) acquires AIS information from the ship. In this case, the AIS processing unit 113 is an example of an AIS acquisition unit. The AIS information includes the ship's departure and arrival schedules. The AIS processing unit 113 associates the acquired AIS information with the ship 3 that is equipped with the AIS device 4 from which the information was acquired, and stores the information in the AIS information DB shown in FIG. 1. When the AIS processing unit 113 stores new AIS information, it notifies the server display unit 111 of this fact.

[0040] When the server device 10 (server display unit 111) receives a notification from the AIS processing unit 113, it refers to the AIS information DB and executes a second display process for displaying a second navigation schedule including the navigation period of the ship indicated by the AIS information acquired by the AIS processing unit 113 (hereinafter referred to as the "AIS navigation period") in association with the ship. The server display unit 111 in this case is an example of a second display unit. The server device 10 (server display unit 111) displays a schedule that shows the second navigation schedule separately from the first navigation schedule.

[0041] Figure 7 is a diagram showing an example of a schedule showing the voyage period of a vessel indicated by AIS information. In the example of Figure 7, the schedule C11 for vessel A includes an AIS voyage period E12 corresponding to the input voyage period D12. Voyage period D12 indicates that the vessel is scheduled to depart on the 13th and arrive on the 22nd, while AIS voyage period E12 indicates that the vessel is scheduled to depart on the 12th and arrive on the 23rd. In the example of Figure 7, the 13th is assumed to be the current day.

[0042] The AIS navigation period E12 indicates that the past portion of the schedule (portion before the 13th) indicates the actual navigation results, and the future portion (portion after the 13th) indicates the scheduled navigation results included in the AIS information. In other words, although the departure date for Vessel A was entered as the 13th, the AIS navigation period E12 indicates that it actually departed on the 12th. In this way, the AIS navigation period E12 can indicate accurate schedules for past dates.

[0043] Furthermore, the expected arrival date of vessel A entered by the user is the 22nd, as indicated by voyage period D12, but the expected arrival date indicated by the AIS information is the 23rd, as indicated by AIS voyage period E12. The expected arrival date and time indicated by the AIS information is updated according to the actual voyage conditions, becoming earlier if the voyage is progressing faster than planned, and becoming later if the voyage is progressing slower than planned. Therefore, AIS voyage period E12 can indicate a more accurate schedule for future dates than voyage period D12.

[0044] Itinerary C12 for vessel B includes AIS voyage period E21, which corresponds to the input voyage period D21. AIS voyage period E21 indicates that the vessel departed two days later than voyage period D21, indicating that the scheduled arrival date is five days later. Itinerary C14 for vessel D includes AIS voyage period E41, which corresponds to the input voyage period D41. AIS voyage period E41 indicates that the vessel arrived three days earlier than the scheduled arrival date of voyage period D41. For these voyage periods as well, the AIS voyage period indicates a more accurate schedule than the input voyage period.

[0045] According to this aspect, the ship's sailing schedule can be grasped more accurately than when only the input sailing period is displayed and the AIS sailing period is not displayed.

[0046] For ease of understanding, the examples of Figures 6 and 7 do not explain the timing at which each period included in the itinerary is displayed, but for example, the navigation period shown in Figure 6 is displayed when it is input by the user. Also, the AIS navigation period shown in Figure 7 is displayed when AIS information indicating that AIS navigation period is acquired. The timing at which the AIS navigation period is displayed will be explained with reference to Figure 8.

[0047] Figure 8 is a diagram showing an example of the timing at which AIS navigation periods are displayed. In the example of Figure 8, a schedule list C2 updated on August 14 from the schedule list C1 as of August 13 shown in Figure 7 is displayed. The schedule list C2 includes schedules C21, C22, C23, and C24 for ships A, B, C, and D. Of these, schedule C23 includes AIS navigation period E32 corresponding to navigation period D32 that was not displayed as of August 13.

[0048] 8, the AIS processing unit 113 acquires AIS information from the AIS device 4 installed on the vessel C at some time between August 13 and August 14, and the server display unit 111 executes a second display process to display a schedule C23 including the AIS navigation period E32 indicated by the acquired AIS information as a second navigation schedule in association with the vessel C. In this way, the AIS navigation period is displayed when the AIS information indicating that AIS navigation period is acquired.

[0049] Furthermore, the server device 10 (AIS processing unit 113) repeatedly acquires AIS information. In this case, the AIS processing unit 113 is an example of an AIS acquisition unit. When the vessel's voyage period indicated by the AIS information acquired by the AIS processing unit 113 changes, the server device 10 (server display unit 111: an example of a second display unit) displays a second voyage itinerary indicating the changed voyage period. For example, the server display unit 111 displays an AIS voyage period E21 for vessel B shown in FIG. 7 with an expected arrival date of August 16, but displays an AIS voyage period E21 shown in FIG. 8 with an expected arrival date of August 15 based on newly acquired AIS information. This configuration makes it easier to grasp changes in the voyage situation than when the second voyage itinerary is fixed.

[0050] Next, we will explain the information processing procedure in the schedule display process that displays the schedules shown in Figures 6 to 8. In the following explanation, the server device 10, the user terminal 20, or each function shown in Figure 4 will be described as the subject of each information processing, but this information processing is executed by at least one processor provided in the ship management system 1, i.e., a processor provided in the control unit of each device (control units 11 and 21).

[0051] 9 is an activity diagram showing an example of a schedule display process. First, the user terminal 20 (operation accepting unit 212) accepts input of ship schedule information by a user (activity A11). In the example of FIG. 9, it is assumed that a land-based employee enters the ship schedule information. The user terminal 20 (user display unit 211) displays an input screen for accepting input of schedule information.

[0052] Figure 10 is a diagram showing an example of an input screen for schedule information. The input screen G2 shown in Figure 10 displays the text "Please enter schedule information," an input field C25, and a confirm button B21. The input field C25 includes input fields for "Vessel Name," "Performance Information," "Schedule Type," "Port of Departure," "Scheduled Date of Departure," "Port of Call," "Scheduled Date of Port Call," "Port of Arrival," and "Scheduled Date of Arrival." It is not necessary to fill in all of these input fields, but in the example of Figure 10, the "Vessel Name," "Port of Departure," "Schedule Type," "Scheduled Date of Departure," "Port of Arrival," and "Scheduled Date of Arrival" marked with "(*)" are considered to be required input fields.

[0053] "Ship Name" is an input field for inputting the name of the ship. "Performance Information" is an input field for inputting information indicating the performance of the ship. Performance information is information indicating, for example, the ship's speed, navigable distance, and load capacity. As performance information, information that directly indicates each performance (speed or distance, etc.) may be input, or information that allows performance to be determined (ship type or model, etc.). For example, if the ship type is a tanker, performance information indicating a speed of approximately 10 to 15 knots, or if the ship type is a container ship, a speed of approximately 20 to 25 knots (these speeds are just examples) may be input.

[0054] "Schedule type" is an input field for inputting the type of schedule. Schedule types include, for example, sailing, waiting, or dock. "Port of departure," "Port of call," and "Port of arrival" are input fields for inputting the name of each port. "Scheduled departure date," "Scheduled port call date," and "Scheduled arrival date" are input fields for inputting the scheduled date of arrival at each port.

[0055] When the user enters information into each input field and operates the Confirm button B21, the user terminal 20 (operation accepting unit 212) accepts the input of schedule information (activity A11) and transmits the input schedule information to the server device 10. The server device 10 (schedule processing unit 114) stores and accumulates the transmitted schedule information in the schedule information DB shown in Fig. 1 (activity A12). The information processing of A11 and A12 is executed, for example, each time a ship schedule is determined or a ship schedule is changed.

[0056] The AIS information acquired from the AIS device 4 includes dynamic information, static information, and navigation-related information. Dynamic information includes position information, Universal Time (UTC), ground course, and ground speed. Static information includes the International Maritime Organization (IMO) number, call sign, ship name, ship length, width, and ship type. Navigation-related information includes the port of departure, port of arrival, departure date and time (or scheduled departure date and time), and arrival date and time (or scheduled arrival date and time).

[0057] The AIS device 4 is connected to or has built-in devices for measuring dynamic information, and periodically acquires dynamic information from these devices (activity A21). Furthermore, the crew operates the AIS device 4 at predetermined times to input voyage-related information. Examples of predetermined times include the start of a voyage and when the estimated arrival date and time changes by a certain amount (e.g., one day or more). The AIS device 4 accepts the input of voyage-related information by the crew (activity A22).

[0058] The AIS device 4 stores static information in advance, and for example periodically reads out the static information to generate AIS information indicating the acquired dynamic information and the input voyage-related information (activity A23), which is then transmitted to the server device 10. The server device 10 (AIS processing unit 113) stores and accumulates the transmitted AIS information in the AIS information DB shown in Fig. 1 (activity A24). The information processes A21, A23, and A24 are executed at predetermined time intervals (every few minutes, for example), but the information process A22 is executed only when the mariner inputs voyage-related information.

[0059] Here, let's assume that a land-based employee operates the user terminal 20 to view a ship schedule. The schedule display operation may or may not include a designation operation to specify the ship for which the schedule is to be displayed. When the user terminal 20 (operation reception unit 212) receives the schedule display operation (activity A31), it sends a schedule display request to the server device 10. The server device 10 (schedule processing unit 114) first reads out the schedule information of the ship to be displayed on the schedule (activity A32). If a display target is specified, the server device 10 (schedule processing unit 114) reads out the schedule information of the specified ship; if no display target is specified, it reads out the schedule information of the ship that is highest in the display order as the ship to be displayed.

[0060] The server device 10 (schedule processing unit 114) then generates an image showing the first sailing schedule based on the retrieved schedule information (activity A33). The image showing the first sailing schedule is, for example, the waiting period D11 and sailing period D12 shown in FIG. 6. Next, the server device 10 (AIS processing unit 113) retrieves the latest AIS information for the vessel to be displayed (activity A41). Next, the server device 10 (AIS processing unit 113) determines whether the AIS information includes sailing-related information (activity A42).

[0061] The AIS information basically includes navigation-related information when the ship is currently sailing, but does not include navigation-related information if the crew has not entered it or if the ship is not currently sailing. If the server device 10 (AIS processing unit 113) determines that the AIS information includes navigation-related information (YES), it generates an image showing a second navigation schedule based on the navigation-related information (activity A43). The image showing the second navigation schedule is, for example, the AIS navigation periods E12 and E21 shown in Figure 7.

[0062] After A43 or if the server device 10 (server display unit 111) determines that no voyage-related information is included (NO) in A42, it generates a schedule (activity A44) and transmits the generated schedule to the user terminal 20. The schedule generated in this manner includes an image showing the first voyage schedule and, if generated, an image showing the second voyage schedule. The user terminal 20 (user display unit 211) displays the transmitted schedule (activity A45). The schedule list C1 shown in Figure 7 is an example of a schedule displayed in this manner.

[0063] Here, the vessel schedule includes non-voyage schedules, which indicate periods other than the vessel's sailing. Non-voyage schedules include, for example, waiting schedules and docking schedules shown in FIG. 8 and elsewhere. If the second sailing schedule overlaps with a non-voyage schedule, the server device 10 (notification processing unit 115) issues a notification in a predetermined manner. In this case, the notification processing unit 115 is an example of a first notification unit. For example, the AIS sailing period E21 shown in FIG. 7 overlaps with the waiting period D22, which is input from August 15th to 17th.

[0064] The server device 10 determines whether the AIS navigation period and the non-voyage schedule overlap (activity A51), and if they do not overlap (NO), returns to A32 and waits for the next itinerary display operation. If they overlap (YES), the server device 10 (notification processing unit 115) generates notification information notifying the overlap and transmits it to the user terminal 20 (activity A52). For example, in the example of Figure 8, the server device 10 (notification processing unit 115) transmits notification information to the user terminal 20 notifying that the AIS navigation period and the non-voyage schedule overlap in the itinerary C12 of ship B.

[0065] The user terminal 20 outputs the transmitted notification information (activity A53). The user terminal 20 may display the notification information on the user display unit 211, or may output a sound indicating the notification information. In either case, it is easier to notice the difference between the forecast and the actual result, i.e., the discrepancy between the input schedule and the actual result or the latest schedule, compared to when notification information is not output.

[0066] Although the expected arrival date is a required field on the input screen shown in FIG. 10 , this is not limiting. For example, when the port of departure and port of arrival of a vessel are input on the input screen, the server device 10 (server display unit 111: an example of a first display unit) may reflect a schedule indicating the number of days required for the vessel's voyage from the port of departure to the port of arrival in the itinerary as a first voyage schedule, even if the expected departure date and expected arrival date are not input. In this case, the server device 10 (server display unit 111) stores, for example, a voyage days table that associates the port of departure, the port of arrival, performance information, and the number of voyage days. The number of voyage days is calculated by dividing the distance along the route from the port of departure to the port of arrival by the average voyage speed indicated by the performance information (e.g., the type of vessel).

[0067] The server device 10 (server display unit 111) then generates and displays a rectangular sailing itinerary image (similar to the sailing itinerary image shown in FIG. 7, etc.) whose length corresponds to the number of sailing days associated in the sailing days table with the departure port, arrival port, and performance information entered on the input screen. The user completes the sailing itinerary input by aligning the edge of the displayed sailing itinerary image with the scheduled departure date. Alternatively, the server device 10 (server display unit 111) may prompt the user to input only the scheduled departure date, and then display the sailing itinerary image so that the edge of the image is aligned with the input scheduled departure date. In either case, the effort required for inputting the schedule can be reduced compared to when all scheduled dates must be entered.

[0068] Furthermore, when an operation to select the second sailing schedule is performed, the server device 10 (server display unit 111) executes a third display process to display a route image showing on a map the position or route of the ship indicated by the AIS information on which the second sailing schedule is based. In this case, the server display unit 111 is an example of a third display unit. The server device 10 (server display unit 111) generates screen data showing the route image and transmits it to the user terminal 20. The user terminal 20 (user display unit 211) displays the route image indicated by the transmitted screen data via the user display unit 211.

[0069] Fig. 11 is a diagram showing an example of a displayed route image. The user terminal 20 (user display unit 211) is displaying the ship management system screen G3 with the position information tab TB2 shown in Fig. 5 selected. As described above, the position information tab TB2 is a tab for displaying the position of the ship on a map, but it is assumed that not only the position of the ship but also the ship's route is displayed.

[0070] The example in Figure 11 shows a navigation image displayed by the server device 10 (server display unit 111) when the AIS navigation period E21 of vessel B shown in Figure 8 is selected. The server device 10 (server display unit 111) displays a route image RT21 including the current position P21 of vessel B and a route R21 to the current position P21 of vessel B based on the AIS information of vessel B. The server device 10 (server display unit 111) displays the route image RT21 as position information C32 of vessel B.

[0071] The position information tab TB2 displays the position information C31, C32, C33, and C34 of ships A, B, C, and D, and when other position information is selected, a route image of the selected ship is displayed. The position information tab TB2 may also display route images of all ships simultaneously. This configuration makes it easier to check the routes of ships shown in the schedule, compared to when it is necessary to switch tabs and select a ship in order to display a route image.

[0072] <Support for Acquiring Location Information> One method for acquiring location information of a ship 3 that is outside the communication range of the AIS land station 6 is to acquire AIS information via a satellite 5, but this is not the only method. For example, when a crew member on board the ship 3 is performing reporting duties, the report can be utilized.

[0073] Figure 12 is a diagram showing the overall configuration of the ship management system 1a. In addition to the components shown in Figure 1, the ship management system 1a also includes a crew terminal 30. The crew terminal 30 is a terminal used by crew members, and is used, for example, for reporting tasks by crew members. Crew members submit, for example, reports on voyages, safety, health, operations, technical matters, and legally required reports. The crew terminal 30 stores templates for various types of reports and displays the type of template selected by the crew member.

[0074] Figure 13 is a diagram showing an example of a template for a report to be made by a seafarer. In Figure 13, the crew terminal 30 displays a report creation screen G4. The report creation screen G4 displays a report name "Movement Report," input fields C41 for the following items: "Vessel Name," "Loading Port," ..., "Wind Power," and "Current Location," and a Save button B41. When each input field is filled in and the Save button B41 is operated, the crew terminal 30 generates an email containing the entered report content in a predetermined format (e.g., a format including predetermined symbols at the beginning and end of sentences), and sends the email to a pre-registered destination (hereinafter referred to as the "report destination").

[0075] The reporting destination is, for example, an email address prepared for aggregating and managing crew reports in the ship management system 1. The server device 10 functions as an example of a report acquisition unit that acquires reports sent by email from the ship 3 via the satellite 5. The server device 10 has the authority to open emails received at the reporting destination, and acquires the reports by extracting portions of a predetermined format contained in the received emails.

[0076] Then, when the acquired report includes location information indicating the position of the ship 3 and indicates that the voyage period of the ship 3 will change depending on the position indicated by the location information, the server device 10 (an example of a second display unit) displays a second voyage itinerary indicating the changed voyage period. The server device 10 calculates the average speed until arrival based on, for example, the number of days until the scheduled arrival date on the second voyage itinerary indicated by the AIS information and the distance from the position indicated by the location information included in the report to the arrival port.

[0077] If the calculated average speed exceeds the speed performance of the vessel 3, the server device 10 determines that the vessel 3 will not be able to arrive by the scheduled arrival date and therefore the voyage period will change.The server device 10 then calculates the number of days required for the vessel 3 to navigate the distance from the position indicated by the position information included in the report to the arrival port based on the speed performance of the vessel 3.The server device 10 displays the AIS voyage period (an example of a second voyage itinerary) with the calculated number of days as the remaining voyage period.According to this aspect, a second voyage itinerary that corresponds to changes in circumstances can be displayed even when the vessel 3 is navigating outside the communication range of the AIS land station 6.

[0078] <Accident Information> To ensure safe navigation, attention may be drawn to locations where accidents have occurred in the past. In this case, the server device 10 first functions as an example of a storage unit that accumulates accident information indicating locations where ship accidents have occurred. The server device 10 pre-stores, for example, information about ship accidents provided by public institutions or private businesses as accident information. The accident information is information indicating the name of the ship involved in the accident, the date and time of the accident, the location of the accident, the type of accident (collision, capsize, fire, etc.), and a summary (text explaining the details of the accident, etc.).

[0079] The server device 10 then functions as an example of a third display unit that executes a process as a third display process for displaying, on the route image, a location image indicating the location of a ship accident that occurred in the sea area indicated by the route image, based on the accumulated accident information. The server device 10, for example, extracts, from the accumulated accident information, accident information indicating an accident that occurred at a location that is a threshold distance or less from the current location of the ship 3. The server device 10 (server display unit 111) causes the user terminal 20 to display a route screen that indicates, on a map, the location of the accident indicated by the extracted accident information.

[0080] Figure 14 is a diagram showing another example of a displayed route image. The ship management system screen G3a shown in Figure 14 displays not only the current position P21 and route R21 of the ship B, but also point images J31 and J32 indicating the locations of accidents that have occurred within a predetermined range from the current position P21. This aspect makes it possible to draw attention to avoid causing an accident in the same location as a previous accident.

[0081] Furthermore, when a location image is selected by the user, the server device 10 (server display unit 111) displays accident information for the accident whose location is indicated by the selected location image. In the example of Fig. 14, accident information J311 corresponding to location image J31 is displayed. According to this aspect, for example, it is possible to determine whether there are any similarities between the situation when a past accident occurred and the current situation, and if there are any similarities, it is possible to navigate with greater caution, thereby making it easier to learn from the accident compared to when the accident information is not displayed.

[0082] Furthermore, the server device 10 (server display unit 111) may only display position images and accident information for accidents that occurred in situations that have something in common with the current situation of the vessel 3. The server device 10 displays position images and accident information only for accidents that have a predetermined number or more commonalities among conditions such as weather, time of day, season, type of vessel, traveling speed, and cargo load ratio. The server device 10 may also change the display format (for example, by using larger text) for accidents that have more commonalities with the current situation. In either case, attention is drawn to accidents that have many commonalities with the current situation of the vessel 3, so the risk of accidents can be reduced more effectively than when position information and accident information are uniformly displayed.

[0083] Furthermore, the server device 10 (alert processing unit 115) may function as an example of a second alert unit that alerts crew members of the ship 3 when the distance between the position of the ship 3 and the location of the accident is equal to or less than a threshold. The server device 10 (alert processing unit 115) alerts crew members, for example, by displaying a pop-up image on the crew terminal 30 indicating that the crew member is approaching the location of the accident. Alternatively, the alert may be issued by outputting an alert sound from a speaker of the crew terminal 30, or by outputting alert information to a mobile terminal carried by a crew member other than the crew terminal 30. According to such an embodiment, it is possible to quickly alert crew members to the approach of the accident site compared to when an approach alert is not issued.

[0084] <Support for Ship Allocation Plans> The ship management system 1 may support ship allocation plans for ships under its management. Ship allocation involves assigning tasks to ships to transport cargo and people and deploying them to the necessary ports. In this case, the server device 10 first functions as an example of a constraint acquisition unit that acquires constraint information indicating constraints on ship operation. Operation constraints are conditions that determine whether a ship can operate, and include, for example, the location and time of shipper demand, the amount of cargo, the ship's basic performance, the port's cargo handling capacity, and restrictions on the time periods during which cargo can be handled.

[0085] Among the constraint information, predetermined information (such as the basic performance of the ship, the cargo handling capacity of the port, and restrictions on the time periods during which cargo can be handled) is pre-stored in the server device 10. Furthermore, dynamically changing constraint information (such as the location and time of occurrence of shipper demand and the amount of cargo) is input to the server device 10 by, for example, an operator operating the user terminal 20 at any time. For example, when the server device 10 is requested by an operator to create a shipping plan, it reads out and acquires the constraint information stored in itself.

[0086] The server device 10 (server display unit 111) then functions as an example of a fourth display unit that executes a fourth display process to display candidate operation schedules that comply with the constraints indicated by the acquired constraint information. The server device 10 extracts, for example, from the current positions and sailing schedules of each ship, ships that can be deployed at the location and time of the shipper's demand indicated by the constraint information. From the extracted ships, the server device 10 identifies a ship (which may be shared by two or more ships) that can carry the amount of cargo indicated by the constraint information.

[0087] The server device 10 sets the scheduled departure date and scheduled arrival date based on the amount of cargo to be loaded onto the identified ship and the basic performance of the ship (particularly the sailing speed) indicated by the constraint information.The server device 10 then sets the date and time for loading and unloading the cargo based on the port's cargo handling capacity and the restrictions on the available cargo handling time slots indicated by the constraint information.Once the server device 10 (server display unit 111) has created candidate operating schedules that comply with the constraints in this way, it displays the created candidates on the user terminal 20.In this case, the user terminal 20 is used, for example, by a person in charge of ship allocation operations.

[0088] 15 is a diagram showing an example of a displayed shipping plan. The shipping plan screen G5 shown in FIG. 15 displays cargo information C50, operation schedule candidates C51, C52, C53, and C54, and decision buttons B51, B52, B53, and B54. The cargo information C50 displays information about the cargo to be shipped, including the cargo shipper, cargo type, weight, departure and arrival points, loading date, and delivery deadline. The loading date indicates the date when the cargo will be available to be loaded onto the ship at the departure port, and the delivery deadline indicates the deadline for delivery of the cargo at the arrival port.

[0089] Each candidate sailing schedule shows the sailing period when operated by available ships E, F, G, and H. For example, in the case of ship E, the sailing period for departing with cargo on August 11th and arriving at the destination port on August 22nd is displayed as a candidate sailing schedule. Each candidate sailing schedule also shows the costs K1, K2, K3, and K4 (K1<K2<K3<K4) required for the sailing. The costs required for the sailing are calculated, for example, based on a fee table set for each ship. In the example of Figure 15, the sailing periods are displayed in order from lowest to highest sailing cost.

[0090] The person in charge of ship allocation decides which ship to actually allocate from the displayed candidate sailing schedules, taking into consideration the schedule, cost, etc., and presses the decision button for the decided ship. The server device 10 (server display unit 111) displays the candidate sailing schedule corresponding to the operated decision button as the first sailing schedule, for example, in the schedule list C1 shown in FIG. 6, etc. This embodiment eliminates the need to search for candidate ships to allocate and to input schedule information for the ship decided to allocate, thereby supporting ship allocation planning.

[0091] The server device 10 (server display unit 111) may change the display mode of the candidate sailing schedule depending on the ship. For example, the server device 10 may display the candidate sailing schedule in a mode corresponding to the margin for the constraints indicated by the constraint information. Specifically, the server device 10 may determine that the margin is higher when the ratio of the cargo weight to the upper load limit is smaller. Furthermore, the server device 10 may determine that the margin is higher when the number of days from the scheduled arrival date until the delivery deadline is longer.

[0092] The server device 10 (server display unit 111) then displays the sailing schedule candidates in a color closer to blue as the margin increases, and in a color closer to red as the margin decreases. The server device 10 (server display unit 111) may also display the sailing schedule candidates by enlarging the rectangular image representing the voyage period or by thickening the border, as the margin increases. In either case, the margin of each candidate can be visually determined, making it easier to decide which ship to assign compared to when the margins are displayed in a uniform manner.

[0093] In the above example, the user was asked to select the vessel to be actually assigned from among the candidate sailing schedules, but the server device 10 may narrow down the candidates to, for example, the one with the lowest cost and automatically reflect this as the first sailing schedule in the itinerary list C1. In this case, the user does not need to go through the trouble of selecting the vessel to be assigned.

[0094] <Fuel Price Prediction> The ship management system 1 may support ship refueling planning. Ships traveling long distances have the opportunity to call at various ports around the world. Ships refuel at the ports they call at, but the price of fuel varies depending on the port and also on the time of year. Therefore, the server device 10 first functions as an example of a prediction unit that predicts the refueling price at the time of port arrival at ports where the ship can call on its planned route.

[0095] For example, the server device 10 accumulates fuel price history at ports around the world and predicts the fuel price at each port at the scheduled time of arrival based on price changes shown in the accumulated history. More specifically, the server device 10 predicts the fuel price at each port at the scheduled time of arrival based on, for example, the correlation between crude oil prices and fuel prices at each port and crude oil price forecasts provided by public institutions or private businesses. Note that the server device 10 may predict the fuel price at each port at the scheduled time of arrival using AI that has learned parameters such as crude oil prices and fuel prices for each port.

[0096] The server device 10 (server display unit 111) functions as an example of a fifth display unit that executes a fifth display process for displaying candidate ports for recommended refueling of the vessel based on the predicted refueling price. Figure 16 is a diagram showing an example of the displayed candidate ports for recommended refueling. The refueling plan screen G6 shown in Figure 16 displays, superimposed on a map, a planned route R61 of the vessel 3, a port image P61 indicating a port that can be entered on the planned route R61, and recommended port images P62 and P63 indicating ports for recommended refueling.

[0097] Ports that can be entered on the planned route R61 are, for example, ports within a certain distance from the planned route R61. Ports for which refueling is recommended are ports that have the lowest expected fuel unit price at the time when the ship 3 can enter the port, among the ports for which refueling is possible. In the example of Figure 15, the two ports with the lowest expected unit price are displayed as ports for which refueling is recommended.

[0098] The server device 10 (server display unit 111) displays the recommended port images P62 and P63 in a different format from the other port images P61, making it easier to understand the ports where refueling is recommended. Furthermore, the server device 10 (server display unit 111) displays fuel price information F62 and F63 in association with the recommended port images P62 and P63. The fuel price information F62 and F63 indicate the estimated unit price of fuel at the time of scheduled arrival if the ship calls at a port during the voyage on the planned route R61, and the estimated price to be incurred if the fuel tank is filled to capacity based on the estimated free capacity at the time of the port call.

[0099] According to this aspect, it is possible to know ports that are easy to stop at on the planned route and have cheaper fuel prices than other ports, thereby reducing fuel costs compared to when the fifth display process is not performed. Note that the server device 10 (server display unit 111) may display, as a port image, an image showing the names of ports where refueling is recommended or information on place names that indicate the locations of the ports, overlaid not only on the map but also on the itinerary shown in Figure 7, or may display fuel price information overlaid on the itinerary.

[0100] The server device 10 (server display unit 111) may also display the optimal amount of fuel to be refueled at each port. For example, if the fuel runs out or falls below a certain amount by the time the ship reaches the cheapest port, the server device 10 (server display unit 111) displays the amount of fuel that can be refueled at the cheapest port that can be reached with the current amount of fuel and that allows the ship to sail to the cheapest port (with some margin to spare). The amount of fuel to be refueled in this case is calculated based on the distance along the route between the ports and the amount of fuel consumed per unit distance. This aspect allows for further optimization of fuel costs.

[0101] <Displaying Only AIS Voyage Period> As described above, the server device 10 (AIS processing unit 113: an example of an AIS acquisition unit) acquires AIS information from a ship, and the AIS information includes the ship's departure and arrival schedules. In this case, the server device 10 (server display unit 111: an example of a display unit) may execute a display process to display a schedule that shows the sailing schedule indicating the ship's sailing period indicated by the AIS information acquired by the AIS processing unit 113, in association with the ship.

[0102] When the server device 10 (server display unit 111) functions as an example of a display unit, for example, even if the sailing schedule has not been input in the sailing schedule of the ship A, it displays the sailing schedule of the ship A including the AIS sailing period indicated by the AIS information of the ship A. According to this aspect, regardless of whether the sailing schedule of the ship has been input or not, the sailing schedule of the ship can be grasped more accurately than when the AIS sailing period is not displayed.

[0103] 1 and the like (overall configuration, hardware configuration, functional configuration, etc.) are merely examples, and other configurations may be used as long as they are not inconvenient for implementation. For example, the server device 10 may be distributed across two or more devices, or may be provided in the form of SaaS (Software as a Service) or a cloud computing system.

[0104] 4 may be performed by two or more separate functions, or two or more functions may be integrated into one function. The AIS information DB and schedule information DB shown in FIG. 1 may be integrated, or each may be divided into two or more DBs. In short, as long as the necessary information processing is performed by the entire ship management system 1, the devices that execute this information processing may have any configuration.

[0105] The output destination of information or data (hereinafter referred to as "information, etc.") may be another device, a display, a memory unit (including an internal memory unit and an external memory unit), an email address, an account of another system, etc. Acquisition of information, etc. includes not only acquiring information, etc. transmitted from another device, but also acquiring information, etc. generated by the device itself. Furthermore, the table, etc. (table, database, etc.) in which parameters are associated is not limited to the illustrated table, etc., and the number of parameters may be reduced or increased. Furthermore, information, etc. corresponding to parameters may be obtained using a mathematical formula, a conditional formula, etc., without using a table, etc.

[0106] The above-described embodiments are described as information processing devices such as the server device 10 and information processing systems such as the ship management system 1 including the server device 10, but may also be information processing methods. The information processing methods include processing steps executed by the information processing system. The above-described embodiments may also be programs. The programs cause a computer to execute the processing executed by a similar information processing system.

[0107] <Additional Notes> Furthermore, the present invention may be provided in the following aspects.

[0108] (1) An information processing system having one or more processors, wherein the processor executes a first display process in a first display step to display a schedule reflecting the inputted schedule of a ship, in which a first navigation schedule including the ship's voyage period is displayed in association with the ship; an AIS acquisition step acquires AIS (Automatic Identification System) information from the ship, the AIS information including the ship's departure and arrival schedules; and a second display step executes a second display process to display the schedule in which a second navigation schedule including the ship's voyage period indicated by the acquired AIS information is displayed in association with the ship and displayed separately from the first navigation schedule.

[0109] According to this embodiment, the ship's sailing schedule can be more accurately determined.

[0110] (2) In the information processing system described in (1) above, the processor repeatedly acquires the AIS information in the AIS acquisition step, and in the second display step, if the voyage period of the ship indicated by the acquired AIS information changes, displays the second voyage schedule indicating the changed voyage period.

[0111] According to this embodiment, changes in the voyage situation can be easily grasped.

[0112] (3) In the information processing system described in (1) or (2) above, the processor, in the report acquisition step, acquires a report by email sent from the ship via satellite, and in the second display step, if the acquired report includes location information indicating the position of the ship and the location indicated by the location information indicates that the ship's voyage period will change, displays the second voyage schedule indicating the changed voyage period.

[0113] According to this embodiment, a second sailing schedule that corresponds to changes in circumstances can be displayed even when sailing outside the communication range of an AIS land station.

[0114] (4) In the information processing system described in any one of (1) to (3) above, the schedule includes a non-voyage schedule indicating a period other than the vessel's voyage, and in the first notification step, the processor issues a notification in a predetermined manner if the second voyage schedule overlaps with the non-voyage schedule.

[0115] According to this aspect, it is possible to easily notice the difference between the predicted value and the actual value.

[0116] (5) In the information processing system described in any one of (1) to (4) above, in the first display step, when the departure port and arrival port of the ship are input, the processor reflects in the schedule table as the first navigation schedule a schedule indicating the number of days required for the ship to sail from the departure port to the arrival port.

[0117] According to this aspect, the time and effort required for inputting the schedule can be reduced.

[0118] (6) In the information processing system described in any one of (1) to (5) above, in the third display step, when an operation to select the second navigation schedule is performed, the processor executes a third display process to display a route image showing on a map the position or route of the ship indicated by the AIS information that is the basis of the second navigation schedule.

[0119] According to this aspect, the route of the ship can be easily confirmed.

[0120] (7) In the information processing system described in (6) above, the processor accumulates accident information indicating the location of a ship accident in the accumulation step, and in the third display step, executes a process as the third display process to display, on the route image based on the accumulated accident information, a location image indicating the location of a ship accident that occurred in the sea area indicated by the route image.

[0121] According to this aspect, it is possible to call attention to prevent accidents from occurring in the same place.

[0122] (8) In the information processing system described in (7) above, in the second notification step, the processor notifies the crew of the ship if the distance between the position of the ship and the point where the accident occurred is less than a threshold value.

[0123] According to this aspect, it is possible to quickly alert the driver to the approach of the accident site.

[0124] (9) In the information processing system described in any one of (1) to (8) above, the processor acquires constraint information indicating constraints on the operation of the ship in a constraint acquisition step, and performs a fourth display process in a fourth display step to display candidate operation schedules that comply with the constraints indicated by the acquired constraint information.

[0125] According to this aspect, it is possible to support ship allocation planning.

[0126] (10) In the information processing system described in any one of (1) to (9) above, the processor, in a prediction step, predicts the refueling price at the time of entry at ports where the ship can enter on the planned route, and in a fifth display step, executes a fifth display process to display candidate ports where refueling of the ship is recommended based on the predicted refueling price.

[0127] According to this aspect, fuel costs can be reduced.

[0128] (11) An information processing system comprising a processor, wherein in an AIS acquisition step, the processor acquires AIS information from a ship, the AIS information including the departure and arrival schedules of the ship, and in a display step, the processor executes a display process to display a schedule showing the voyage schedule indicating the voyage period of the ship indicated by the acquired AIS information in correspondence with the ship.

[0129] According to this embodiment, the ship's sailing schedule can be more accurately determined.

[0130] (12) An information processing method comprising the steps of the information processing system according to any one of (1) to (11) above.

[0131] According to this embodiment, the ship's sailing schedule can be more accurately determined.

[0132] (13) A program that causes a computer to execute each step of the information processing system described in any one of (1) to (11) above.

[0133] According to this aspect, it is possible to grasp the sailing schedule of a ship more accurately. Of course, this is not limited to this. Furthermore, the above-described embodiment and modified examples may be implemented in any combination.

[0134] Finally, while various embodiments of the present invention have been described, these are presented by way of example only and are not intended to limit the scope of the invention. The novel embodiments may be embodied in various other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. The embodiments and their modifications are intended to be included within the scope and spirit of the invention, as well as within the scope of the inventions and their equivalents as defined in the appended claims.

[0135] 1, 1a: ship management system, 2: communication line, 3: ship, 4: AIS device, 5: satellite, 6: AIS land station, 10: server device, 11: control unit, 20: user terminal, 21: control unit, 30: crew terminal, 111: server display unit, 112: user authentication unit, 113: AIS processing unit, 114: schedule processing unit, 115: notification processing unit, 211: user display unit, 212: operation reception unit

Claims

1. An information processing system having one or more processors, wherein the processor executes, in a first display step, a first display process for displaying a schedule reflecting the inputted schedule of a ship, the schedule showing a first voyage schedule including the ship's voyage period associated with the ship, the schedule, in association with the ship, the AIS acquisition step, AIS (Automatic Identification System) information from the ship, the AIS information including the ship's departure schedule and arrival schedule, the second display step, a second display process for displaying the schedule showing a second voyage schedule including the ship's voyage period indicated by the acquired AIS information associated with the ship and displayed separately from the first voyage schedule.

2. An information processing system as described in claim 1, wherein the processor, in the AIS acquisition step, repeatedly acquires the AIS information, and, in the second display step, if the voyage period of the ship indicated by the acquired AIS information changes, displays the second voyage schedule indicating the changed voyage period.

3. An information processing system as claimed in claim 1 or claim 2, wherein the processor, in the report acquisition step, acquires a report by e-mail sent from the ship via a satellite; and, in the second display step, if the acquired report includes location information indicating the position of the ship and the location indicated by the location information indicates that the ship's voyage period will change, displays the second voyage itinerary indicating the changed voyage period.

4. An information processing system according to any one of claims 1 to 3, wherein the schedule includes a non-voyage schedule indicating a period other than when the ship is sailing, and in the first notification step, the processor issues a notification in a predetermined manner if the second sailing schedule overlaps with the non-voyage schedule.

5. An information processing system according to any one of claims 1 to 4, wherein in a first display step, when the departure port and arrival port of the ship are input, the processor reflects in the itinerary a schedule indicating the number of days required for the ship to travel from the departure port to the arrival port as the first voyage schedule.

6. An information processing system according to any one of claims 1 to 5, wherein in a third display step, when an operation to select the second navigation schedule is performed, the processor executes a third display process for displaying a route image showing on a map the position or route of the ship indicated by the AIS information on which the second navigation schedule is based.

7. An information processing system as described in claim 6, wherein the processor, in the storage step, stores accident information indicating the location of a ship accident, and in the third display step, executes processing as the third display processing for displaying, on the route image, a location image indicating the location of a ship accident that occurred in the sea area indicated by the route image, based on the stored accident information.

8. An information processing system as described in claim 7, wherein in the second notification step, the processor notifies the crew of the ship if the distance between the position of the ship and the point where the accident occurred is equal to or less than a threshold value.

9. An information processing system according to any one of claims 1 to 8, wherein the processor, in a constraint acquisition step, acquires constraint information indicating constraints on the operation of the ship, and in a fourth display step, executes a fourth display process for displaying candidate operation schedules that comply with the constraints indicated by the acquired constraint information.

10. An information processing system according to any one of claims 1 to 9, wherein the processor, in a prediction step, predicts the refueling price at the time of entry at ports where the ship can enter on its planned route, and in a fifth display step, executes a fifth display process for displaying candidate ports for which refueling of the ship is recommended based on the predicted refueling price.

11. An information processing system comprising a processor, wherein in an AIS acquisition step, the processor acquires AIS information from a ship, the AIS information including the departure and arrival schedules of the ship, and in a display step, executes a display process for displaying a schedule showing the voyage schedule indicating the voyage period of the ship indicated by the acquired AIS information in correspondence with the ship.

12. An information processing method comprising the steps of the information processing system according to any one of claims 1 to 11.

13. A program causing a computer to execute each step of the information processing system according to any one of claims 1 to 11.

Images