Computer-implementing method, system, and computer program

Abstract

To provide a computer-implemented method, a system, and a computer program that enable a recreational fishing boat operation manager to efficiently conduct responsibilities related to vessel departures as prescribed by law.SOLUTION: A computer-implemented method includes the steps of: accepting, by a server, input of a departure schedule of a recreational fishing boat from a recreational fishing boat operation manager; registering the departure schedule in a departure schedule database; causing the server to display, on a terminal of the recreational fishing boat operation manager, an input screen for allowing the operation manager to input data corresponding to the departure schedule registered in the departure schedule database; and registering, in a record database, data input through the input screen. The input screen is configured for allowing the recreational fishing boat operation manager to input at least one piece of data selected from among: before-departure inspection data corresponding to the departure schedule, crew operation record data corresponding to the departure schedule, and catch amount data corresponding to the departure schedule.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to computer-implemented methods, systems, and computer programs. [Background technology]

[0002] The Recreational Fishing Boat Business Regulation Act (hereinafter referred to as the "Act") imposes responsibilities on recreational fishing boats when they depart. These responsibilities include, for example, inspecting and recording recreational fishing boats before departure, conducting alcohol tests, and compiling crew records. These responsibilities are imposed on the recreational fishing boat operations manager. Summary of the Invention

[0003] However, it is cumbersome to carry out pre-departure inspections, record them on paper, and store them.

[0004] Therefore, technical measures are needed to enable recreational fishing vessel operation managers to efficiently carry out their legally mandated responsibilities for setting sail (e.g., pre-departure inspections, compiling crew records, etc.).

[0005] One aspect of the present disclosure is a computer-implemented method executed by a computer. The disclosed method may include displaying an input screen on a terminal that allows a recreational fishing vessel operations manager to input at least one of pre-departure inspection data and crew record data, and registering the data entered on the input screen in a database. The disclosed method also includes, upon receiving a recreational fishing vessel departure schedule, registering the departure schedule in a departure schedule database, providing an input screen for the recreational fishing vessel operations manager to display on the terminal of the recreational fishing vessel operations manager so that the input screen allows the recreational fishing vessel operations manager to input data for the departure schedule registered in the departure schedule database, and registering the data entered on the input screen in a record database. The input screen is configured to prompt the recreational fishing vessel operations manager to input at least one of pre-departure inspection data corresponding to the departure schedule, crew record data corresponding to the departure schedule, and catch volume data corresponding to the departure schedule.

[0006] Another aspect of the present disclosure may be a system or a computer program. Further details will be described in the following embodiments. [Brief explanation of the drawings]

[0007] [Figure 1] Figure 1 is a diagram of the system configuration. [Figure 2] FIG. 2 is a diagram showing the configuration of the server. [Figure 3] Figure 3 shows the relationship between recreational fishing boat operators and departure schedules, etc. [Figure 4] Figure 4 is an explanatory diagram of the responsibilities (duties) of a recreational fishing boat operations manager. [Figure 5] FIG. 5 is an explanatory diagram of the subsystems that make up the system. [Figure 6] FIG. 6 is a flowchart showing the flow of processing by the system. [Figure 7]FIG. 7 is a diagram showing a recreational fishing boat operator database. [Figure 8] FIG. 8 shows databases for recreational fishing vessels, recreational fishing vessel business managers, and departure schedules. [Figure 9] Figure 9 shows the databases for pre-departure inspection, crew records, and catch volume. [Figure 10] FIG. 10 shows the databases of relevant government agencies, users (anglers), and passenger lists. [Figure 11] FIG. 11 is a flowchart of the departure schedule registration process. [Figure 12] FIG. 12 is a flowchart of the pre-departure inspection registration process. [Figure 13] FIG. 13 is a flowchart of the registration process of the driving record. [Figure 14] FIG. 14 is a flowchart of the process for registering the catch amount. [Figure 15] FIG. 15 is a flowchart of the process of viewing the records of pre-departure inspections, etc. [Figure 16] FIG. 16 is a flowchart of the process for viewing the catch amount. [Figure 17] FIG. 17 is a flowchart of the passenger manifest registration process. [Figure 18] FIG. 18 shows a screen of this system. [Figure 19] FIG. 19 shows a screen of this system. [Figure 20] FIG. 20 shows a screen of this system. [Figure 21] Figure 21 shows the items for pre-departure inspection (test). [Figure 22] FIG. 22 shows a screen of this system. [Figure 23] FIG. 23 shows a screen of this system. [Figure 24] FIG. 24 shows a screen of this system. [Figure 25] FIG. 25 shows a screen of this system. [Figure 26]FIG. 26 shows a screen of this system. [Figure 27] FIG. 27 shows a screen of this system. [Figure 28] FIG. 28 shows the items of the crew record. [Figure 29] FIG. 29 shows a screen of this system. [Figure 30] FIG. 30 shows a screen of this system. [Figure 31] FIG. 31 shows a screen of this system. [Figure 32] FIG. 32 shows a screen of this system. [Figure 33] FIG. 33 shows a screen of this system. [Figure 34] FIG. 34 shows a screen of this system. [Figure 35] FIG. 35 shows a screen of this system. [Figure 36] FIG. 36 shows a screen of this system. [Figure 37] FIG. 37 shows a screen of this system. [Figure 38] FIG. 38 shows a screen of this system. [Figure 39] FIG. 39 shows a screen of this system. [Figure 40] FIG. 40 is a diagram showing the relationship between recreational fishing boat operators, recreational fishing boats, and business managers. [Figure 41] Figure 41 shows the relationship between the recreational fishing boat operator and the recreational fishing boat, business manager, captain, crew, and liaison officer. [Figure 42] FIG. 42 is a flowchart showing the procedure for setting a departure schedule. [Figure 43] FIG. 43 shows a screen of this system. [Figure 44] FIG. 44 is a diagram showing the relationship between recreational fishing boat operators and departure schedules. [Figure 45] FIG. 45 shows the relationship between the departure schedule and each data item: passenger list, pre-departure inspection, crew record, and catch volume. [Figure 46] FIG. 46 is a diagram showing the relationship between the departure schedule and the passenger list data. [Figure 47] FIG. 47 shows a screen of this system. [Figure 48] FIG. 48 shows a screen of this system. [Figure 49] FIG. 49 shows a screen of this system. [Figure 50] FIG. 50 shows a screen of this system. [Figure 51] FIG. 51 is a diagram showing the relationship between departure schedules and pre-departure inspection data. [Figure 52] FIG. 52 shows a screen of this system. [Figure 53] FIG. 53 is a diagram showing the relationship between the departure schedule and crew record data. [Figure 54] FIG. 54 shows a screen of this system. [Figure 55] FIG. 55 shows a screen of this system. [Figure 56] FIG. 56 shows a screen of this system. [Figure 57] FIG. 57 shows a screen of this system. [Figure 58] FIG. 58 shows a screen of this system. [Figure 59] FIG. 59 shows a screen of this system. [Figure 60] FIG. 60 shows a screen of this system. [Figure 61] FIG. 61 shows a screen of this system. [Figure 62] FIG. 62 shows a screen of this system. DETAILED DESCRIPTION OF THE INVENTION

[0008] <1. Overview of computer-implemented methods, systems, and programs>

[0009] (1) A method according to an embodiment may be a computer-implemented method executed by a computer. The method according to an embodiment may include displaying an input screen on a terminal for allowing a recreational fishing vessel operations manager to input at least one of pre-departure inspection data and crew record data, and registering the data entered on the input screen in a database. The method according to an embodiment may include, upon receiving input of a recreational fishing vessel departure schedule, registering the departure schedule in a departure schedule database, providing an input screen for the recreational fishing vessel operations manager to display on the terminal of the recreational fishing vessel operations manager so that the input screen allows the recreational fishing vessel operations manager to input data for the departure schedule registered in the departure schedule database, and registering the data entered on the input screen in a record database. The input screen may be configured to prompt the recreational fishing vessel operations manager to input at least one of pre-departure inspection data corresponding to the departure schedule, crew record data corresponding to the departure schedule, and catch volume data corresponding to the departure schedule as the data to be input by the recreational fishing vessel operations manager.

[0010] (2) The method according to the embodiment may further include displaying on the terminal of the recreational fishing vessel operations manager a schedule display screen showing one or more of the departure schedules registered in the departure schedule database. The input screen may be a screen for the recreational fishing vessel operations manager to input data for a departure schedule selected on the schedule display screen.

[0011] (3) It is preferable that the timing of inputting the data is restricted based on the departure time indicated by the departure schedule, and the data can be input at an input time outside the restricted timing.

[0012] (4) The data may only be input by users who have been pre-registered as recreational fishing boat business managers.

[0013] (5) A specific user who is the recreational fishing boat business manager may be associated with the departure schedule, and only the specific user may be able to input the data corresponding to the departure schedule. A recreational fishing boat business manager may be associated with the departure schedule, and only the recreational fishing boat business manager associated with the departure schedule may be able to input the data corresponding to the departure schedule.

[0014] (6) It is preferable that a computer system that executes the computer-implemented method described in any one of (1) to (5) can set the departure schedule for the recreational fishing boat operator's recreational fishing boat by logging in to the system using an account of the recreational fishing boat operator or a related party.

[0015] When the user logs in with the account of the recreational fishing boat operator, a screen displaying the preset sailing schedule for the recreational fishing boat operator is preferably displayed. The input screen displayed on the terminal is preferably an input screen for data corresponding to a sailing schedule selected on the screen displaying the preset sailing schedule.

[0016] (7) It is preferable that a computer system that executes the computer-implemented method described in any one of (1) to (5) can be logged in using an account for logging in to the system, and that the input screen displays one or more pieces of data associated with the logged-in account.

[0017] (8) Preferably, the data associated with the logged-in account includes the name of the recreational fishing vessel operations manager.

[0018] (9) The departure schedule may be associated with the recreational fishing vessel business manager. The recreational fishing vessel business manager associated with the departure schedule may be displayed on the input screen for the data corresponding to the departure schedule.

[0019] (9A) The departure schedule may be associated with the recreational fishing vessel operations manager. One or more recreational fishing vessel operations managers, including the recreational fishing vessel operations manager associated with the departure schedule, may be displayed selectably on the input screen for the data corresponding to the departure schedule.

[0020] (10) Registering the data in the record database may include registering the data included in the departure schedule in the record database together with the data entered on the input screen.

[0021] (10A) Accepting input of the departure schedule may include accepting input for setting a recreational fishing vessel operations manager for each departure schedule. Registering the departure schedule in a departure schedule database may include registering the recreational fishing vessel operations manager for each departure schedule in the departure schedule database. The input screen may be configured to have the recreational fishing vessel operations manager input at least one of pre-departure inspection data corresponding to the departure schedule and crew record data corresponding to the departure schedule as the data to be input by the recreational fishing vessel operations manager. Registering in the record database may include registering in the record database the recreational fishing vessel operations manager registered in the departure schedule corresponding to the pre-departure inspection data or the crew record data as the recreational fishing vessel operations manager in the pre-departure inspection data or the crew record data.

[0022] (10B) The computer-implemented method may further include providing a plurality of departure schedules registered in the departure schedule database to the terminal of the recreational fishing vessel operations manager for display on the terminal, and accepting a selection of a departure schedule from the plurality of departure schedules displayed on the terminal. Providing the input screen to the terminal of the recreational fishing vessel operations manager for display on the terminal may include providing the input screen for the selected departure schedule to the terminal.

[0023] (10C) The computer-implemented method may further comprise providing a selection screen to the terminal of the recreational fishing boat operations manager for displaying on the terminal a selection screen for accepting the selection of a departure schedule into which the data will be input from among a plurality of departure schedules registered in the departure schedule database. Each of the plurality of departure schedules on the selection screen is Pre-departure inspection data corresponding to said departure schedule; crew record data corresponding to said departure schedule; Passenger manifest data corresponding to the departure schedule; and Data on catch volume corresponding to the departure schedule The display may include a display for selecting the data to be input from at least two or more of the data.

[0024] (10D) Each of the plurality of departure schedules on the selection screen is Pre-departure inspection data corresponding to said departure schedule; crew record data corresponding to said departure schedule; and passenger list data corresponding to the departure schedule; may include an indication of

[0025] (11) The method according to the embodiment may further comprise receiving passenger data regarding the departure schedule from the passenger's terminal and registering the data in a passenger list database.

[0026] (11A) A method according to an embodiment is a computer-implemented method executed by a computer, and may include displaying an input screen on a terminal to allow a recreational fishing vessel operations manager to input at least one of pre-departure inspection data and crew record data, and registering the data entered on the input screen in a database.

[0027] (11B) A method according to an embodiment may be a computer-implemented method executed by a computer, in which a recreational fishing boat business manager belonging to a recreational fishing boat operator is registered in association with the recreational fishing boat operator, and the recreational fishing boat business manager registered in association with the recreational fishing boat operator is displayed on a screen displayed on a terminal for inputting data on pre-departure inspections or crew records for the departure of a recreational fishing boat by the recreational fishing boat operator.

[0028] (11C) Displaying the recreational fishing vessel business manager may include displaying one or more registered recreational fishing vessel business managers in a selectable manner.

[0029] (11D) The recreational fishing vessel operations manager may be registered in the system in association with an account for logging in to the system that executes the method.

[0030] (12) In the embodiment, when the system accepts input of a recreational fishing boat departure schedule, it registers the departure schedule in a departure schedule database, and provides an input screen for the recreational fishing boat business manager to input data for the departure schedule registered in the departure schedule database to the terminal of the recreational fishing boat business manager so that the input screen can be displayed on the terminal, and registers the data entered on the input screen in a record database. The input screen may be configured to have the recreational fishing vessel operations manager input, as the data to be input by the recreational fishing vessel operations manager, at least one of pre-departure inspection data corresponding to the departure schedule, crew record data corresponding to the departure schedule, and catch volume data corresponding to the departure schedule.

[0031] (13) A computer program according to an embodiment may cause a computer to execute the following operations: upon receiving an input of a recreational fishing vessel departure schedule, register the departure schedule in a departure schedule database; provide an input screen for a recreational fishing vessel operations manager to input data about the departure schedule registered in the departure schedule database to a terminal of the recreational fishing vessel operations manager to display on the terminal; and register the data entered on the input screen in a record database. The input screen may be configured to prompt the recreational fishing vessel operations manager to input at least one of pre-departure inspection data corresponding to the departure schedule, crew record data corresponding to the departure schedule, and catch volume data corresponding to the departure schedule as the data to be entered by the recreational fishing vessel operations manager.

[0032] 2. Examples of computer-implemented methods, systems, and programs

[0033] Hereinafter, the embodiment will be described in more detail with reference to the drawings.

[0034] FIG. 1 shows a system 100 according to an embodiment. As an example, the system 100 according to an embodiment is a system (pre-departure inspection and crew record system) in which a recreational fishing boat operator (trade name) prescribed by law prepares departure information (departure schedule) in advance for each departure of a recreational fishing boat, and a recreational fishing boat operations manager, who is responsible for the registration of departure information (departure schedule), efficiently executes and manages legally prescribed responsibilities for departure (pre-departure inspection, preparation of crew records, etc.), and stores records of the fulfillment of responsibilities in a database. The records of the fulfillment of responsibilities are stored in a record database. The record database is, for example, at least one of a pre-departure inspection database 34, a crew record database 35, and a catch volume database 36, which will be described later.

[0035] System 100 according to the embodiment is shared by multiple recreational fishing boat operators, and each recreational fishing boat operator can use it by logging in from a terminal using their account. In system 100, each recreational fishing boat operator (or a related party) can log in to system 100 using their account and set a departure schedule for that individual recreational fishing boat operator. In addition, in system 100, each recreational fishing boat operator (or a related party, for example, a recreational fishing boat business manager) can log in to system 100 using their account and enter data on pre-departure inspections of the recreational fishing boats of that recreational fishing boat operator, enter data on crew records for the recreational fishing boats of that recreational fishing boat operator, and so on.

[0036] In system 100, the input screen for entering data for pre-departure inspections, etc. is basically the same regardless of the account used, but information specific to each account (for example, the name of the recreational fishing boat business manager associated with the recreational fishing boat operator's account, or the name of the recreational fishing boat, etc.) may be displayed. In other words, the input screen for entering data for pre-departure inspections, etc. may display an input form common to all recreational fishing boat operators, as well as information specific to each account (for example, the name of the recreational fishing boat business manager associated with the recreational fishing boat operator's account, or the name of the recreational fishing boat, etc.).

[0037] The system 100 may include a server 10 connected to a network 15 such as the Internet. The server 10 is configured by one or more computers. As shown in Fig. 2, the computer configuring the server 10 may include a processor 20 and a storage device 30 connected to the processor 20. The processor 20 is, for example, a CPU.

[0038] The storage device 30 includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 30 includes a computer program executed by the processor 20. The processor 20 reads and executes the computer program stored in the storage device 30. The computer program has program code representing instructions for causing a computer to execute information processing required by the server 10 according to the embodiment.

[0039] The computer program causes the computer to function as various modules shown in Figure 2. For example, when the computer program is executed by the processor 200, it causes the computer to operate as (1) a departure schedule creation module 21, (2) a pre-departure inspection management module 22, (3) a crew record management module 23, (4) a catch volume management module 24, (5) and (6) a relevant government agency connection module 25, and (7) a passenger manifest entry module 26.

[0040] The storage device 30 includes various databases 31A, 31B, 32, 33, 34, 35, 36, 37, 38, and 39 (see also FIGS. 7 to 10). These databases will be described later.

[0041] The server 10 may include an input device 40. The input device 40 is a device for inputting data from the outside to the server 10. The input device 40 may be used, for example, to input data to the server 10. The input device 40 may be a device for inputting data by user operation, such as a keyboard or a mouse, or may be a data communication device for acquiring data from the outside via the network 15.

[0042] The server may include an output device 50. The output device 50 is a device that outputs data. The output device 50 may be used, for example, to output data. The output device 50 may be, for example, a data display device, such as a display device, or may be a data communication device that transmits data to the outside via the network 15.

[0043] Returning to FIG. 1 , the system 100 may include terminals 101, 102, 105, and 107 used by users. The users may be, for example, recreational fishing boat operators, recreational fishing boat business managers, relevant government agencies, anglers, etc. Therefore, the terminals used by the users may be, for example, the terminal device 101 of the recreational fishing boat operator, the terminal device 102 of the recreational fishing boat business manager, the terminal device 105 of the relevant government agency, and the terminal device 107 of the angler (passenger). The server 10 can accept data input from the terminals 101, 102, 105, and 107 and output data to be displayed on the terminals 101, 102, 105, and 107.

[0044] The terminals 101, 102, 105, and 107 are configured by computers such as smartphones, tablets, and personal computers used by users. Similar to the server 10, the computers may include a processor and a storage device connected to the processor. The processor is, for example, a CPU. The storage device includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, a RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The storage device includes a computer program executed by the processor. The processor reads and executes the computer program stored in the storage device. The computer program has program code representing instructions for causing the computer to execute information processing required by the terminals 101, 102, 105, and 107 according to the embodiments.

[0045] The terminals 101, 102, 105, and 107 may include input devices and output devices. The input devices and output devices may be, for example, touch panel displays in smartphones, etc. The input devices and output devices may also be a mouse and keyboard, a display device, etc. in personal computers, etc.

[0046] The terminals 101, 102, 105, and 107 are equipped with communication devices and are capable of communicating with the server 10. The terminals 101, 102, 105, and 107 can transmit data to the server 10 and receive data from the server 10 via the network 15. The terminals 101, 102, 105, and 107 can be connected to the server 10 via, for example, wireless base stations or (wireless) LANs 15A, 15B, 15C, and 15D shown in FIG.

[0047] The terminals 101, 102, 105, and 107 (for example, the terminal 102 of the recreational fishing boat operations manager) may be equipped with location information acquisition means such as GPS. The location information acquisition means can record the location of the terminals 101, 102, 105, and 107 when data is input to the terminals 101, 102, 105, and 107 in a database or the like.

[0048] Figure 3 shows the relationship between recreational fishing boat operators, boats (recreational fishing boats), related parties, and departure schedules in system 100. Related parties may include, for example, the recreational fishing boat business manager, the captain, and crew members. Here, recreational fishing boat business refers to a business that guides passengers to fishing grounds by boat and allows them to catch fish and other aquatic animals and plants by fishing or other methods. Recreational fishing boats refer to vessels used for recreational fishing boat business. Recreational fishing boat operators refer to persons who operate recreational fishing boat businesses after receiving registration under the law.

[0049] A recreational fishing boat business manager is a person who performs duties related to ensuring the safety and protecting the interests of recreational fishing boat users and ensuring stable utilization of fishing grounds, and who conforms to the standards set forth in the Ministry of Agriculture, Forestry and Fisheries Ordinance. Recreational fishing boat operators may be sole proprietors or corporations. The name of a recreational fishing boat operator is sometimes called a trade name. Recreational fishing boat operators must appoint a recreational fishing boat business manager to perform the duties set forth in the Ministry of Agriculture, Forestry and Fisheries Ordinance, including safety management of recreational fishing boat users.

[0050] A recreational fishing boat operator may own one or more boats. In other words, one or more recreational fishing vessels may belong to one recreational fishing boat operator. Figure 3 shows two recreational fishing boats, A and B, belonging to one recreational fishing boat operator. A departure schedule is set for each recreational fishing boat before it departs. For example, in Figure 3, four departure schedules, such as "May 5th, 8:00 AM - 12:00 PM," are set for recreational fishing boat A, and two departure schedules, such as "May 6th, 8:00 AM - 12:00 PM," are set for recreational fishing boat B. A departure schedule may include data indicating at least the time (date and time) of departure, such as "May 5th, 8:00 AM - 12:00 PM." A recreational fishing boat operator may be assigned one or more recreational fishing boat business managers. A recreational fishing boat operator may be assigned one or more captains. A recreational fishing boat operator may be assigned one or more crew members (employees). One person may hold two or more of the roles of recreational fishing vessel operations manager, captain, and crew member (employee).

[0051] As shown in Figure 3, each departure schedule may be set with the parties involved in the departure. As shown in Figure 3, the parties involved are, for example, the recreational fishing boat operations manager, the captain, and crew members. In Figure 3, for example, the departure schedule for recreational fishing boat A, "May 5th, 8:00 - 12:00," is associated with recreational fishing boat operations manager A1, captain A1, and crew member A1. Here, an example is shown in which one person A1 serves as recreational fishing boat operations manager, captain, and crew member. Each departure schedule has data indicating the date and time of departure, and may be associated with a single recreational fishing vessel. One or more recreational fishing boat operations managers may be associated with each departure schedule. One or more captains may be associated with each departure schedule. One or more crew members (employees) may be associated with each departure schedule.

[0052] As shown in Figure 4, the recreational fishing vessel operations chief must confirm the implementation of (2) the pre-departure inspection (pre-departure inspection) before departure and keep a record of the inspection. In addition, the recreational fishing vessel operations chief must conduct alcohol tests on the captain, operations chief, and crew before departure, prepare a record, and keep a record of the inspection.

[0053] As shown in Figure 4, after returning to the voyage, the recreational fishing vessel operations manager must prepare (3) a crew record (including weather and sea conditions, guided sea areas, and any accidents that occurred). It is also recommended that the recreational fishing vessel operations manager report (4) the catch volume to the Fisheries Agency, etc.

[0054] 5 and 6 show subsystems 200, 300, and 400 that make up the system 100 according to the embodiment. The system 100 may include, for example, a recording system 200 for (1), (2), (3), and (4) pre-departure inspection (pre-departure inspection), crew records, etc. The recording system 200 accepts (1) registration of a departure schedule (in advance before departure) from a terminal 101 or the like of a recreational fishing boat operator, etc., and registers the departure schedule in the system 100 (its departure schedule database 33).

[0055] The recording system 200 accepts data input for recording (2) pre-departure inspection (pre-departure inspection) from the recreational fishing boat operations manager's terminal 102 before departure for the departure schedule registered in the system 100, and registers the pre-departure inspection data in the system 100 (pre-departure inspection database 34; recording database 34). The pre-departure inspection data is registered in association with the corresponding departure schedule.

[0056] After the return (return to port), the recording system 200 accepts (3) crew record data input from the recreational fishing boat operations manager's terminal 102 and registers the crew record data in the system 100 (crew record database 35; recording database 35). The crew record data is registered in association with the corresponding departure schedule.

[0057] After the vessel returns to port, the recording system 200 receives data input for recording the catch volume (4) from the recreational fishing vessel operations manager's terminal 102, and registers the catch volume data in the system 100 (catch volume database 35; recording database 36). The catch volume data is registered in association with the corresponding departure schedule.

[0058] The system 100 may include, as a subsystem 300, (5) and (6) a related government agency data linkage system 300. The linkage system 300 accepts access from the terminal 105 of the related government agency and provides the data registered in the record databases 34, 35, and 36 to the terminal 105 of the related government agency for display on the terminal 105 so that the person in charge of the related government agency can view (5) the pre-departure inspection record and crew record, and (6) the catch volume.

[0059] The system 100 may include (7) a passenger manifest system 400 as a subsystem 400. A passenger manifest is a list of passengers on a recreational fishing boat. The passenger manifest includes data such as name, gender, date of birth, and emergency contact information (see the passenger manifest database 39 in Figure 10). The passenger manifest is useful for identifying passengers in the event of an accident or other incident, and it is desirable to record and store the passenger manifest. To facilitate the creation of a passenger manifest, the passenger manifest system 400 accepts input of passenger data from the terminal 107 of passengers, such as anglers, before boarding the boat, and registers the passenger data in the system 100 (the passenger manifest database 39). This eliminates the need for passengers to write their names and other information on a paper passenger manifest. Furthermore, compared to a paper passenger manifest, the passenger manifest is easier to store and manage.

[0060] The passenger manifest data (passenger data) is registered in association with the corresponding departure schedule. In other words, the passenger manifest system 400 accepts input of passenger data corresponding to the departure schedule and registers the passenger data in the system 100. In this way, not only are pre-departure inspection records or crew records, etc. associated and registered with the departure schedule set before departure, but the passenger manifest data can also be associated and registered. Therefore, for each departure schedule, not only can the pre-departure inspection records or crew records, etc. be recorded and saved, but the passenger manifest can also be recorded and saved, which is convenient.

[0061] FIG. 7 shows recreational fishing boat operator database 31A. Recreational fishing boat operator database 31A shows recreational fishing boat operators registered in system 100. Recreational fishing boat operator database 31A has the data items shown in FIG. 7. In FIG. 7, the system user (system user administrator) is the person (person in charge) who uses system 100 as a recreational fishing boat operator. The system user has an account (and password) for logging in to system 100 from terminal 101 as a recreational fishing boat operator. A user who logs in to system 100 with the account of a system user who is a recreational fishing boat operator can set a departure schedule. It is preferable that the ability to set departure schedules be limited to users who log in to system 100 with the account of a system user who is a recreational fishing boat operator, but other users may also be able to set departure schedules.

[0062] In addition, a recreational fishing boat operator may also serve as a recreational fishing boat business manager. When a recreational fishing boat operator also serves as a recreational fishing boat business manager, the "concurrent position flag" in Figure 7 is set to 1 (applicable). When a recreational fishing boat operator also serves as a recreational fishing boat business manager, the recreational fishing boat operator can set departure schedules and can also use the functions of system 100 that correspond to the tasks that a recreational fishing boat business manager should perform, such as recording pre-departure inspections.

[0063] Figure 8 shows the recreational fishing vessel database 31B (recreational fishing vessel database 31B). The recreational fishing vessel database 31B shows data related to recreational fishing vessels. The recreational fishing vessels shown in Figure 8 are associated with the recreational fishing vessel operator that owns the vessel or the recreational fishing vessel operator to which the vessel belongs. In other words, the recreational fishing vessel database 31B shown in Figure 8 is associated with one of the individual recreational fishing vessel operators registered in the recreational fishing vessel operator database 31A shown in Figure 7 (see also Figure 40). As shown in Figure 8, recreational fishing vessels have a recreational fishing vessel ID (recreational fishing vessel ID; recreational fishing vessel identifier). In the system 100, individual recreational fishing vessels are identified by their recreational fishing vessel identifiers.

[0064] FIG. 8 also shows the recreational fishing boat business manager database 32. The recreational fishing boat business manager database 32 shows data related to recreational fishing boat business managers. The recreational fishing boat business managers shown in FIG. 8 are associated with the recreational fishing boat operators to which they belong (see also FIG. 40). In other words, the recreational fishing boat business manager database 32 shown in FIG. 8 is associated with one of the individual recreational fishing boat operators registered in the recreational fishing boat operator database 31A shown in FIG. 7.

[0065] A person registered in the recreational fishing boat business manager database 32 as a recreational fishing boat business manager has an account (and password) for logging in to the system 100 from the terminal 102 as a recreational fishing boat business manager. A user who logs in to the system 100 with a recreational fishing boat business manager's account can input data such as pre-departure inspection records and crew records. A recreational fishing boat business manager can input data such as pre-departure inspection records and crew records for the departure schedule of a recreational fishing boat operator associated with that recreational fishing boat business manager or the departure schedule of that recreational fishing boat operator's recreational fishing boat. It is preferable that the ability to input data such as pre-departure inspection records and crew records be limited to users who log in to the system 100 with a recreational fishing boat business manager's account (including recreational fishing boat operators when the recreational fishing boat operator also serves as a recreational fishing boat business manager). Furthermore, it is preferable that users (recreational fishing boat business managers) who can input data such as pre-departure inspection records and crew records corresponding to the departure schedule of a certain recreational fishing boat operator are limited to users (recreational fishing boat business managers) associated with that recreational fishing boat operator. In other words, even if a recreational fishing boat business manager is registered in system 100, it is preferable that he or she cannot input data such as pre-departure inspection records and crew records corresponding to the departure schedule of a recreational fishing boat operator other than the recreational fishing boat operator to which the recreational fishing boat business manager belongs.

[0066] As mentioned above, a recreational fishing boat business manager may also serve as a recreational fishing boat operator. If a recreational fishing boat business manager also serves as a recreational fishing boat operator, the "concurrent position flag" in Figure 8 is set to 1 (applicable). If a recreational fishing boat business manager also serves as a recreational fishing boat operator, the recreational fishing boat business manager can also set the departure schedule for the recreational fishing boat operator's recreational fishing boats.

[0067] FIG. 8 also shows the departure schedule database 33. The departure schedule database 33 shows data related to departure schedules registered in the system 100. In the departure schedule database, a departure schedule has a departure schedule ID (departure schedule identifier) ​​for identifying each departure schedule. The departure schedule also has data indicating the recreational fishing vessel associated with the departure schedule (recreational fishing vessel ID; recreational fishing vessel identifier). The departure schedule also has data indicating the time of departure, specified by the departure date and time, return date and time (return date and time), etc. The departure schedule also has data indicating the recreational fishing vessel business manager associated with the departure schedule (recreational fishing vessel business manager ID; recreational fishing vessel business manager identifier). As an example, in the system 100, only the recreational fishing vessel business manager who is associated with the departure schedule in advance can input data such as pre-departure inspection records and crew records. Note that the recreational fishing vessel business manager does not need to be associated with the departure schedule in advance. In this case, when data such as pre-departure inspection records and crew records are entered for a certain departure schedule, the recreational fishing boat operations manager (or his / her identifier) ​​who entered the data can be registered in database 33 in association with that departure schedule.

[0068] FIG. 9 shows the pre-departure inspection database 34. The pre-departure inspection database 34 shows data on inspections (tests) of recreational fishing vessels conducted before departure (records of pre-departure inspections (pre-departure inspections)). In the pre-departure inspection database 34, the pre-departure inspection data has a departure schedule ID (identifier of the departure schedule) corresponding to the pre-departure inspection. The pre-departure inspection data also has the recreational fishing vessel operations manager ID (identifier of the recreational fishing vessel operations manager) who entered the pre-departure inspection data. The pre-departure inspection data may also have data indicating the date and time of the pre-departure inspection (the date and time the pre-departure inspection data was entered). The pre-departure inspection data may also have data indicating the location of the pre-departure inspection (e.g., latitude and longitude; the location where the pre-departure inspection data was entered). The location of the pre-departure inspection can be registered by acquiring the location of the terminal 102 at the time the pre-departure inspection data is entered using location information acquisition means such as a GPS function provided in the terminal 102 of the recreational fishing boat operations manager, and transmitting that location to the server 10. By registering the location of the pre-departure inspection, it can be confirmed when data is entered at a location other than the recreational fishing boat or its vicinity.

[0069] The pre-departure inspection data may also include the IP address of the pre-departure inspection terminal. The IP address of the pre-departure inspection terminal indicates the IP address of the terminal 102 of the recreational fishing vessel operations manager who entered the data. The IP address of the pre-departure inspection terminal makes it possible to confirm that the pre-departure inspection data was entered by the appropriate terminal 102. The pre-departure inspection data may also include the MAC address of the terminal 102 of the recreational fishing vessel operations manager who entered the data. In this way, the pre-departure inspection data may include data for identifying the terminal 101 that entered the data.

[0070] The pre-departure inspection data may include data indicating the inspection results for each item in the pre-departure inspection. The items in the pre-departure inspection will be described later. The pre-departure inspection data may include the update date and time of the pre-departure inspection data.

[0071] FIG. 9 also shows the crew record database 35. The crew record database 35 shows crew record data entered after returning to port (returning to voyage). In the crew record database 35, the crew record data has a departure schedule ID (identifier of the departure schedule) corresponding to the crew record. The crew record data also has the recreational fishing boat operations manager ID (identifier of the recreational fishing boat operations manager) who entered the crew record data. The crew record data may also have data indicating the crew record date and time (the date and time the crew record data was entered). The crew record data may also have data indicating the location of the crew record (e.g., latitude and longitude; the location where the crew record data was entered). The location of the crew record may be registered by acquiring the location of the terminal 102 at the time the crew record data was entered using location information acquisition means such as a GPS function provided in the recreational fishing boat operations manager's terminal 102, and transmitting that location to the server 10. By registering the location of the crew record, it is possible to confirm when data is entered at a location other than a recreational fishing vessel or its vicinity.

[0072] The crew record data may also include a crew record terminal IP address. The crew record terminal IP address indicates the IP address of the terminal 102 of the recreational fishing boat operations manager who entered the data. The crew record terminal IP address makes it possible to confirm that the crew record data was entered by the appropriate terminal 102. The crew record data may also include the MAC address of the terminal 102 of the recreational fishing boat operations manager who entered the data. In this way, the crew record data may include data for identifying the terminal 101 on which the data was entered.

[0073] The data of the work record may include data on each item of the work record. The items of the work record will be described later. The data of the work record may include the update date and time of the data of the work record.

[0074] FIG. 9 also shows the catch volume database 36. The catch volume database 36 shows data on the catch volume for each departure schedule. The catch volume is entered after returning to port (returning voyage). In the catch volume database 36, the catch volume data has a departure schedule ID (departure schedule identifier) ​​corresponding to that catch volume. The catch volume data indicates the species, size, number, etc. of fish caught during that departure.

[0075] FIG. 10 shows the relevant government agency database 37. The relevant government agency database 37 has the IDs (personnel accounts) of personnel who can log in to the system 100 and data related to those personnel. Personnel registered in the relevant government agency database 37 can log in to the system 100 and view data such as pre-departure inspections and crew records.

[0076] 10 also shows a user (passenger such as angler) database 38 and a passenger list database 39. The passenger list database 39 shows passenger data for each departure schedule. In the system 100, passenger data is input by passengers from their terminals 107 before departure. If passengers are registered in the user database 38 in advance, the information in the user database 38 can be automatically registered in the passenger list database 39 as passenger data.

[0077] Figure 11 shows the departure schedule registration process by the system 100 ((1) departure schedule creation module 21). When the recreational fishing boat operator's terminal 101 or the like receives an operation to register a departure schedule, the server 10 accepts the departure schedule (acquires the departure schedule) and registers the departure schedule in the departure schedule database 33. The departure schedule is registered before departure. The departure schedule can be set for each recreational fishing boat operator, and can also be set for each recreational fishing boat belonging to that recreational fishing boat operator. It is preferable that the departure schedule include data indicating the recreational fishing boat business manager corresponding to the departure schedule (such as the identifier of the recreational fishing boat business manager).

[0078] Figure 12 shows the registration process of pre-departure inspection records by system 100 ((2) Pre-departure inspection management module 22). A recreational fishing boat business manager (including a recreational fishing boat operator when the recreational fishing boat operator also serves as the recreational fishing boat business manager; the same applies below) logs in to server 10 from their terminal 102. If server 10 determines that the ID (login account) of the person who logged in is a recreational fishing boat business manager ID (recreational fishing boat business manager ID authentication), it extracts one or more departure schedules corresponding to that recreational fishing boat business manager ID (recreational fishing boat business manager identifier) ​​from the departure schedule database 33. Server 10 may also extract departure schedules corresponding to the recreational fishing boat operator to which that recreational fishing boat business manager belongs. In this case, departure schedules associated with other recreational fishing boat business managers belonging to that recreational fishing boat operator are also extracted. The server 10 provides the extracted data of one or more departure schedules to the terminal 102 for display on the screen of the terminal 102. Of the extracted departure schedules, the departure schedule closest to the date and time at the time of display can be displayed.

[0079] The recreational fishing boat operations manager operates terminal 102 to select from one or more displayed departure schedules the departure schedule for which he wishes to input pre-departure inspection data.

[0080] When the server 10 accepts that an operation to select a departure schedule has been performed on the terminal 102, it acquires (generates) an input form (input screen) for recording the pre-departure inspection for the selected departure schedule. The input form (input screen) is configured so that the recreational fishing boat operations manager can input the pre-departure inspection data. The server 10 provides (outputs) the generated input form (input screen) to the terminal 102 for screen display on the terminal 102. The input form (input screen) provided to the terminal 102 is displayed on the display of the terminal 102.

[0081] The data entered by the recreational fishing vessel operations manager into the input form displayed on the terminal 102, as well as other necessary data, is transmitted from the terminal 102 to the server 10. The server 10 receives the transmitted data and registers it in the pre-departure inspection database 34.

[0082] In the procedure shown in Figure 12, the recreational fishing boat business manager ID authentication does not have to be performed. For example, a recreational fishing boat business manager may log in to system 100 using a recreational fishing boat operator ID (recreational fishing boat operator ID) and select a recreational fishing boat business manager from the list of recreational fishing boat business managers displayed, and a departure schedule corresponding to the selected recreational fishing boat business manager may be extracted. Also, without selecting a recreational fishing boat business manager, a departure schedule corresponding to the logged-in recreational fishing boat operator or the recreational fishing boat of that recreational fishing boat operator may be extracted. The login may be performed by someone related to the recreational fishing boat operator.

[0083] In the step of extracting a departure schedule corresponding to a recreational fishing vessel business manager ID, if the scheduled departure time has already passed, the schedule may not be extracted. In other words, even if a departure schedule corresponds to a recreational fishing vessel business manager ID, a departure schedule for which the scheduled departure time has passed will not be extracted. Therefore, it is preferable that pre-departure inspection data cannot be input after the scheduled departure time. In this way, in system 100, the timing of inputting data such as pre-departure inspections is restricted based on the departure time indicated by the departure schedule (e.g., the scheduled departure time), and data such as pre-departure inspections can only be input outside of the restricted timing (e.g., before the scheduled departure time). However, this restriction can also be lifted. In other words, data may be input after the scheduled departure time. Even if data input is possible, by registering the data input time, if data is input after the scheduled departure time, it is possible to confirm the data after the fact.

[0084] Furthermore, in order to prevent the input of pre-departure inspection data after departure, GPS information may be used in addition to the scheduled departure time to exclude cases where the terminal 102 has moved from the boarding location toward the sea, and pre-departure inspection data may not be input. Data input may also be possible even when the terminal has moved toward the sea, and in this case, the data input location may be registered so that it can be confirmed after the fact.

[0085] FIG. 13 shows the crew record registration process by the system 100 ((3) crew record management module 23). A recreational fishing boat business manager (including a recreational fishing boat operator when the recreational fishing boat operator also serves as the recreational fishing boat business manager; the same applies below) logs in to the server 10 from their terminal 102. If the server 10 determines that the ID (login account) of the person who logged in is a recreational fishing boat business manager ID (recreational fishing boat business manager ID authentication), it extracts from the departure schedule database 33 one or more departure schedules that correspond to the recreational fishing boat business manager ID (recreational fishing boat business manager identifier) ​​and that have already departed (those that have passed the scheduled departure time in the departure schedule). The server 10 may also extract departure schedules that correspond to the recreational fishing boat operator to which the recreational fishing boat business manager belongs. In this case, departure schedules associated with other recreational fishing boat business managers belonging to the recreational fishing boat operator are also extracted. The server 10 provides the extracted data of one or more departure schedules to the terminal 102 for display on the screen of the terminal 102. Of the extracted departure schedules, the departure schedule closest to the date and time at the time of display can be displayed.

[0086] The recreational fishing boat operations manager operates terminal 102 to select from one or more displayed departure schedules the departure schedule for which he wishes to input crew record data.

[0087] When the server 10 accepts that an operation to select a departure schedule has been performed on the terminal 102, it acquires (generates) an input form (input screen) for the crew record for the selected departure schedule. The input form (input screen) is configured so that the recreational fishing boat operations manager can input crew record data. The server 10 provides (outputs) the generated input form (input screen) to the terminal 102 for screen display on the terminal 102. The input form (input screen) provided to the terminal 102 is displayed on the display of the terminal 102.

[0088] The data entered by the recreational fishing boat operations manager into the input form displayed on the terminal 102, as well as other necessary data, is transmitted from the terminal 102 to the server 10. The server 10 receives the transmitted data and registers it in the crew record database 35.

[0089] In the procedure shown in Figure 13, the recreational fishing boat business manager ID authentication does not have to be performed. For example, a recreational fishing boat business manager may log in to system 100 using a recreational fishing boat operator ID (recreational fishing boat operator ID) and select a recreational fishing boat business manager from the list of recreational fishing boat business managers displayed, and a departure schedule corresponding to the selected recreational fishing boat business manager may be extracted. Also, without selecting a recreational fishing boat business manager, a departure schedule corresponding to the logged-in recreational fishing boat operator or the recreational fishing boat of that recreational fishing boat operator may be extracted. The login may be performed by a person related to the recreational fishing boat operator.

[0090] In the step of extracting a departure schedule corresponding to a recreational fishing boat operations manager ID, if the scheduled departure time or scheduled return time to port (return) has not yet passed, the schedule may be extracted, but it is preferable that it is not excluded. In other words, even if a departure schedule corresponds to a recreational fishing boat operations manager ID, a departure schedule for which the scheduled departure time or scheduled return time to port (return) has not yet passed is preferably not extracted. Therefore, it is preferable that crew record data cannot be input before the scheduled departure time or scheduled return time to port (return). In this way, in system 100, the timing of input of crew record data is restricted based on the departure time indicated by the departure schedule (e.g., the scheduled departure time or the scheduled return time to port (return)). Data such as crew record data can only be input at input times outside the restrictions (e.g., after the scheduled departure time or the scheduled return time to port (return)). However, this restriction can also be lifted. In other words, input may be possible even before the scheduled departure time. Even if data entry is possible, by registering the time of data entry, if data is entered before the scheduled departure time, it can be confirmed after the fact.

[0091] Furthermore, in order to prevent the input of crew record data before departure or return to port, GPS information may be used in addition to the scheduled departure time, etc., so that crew record data cannot be input even when the terminal 102 has not moved out to sea from the boarding location. Data input may also be possible even when the terminal has not moved out to sea, and in this case, the data input location can be registered and checked after the fact.

[0092] Figure 14 shows the process of registering catches by the system 100 ((4) Catch Volume Management Module 24). The catch volume can also be registered in the system 100 catch volume database 36 from the recreational fishing boat operations manager's terminal 102, just like the pre-departure inspection records and crew records.

[0093] 15 and 16 show the procedure for viewing pre-departure inspection records, etc., using the system 100 ((5)(6) relevant government agency connection module 25). As shown in FIG. 15, relevant government agencies can view pre-departure inspection records, etc., registered in the system 100.

[0094] Figure 17 shows the procedure for registering a passenger list by the system 100 ((7) passenger list entry module 26). To enter information into the passenger list and give consent for boarding, a user (passenger) such as an angler selects the relevant passenger list (departure schedule) in the passenger list entry system 400 from their own terminal 107 and enters the required information into the passenger list entry form. If the user (passenger) has already created an account, the required information can be automatically entered by logging into the system with the user's ID and password. Note that the user (angler) can use the passenger list entry function without registering an account. In this case, there is no need to log in to the passenger list entry system 400, authenticate the user's (angler's) ID, and complete the process of logging in.

[0095] To log in or access the system from the terminal 107, a user (passenger) such as an angler may read a two-dimensional code for logging in or accessing the system, or may wirelessly connect the terminal 107 to another terminal (e.g., the terminal 101 of a recreational fishing boat operator) and obtain information for logging in or accessing from that terminal 101. The recreational fishing boat operator may provide the user (passenger) such as an angler with a URL to a passenger list input form (passenger list input screen) corresponding to the departure schedule for which the user (passenger) is scheduled to board. The user (passenger) such as an angler may use the URL to display the passenger list input screen in a browser. The URL may be generated, for example, based on the ID of the departure schedule. The URL may be converted into a two-dimensional code and read by the terminal 107.

[0096] FIG. 18 shows an example of a departure schedule screen displayed on the terminal 101 of a recreational fishing boat operator or the terminal 102 of a recreational fishing boat business manager. When a recreational fishing boat operator or a recreational fishing boat business manager belonging to that recreational fishing boat operator logs in to the system 100 using their account, the departure schedule set for that recreational fishing boat operator is displayed on the screen (home screen) of FIG. 18. As an example, the screen of FIG. 18 displays the current day (today) and several days before and / or after that as selectable dates, and displays the departure schedule for the selected date. The departure schedule screen of FIG. 18 displays data previously registered as the departure schedule (recreational fishing boat name (Monaka Maru), fish to be caught (red sea bream), departure date and time (Monday, March 10, 8:00-14:00), recreational fishing boat business manager (Takeda Hayato), fishing grounds (Kishiwada Port), etc.). The departure schedule screen in Figure 18 also displays the number of people currently registered on the passenger list (registered passengers) at the time of display. By operating this screen (for example, by tapping on the screen), the recreational fishing boat operations manager can display a screen (input form) for entering data on the pre-departure inspection record and crew record corresponding to the departure schedule. The screen in Figure 18 can also be viewed by recreational fishing boat operators. Recreational fishing boat operators or recreational fishing boat operations managers can also operate the screen in Figure 18 to display the registered passenger list for each departure schedule.

[0097] As shown in FIG. 18, the screen displaying the departure schedule displays, for each departure schedule, a button for entering pre-departure inspection data, a button for entering crew record data, and a button for displaying the crew roster, etc. Therefore, by selecting a departure schedule on the screen of FIG. 18, data such as the pre-departure inspection, crew record, and crew roster corresponding to that departure schedule can be easily entered. Furthermore, the recreational fishing boat operator or the recreational fishing boat business manager can also enter or edit the crew roster on behalf of the angler (passenger) by operating the screen. Furthermore, the recreational fishing boat operator or the recreational fishing boat business manager can upload a photograph (image) of a handwritten roster (e.g., a paper roster) to the system 100 and store it in the system 100's crew roster DB (see FIG. 35). The recreational fishing boat operator or the recreational fishing boat business manager can also register a new departure schedule (roster) by operating the screen of FIG. 18 (adding a new roster).

[0098] 19 to 23 show input screens for pre-departure inspection records. FIG. 19(A) shows that the input of pre-departure inspection data for a certain departure schedule has not yet been completed. When an operation to select a displayed departure schedule is performed on the screen of FIG. 19(A), the screen shown in FIG. 19(B) is displayed. The screen of FIG. 19(B) displays the data for the selected departure schedule (recreational fishing vessel name (Monaka Maru 20), fishing target (red sea bream), departure date and time (Saturday, March 2, 2024), recreational fishing vessel business manager (Hayashi), fishing ground (Osaka Bay), etc.). Therefore, the recreational fishing vessel business manager does not need to input this departure schedule data during the pre-departure inspection, which is convenient. Furthermore, the above data registered in the departure schedule can be automatically saved in the crew record database as pre-departure inspection data, but the data can also be modified on the crew record input screen. For example, data such as the fishing target and recreational fishing vessel business manager for the departure schedule can be modified on the pre-departure inspection input screen. When "Start pre-departure inspection" is selected in FIG. 19(B), a screen (input form) for inputting each item of the pre-departure inspection shown in FIGS. 20(A), 20(B), and 20(C) is displayed. In the input screen (input form) shown in FIG. 20, the fields for inputting each inspection result item of the pre-departure inspection display the same content for each recreational fishing boat operator (or related party) regardless of the account used to log in. However, the name of the "recreational fishing boat," the "fishing object," and the name of the recreational fishing boat business manager in the departure schedule corresponding to the pre-departure inspection display data specific to each account. For example, the name of the recreational fishing boat and the name of the recreational fishing boat business manager displayed at the top of FIG. 20(A) are data specific to the logged-in account. The account-specific data is displayed, for example, by referring to data set by the system 100 in the departure schedule corresponding to the pre-departure inspection. Furthermore, the account-specific data is displayed by referring to data associated with the account used to log in to the system 100.

[0099] Figure 21 shows each item in the pre-departure inspection. Figures 22(A) and 22(B) show the screen when the data entry for the pre-departure inspection is complete, with Figure 22(A) showing the case where the pre-departure inspection is normal and Figure 22(B) showing the case where there are deficiencies. Figures 23(A) and 23(B) show the screen for correcting deficiencies, and Figures 23(C) and 23(D) show the screen showing the departure schedule when the pre-departure inspection is normal.

[0100] As shown in Figures 20 and 21, the pre-departure inspection items include an alcohol test. In Figure 20, the alcohol test result is entered as a number, but instead of or in addition to this, an image of the screen or display showing the alcohol test result on the breathalyzer may be uploaded to the system 100 and stored as part of the pre-departure inspection data. Furthermore, the system 100 may recognize the test result (such as a numerical value indicating the test result) from the uploaded image, and the recognized test result may be automatically reflected as the alcohol test result (numerical value) on the screen shown in Figure 20(C).

[0101] 24 to 28 show screens for inputting crew records, etc. FIG. 24(A) shows that the input of crew record data for a certain departure schedule has not yet been completed. When an operation to select a displayed departure schedule is performed on the screen of FIG. 24(A), the screen shown in FIG. 24(B) is displayed. The screen of FIG. 24(B) displays the data of the selected departure schedule (recreational fishing vessel name (Monaka Maru 20), fishing target (red sea bream), departure date and time (Saturday, March 2, 2024), recreational fishing vessel business manager (Hayashi), fishing ground (Osaka Bay), etc.). Therefore, when inputting crew records, the recreational fishing vessel business manager does not need to input this departure schedule data, which is convenient. Furthermore, the above data registered in the departure schedule can be saved in the crew record database as crew record data, but the data can also be modified on the crew record input screen. For example, the return time of the departure schedule can be modified to the actual return time on the crew record input screen. When "Start crew record" is selected on the screen of Figure 24(B), a screen (input form) for inputting each item of the crew record shown in Figures 25 to 27 is displayed. In Figures 25 to 27, the data registered in the departure schedule (which may be the departure schedule in the passenger manifest) is automatically reflected and displayed. Even in data reflected from the departure schedule (passenger manifest), data items that may be changed can be edited (modified). Figure 28 shows each item of the crew record. Figures 24(C) and (D) show screens showing the departure schedule when the entry of the crew record is normal.

[0102] In the input screens (input forms) shown in Figures 25 to 27, the fields for entering crew record items basically display the same content regardless of which recreational fishing boat operator's (or related party's) account is used to log in, but the name of the "recreational fishing boat," "fishing target," and "name of recreational fishing boat operations manager" in the departure schedule corresponding to the crew record display data specific to each account. For example, the name of the recreational fishing boat and the name of the recreational fishing boat operations manager displayed at the top of Figure 25 are data specific to the logged-in account. The account-specific data is displayed, for example, by the system 100 referencing data set in the departure schedule corresponding to the crew record. Furthermore, the account-specific data is displayed by the system 100 referencing data associated with the account used to log in to the system 100.

[0103] 29 and 30 show screens for setting the passenger list and departure schedule from the recreational fishing boat operator's terminal 101, etc. FIG. 29(A) shows a two-dimensional code to be read by the passenger's terminal 107. The two-dimensional code may be generated for each departure schedule, for example, based on the departure schedule's ID (identifier). FIG. 29(B) shows a screen for adding a new passenger list (departure schedule). Here, as an example, when a new passenger list is added, new departure schedule data is added and the passenger list is registered for that departure schedule. In this way, the departure schedule and passenger list data may be integrated data or may be separate data. FIG. 29(C) shows a screen for setting the "fish" in the new passenger list (new departure schedule). FIG. 29(D) shows a screen for setting the "departure time" (scheduled departure time) in the new passenger list (new departure schedule). Figure 29(E) shows a screen for setting the "return time" (scheduled return time) in a new boarding list (new departure schedule). Figure 29(F) shows a screen for setting the "fishing area" in a new boarding list (new departure schedule). Figure 30(A) shows a screen for setting the responsible "recreational fishing boat business manager" in a new boarding list (new departure schedule). The recreational fishing boat business manager set here is registered as the recreational fishing boat business manager associated with that boarding list (or departure schedule). Figures 30(B) and (C) are screens showing the set information and completion of the setting.

[0104] For reference, Figures 31 to 39 show examples of screens that may be displayed on a terminal of this system, including screens that have already been described with reference to figures prior to Figure 31.

[0105] "1. Login" in Figure 31 is a screen that allows recreational fishing boat operators to log in to the system 100 from the terminal 101. Here, recreational fishing boat operators, captains, crew members (employees), and contact persons who belong to the recreational fishing boat operator can also log in as recreational fishing boat operators. However, the functions available after logging in may differ depending on the role of the logged-in user, whether that user is a recreational fishing boat operator, captain, crew member (employee), or contact person. Once logged in, the menu screen shown in Figure 39 (display button for displaying the hamburger menu (the "three lines" displayed in the upper right corner of "2. Home" in Figure 31; hamburger menu button)) is displayed.

[0106] When "Passenger Roster QR Code" is selected on the menu screen of Figure 39, a QR Code (registered trademark) is displayed, as shown in "2. Home" of Figure 31, allowing the angler (passenger) to access the passenger roster input screen. A QR code (two-dimensional code) is generated for each created departure schedule (passenger roster). The QR code (two-dimensional code) is generated, for example, from a URL that includes an identifier for the departure schedule (or passenger roster). The angler (passenger) can easily access the passenger roster input screen for a specific departure schedule by reading the QR code corresponding to the departure schedule (or passenger roster) with terminal 107.

[0107] "3. Today's Roster List" in Figure 32 allows you to register daily departure schedules. If you want to register a new boarding roster for a certain day (new departure schedule), select the date you want to register (in Figure 32, "Today", March 15, 2024), and then select the "+ Add New Roster" button. Then, as shown in Figure 32, the "recreational fishing boats" that can be selected for that departure schedule will be displayed. The "recreational fishing boats" that are displayed as selectable are the recreational fishing boats associated with the recreational fishing boat operator that you logged in with.

[0108] Next, the "fishing target," "departure time," "return time," and "fishing area" for the departure schedule to be registered are entered as shown in Figure 33. On the "fishing target" and "fishing area" input screen, the "fishing target" and "fishing area" for other departure schedules that have already been registered are displayed as options, allowing for easy input by selecting an option.

[0109] Furthermore, as shown in "9. Register (Recreational Fishing Boat Business Manager)" in Figure 34, an input screen (selection screen) for the recreational fishing boat business manager for the departure schedule to be registered is displayed. Here, one or more recreational fishing boat business managers belonging to the recreational fishing boat operator who has logged in are displayed for selection.

[0110] The display of options may be based on, for example, other departure schedules already set for the selected recreational fishing boat. While multiple options are displayed based on multiple departure schedules already set, one of the options (for example, data set in the most recent departure schedule) may be displayed in an editable format in the input field as a candidate for input data. The order in which each data item in the departure schedule is entered is not particularly limited.

[0111] Finally, the "10. Register (Confirm registration details)" screen in Figure 34 will be displayed. This screen displays a list of the entered data. When the "Save" button is selected, the entered data will be saved in the database as a departure schedule (or departure schedule data included in the boarding list), and the "11. Register (Registration Complete)" screen in Figure 34 will be displayed.

[0112] "12. Roster details" in Figure 35 shows a screen that displays the registered departure schedule (and passenger list). The screen in Figure 35 is displayed, for example, by selecting the "Check Roster & Detailed Information" button on the screen in Figure 18 that is displayed after a recreational fishing boat operator logs in. The "12. Roster details" screen in Figure 35 displays various data included in the departure schedule in an editable format. It also displays the completed passenger list. Therefore, recreational fishing boat operators and the like can easily check the passengers on board.

[0113] When you select (tap) the name of a passenger (angler) on the displayed passenger list, the "Edit user information entered on the list" screen will be displayed, as shown in Figure 35. On this screen, the recreational fishing boat operator etc. can edit the information entered by the passenger (angler).

[0114] On the "12. Register Details" screen in Figure 35, a photograph (image) of a handwritten register, such as a paper register, can be uploaded to the system 100. The uploaded photograph is stored in the system 100 in association with the data of the departure schedule or the passenger register, as part of the data constituting the passenger register corresponding to the departure schedule. Therefore, a handwritten passenger register, such as a paper register, can also be used, which is advantageous as it can accommodate passengers (anglers) who prefer to write on paper.

[0115] Figure 36 shows the display screen for the registered "14. All Roster List" and "15. Monthly Roster List." Also, Figure 37 shows the registered "16. Roster Download / Email Sending Screen" and "17. Roster Printing Screen." Here, the boarding roster is converted to PDF, and the PDF file is downloaded, attached to an email, and printed.

[0116] "18. QR Code for the Boat List" in Figure 38 shows the QR Code (registered trademark) that anglers (passengers) use to access the boat list input screen, and is the same as the "QR Code" shown in "2. Home" in Figure 31.

[0117] "19. Basic Information Confirmation" in Figure 38 shows the information set for the recreational fishing boat operator who has logged in. As shown in Figure 38, the recreational fishing boat operator has the name of the boat they own (recreational fishing boat), the recreational fishing boat business manager, etc. set (see also Figure 40).

[0118] "17. Hamburger Menu (Menu Screen)" in Figure 39 shows the hamburger menu (the three-line menu screen display button; the "three lines" in the upper right corner of Figures 31 and 32) after logging in. If you select "All Rosters" on this menu screen, the "14. All Roster List" screen in Figure 36 will be displayed. If you select "Download / Email All Rosters" on this menu screen, the "16. Download / Email Roster" screen in Figure 37 will be displayed. If you select "Print Roster" on this menu screen, the "17. Print Roster" screen in Figure 37 will be displayed. If you select "Passenger Roster QR Code" on this menu screen, the "18. Passenger Roster QR Code" screen in Figure 38 will be displayed. If you select "Confirm Basic Information" on this menu screen, the "19. Confirm Basic Information" screen in Figure 38 will be displayed.

[0119] As described above, the system 100 according to the embodiment is configured to store identification information associated with recreational fishing vessel business managers and recreational fishing vessels. The system 100 accepts registration of departure schedules from recreational fishing vessel operators who use recreational fishing vessels to depart, and executes steps that record the execution, completion status, and reports of the responsibilities required for the departure. Furthermore, since responsibilities are strict and stipulated by law, and failure to properly fulfill responsibilities carries penalties including fines and imprisonment, the system 100 may incorporate restrictions to ensure proper execution of responsibilities. Furthermore, the system 100 can retain data that serves as evidence. For example, (A) the execution of responsibilities is limited to accounts issued to each manager. (B) There is a restriction that pre-departure inspections can only be performed before departure time. (C) Information about the executed terminal, the execution date and time, etc. are automatically saved and cannot be tampered with. Furthermore, since the records of the performance of duties may be used as evidence in the case of an accident, in criminal cases, or for compensation for damages, System 100 can easily share this data with the Japan Coast Guard, police, Fisheries Agency, Ministry of Land, Infrastructure, Transport and Tourism, prefectures, etc. Furthermore, recreational fishing boat operators, recreational fishing boat business managers, captains, and crew members can all hold multiple positions, and System 100 can handle cases where the same person holds these positions.

[0120] Now, Figure 40 shows the relationship between recreational fishing boat operators, recreational fishing vessels, and recreational fishing boat business managers, as already explained. Multiple recreational fishing boat operators who use system 100 are registered in recreational fishing boat operator database 31. As an example, Figure 40 shows recreational fishing boat operator X, whose recreational fishing boat operator ID is 001, and recreational fishing boat operator Y, whose recreational fishing boat operator ID is 002. Each of recreational fishing boat operators X and Y is affiliated with one or more recreational fishing boat hulls and one or more recreational fishing boat business managers, which are associated with each recreational fishing boat operator and registered in the database. System 100 is a system shared by multiple recreational fishing boat operators X and Y registered in system 100, and each recreational fishing boat operator (or their associates) logs in to system 100 with their account to use system 100.

[0121] For example, recreational fishing boat operator X is associated with three recreational fishing hulls A, B, and C. Furthermore, recreational fishing boat operator X is associated with two recreational fishing boat business managers A1 and B1. Furthermore, recreational fishing boat operator Y is associated with three recreational fishing hulls E, F, and G. Furthermore, recreational fishing boat operator Y is associated with two recreational fishing boat business managers E1 and F1.

[0122] Each recreational fishing boat operator X, Y may be associated with data other than the recreational fishing boat hull and recreational fishing boat business manager (for example, data on related parties). For example, in Figure 41, recreational fishing boat operator X is associated with captains A1 and A3, crew members (employees) A1, A2, and A4, and liaison officer A5. In Figure 41, A1 serves as the recreational fishing boat business manager, captain, and crew member (employee). A2 serves as the recreational fishing boat business manager and crew member (employee). A1 to A5 are people who belong to any of the recreational fishing boat operators.

[0123] Here, the "liaison officer" shown in Figure 41 is a person on land who can contact the Japan Coast Guard or other organizations in the event of a maritime accident, and is designated for each recreational fishing boat operator. The liaison officer is authorized to log in to system 100, refer to the corresponding recreational fishing boat operator's ship roster, pre-departure inspection data, and crew record data, and transmit that data to the Japan Coast Guard or other organizations. For example, in the event of a maritime accident, the liaison officer can log in to system 100, display the screens shown in Figures 36 and 37, download, email, or print the ship roster, and then submit the ship roster to the Japan Coast Guard or other organizations. Similarly, the liaison officer can download, email, or print the pre-departure inspection data and crew record data, and then submit that data to the Japan Coast Guard or other organizations.

[0124] Figure 42 shows an example of the procedure for registering a departure schedule by a recreational fishing boat operator or the like. When registering a departure schedule, the system 100 first reads out from the database of the system 100 the recreational fishing boats associated with the recreational fishing boat operator who has logged in to the system 100, and displays one or more of the read recreational fishing boats as options (step S421; see "3. Today's Roster List (Recreational Fishing Boat Selection Screen)" in Figure 32). The system 100 then accepts the selection of a recreational fishing boat from a user such as a recreational fishing boat operator (step S422).

[0125] The system 100 also accepts input of the catch (step S423; see "5. Register (catch)" in FIG. 33).

[0126] The system 100 also accepts input of departure time and return time (step S424; see "6. Register (departure time)" and "7. Register (return time)" in FIG. 33).

[0127] The system 100 also accepts input of fishing grounds (step S425, see "8 Register (fishing grounds)" in FIG. 33).

[0128] Furthermore, system 100 reads out from the database of system 100 the recreational fishing boat business manager associated with the recreational fishing boat operator who has logged in to system 100, and displays one or more of the read out recreational fishing boat business managers as options (step S426; see "9. Register (Recreational Fishing Boat Business Manager)" in Figure 34). System 100 then accepts the selection of a recreational fishing boat business manager from a user such as a recreational fishing boat operator (step S427).

[0129] The input data is registered in the departure schedule database. The order in which the data is input in steps S421 to S427 is not particularly limited, and any order may be used.

[0130] Figure 43 shows an example of a display screen for registered departure schedules. The basic functions of the screen in Figure 43 are the same as those of the screen in Figure 18. On the screen in Figure 43, a day can be selected, and the departure schedule for the selected day is displayed. Each departure schedule includes a button for viewing the departure schedule (passenger list) ("View departure schedule (passenger list)" button), a button for entering pre-departure inspection data ("Perform pre-departure inspection" button), and a button for entering crew record data ("Enter crew record" button).

[0131] Figure 44 shows the relationship between registered departure schedules and recreational fishing boat operators. As shown in Figure 43, in the departure schedule database 33, each departure schedule is registered in association with the recreational fishing boat operator who created the departure schedule (including the recreational fishing boat operator to which the relevant party belongs, if the departure schedule was created by a related party). For example, in Figure 44, recreational fishing boat operator X stores three associated departure schedules with departure schedule identifiers X001, X002, and X003. Recreational fishing boat operator Y stores three associated departure schedules with departure schedule identifiers Y001, Y002, and Y003. When recreational fishing boat operator X logs into the system, he can refer to and edit the departure schedules with departure schedule identifiers X001, X002, and X003 and can enter pre-departure inspection and crew record data corresponding to those departure schedules. He can also refer to and edit the crew rosters corresponding to those departure schedules. Recreational fishing boat operator Y can also operate the departure schedule associated with recreational fishing boat operator Y in the same way.

[0132] Figure 45 shows the relationship between each departure schedule and the data on the crew list, pre-departure inspection, crew record, and catch volume. As shown in Figure 45, the data on the crew list, pre-departure inspection, crew record, and catch volume are associated with the departure schedule. In this system 100, the data on the crew list, pre-departure inspection, crew record, and catch volume are created for a pre-registered departure schedule, so the relationship between the departure schedule and each data is clear, making it easy to check each data in the event of a maritime accident, etc. Furthermore, data included in the pre-registered departure schedule (e.g., data on the recreational fishing boat, departure and return dates and times, and the weekly fishing boat operations manager) is automatically reflected in the data on the crew list, pre-departure inspection, crew record, and catch volume as needed, eliminating the need to enter the same departure schedule each time the data on the crew list, pre-departure inspection, crew record, and catch volume are created, simplifying the process. Furthermore, when creating the data for the crew manifest, pre-departure inspection, crew record, and catch volume, it may be possible to modify the data included in the departure schedule (or it may not be possible to modify it).

[0133] In system 100, multiple departure schedules for the same recreational fishing boat operator are associated via that recreational fishing boat operator, so it is easy to refer to other departure schedules for the same recreational fishing boat operator. For example, when a recreational fishing boat operator sets a new departure schedule, system 100 references the data of the already set departure schedule for that recreational fishing boat operator and displays it as an input data option (input candidate) for the new departure schedule, thereby omitting input or reducing the effort required for input.

[0134] 46 and 47 show the relationship between the departure schedule and the passenger list data. As shown in FIG. 46, the passenger list data can be associated with the departure schedule. Recreational fishing boat operators can refer to the departure schedule and the corresponding passenger list on the passenger list screen for recreational fishing boat operators (see, for example, FIG. 35 and FIG. 47). The passenger list screen for recreational fishing boat operators automatically reflects and displays the data included in the departure schedule. Furthermore, the passenger list data is automatically reflected and registered with the data included in the departure schedule. On the screen of FIG. 47, recreational fishing boat operators can edit the departure schedule, enter the passenger list (see FIG. 48), and upload handwritten passenger list photos (similar to the screen of FIG. 35). Note that if data included in the departure schedule is edited on the passenger list screen, the edits are also reflected in the data registered in the departure schedule database. Therefore, the edited departure schedule is displayed on the screen for entering data for the pre-departure inspection or crew record.

[0135] When a photograph of a handwritten name list is uploaded, the system 100 may recognize the information contained in the photograph of the handwritten name list through character recognition processing, and integrate the recognized information (name list information) with the information (name list information) entered on the screen of Figure 46 described below, and store the result in the database as boarding list data.

[0136] As shown in Figure 46, anglers (passengers) can register their own information as data in the passenger list (filling out the passenger list). Figure 49 shows an example of the passenger list registration screen. The angler accesses the screen of Figure 49 from the terminal 107, and from the screen of Figure 49 displays the screen of Figure 50, where they enter their own information. If the angler is a registered user and is registered in the user (angler) database 38 (see Figure 10), when the angler logs in as a registered user, the information registered in the database 38 will automatically be reflected on the screen of Figure 50 by the system 100.

[0137] Figure 51 shows the relationship between the departure schedule and pre-departure inspection (pre-departure inspection) data. As shown in Figure 51, the recreational fishing vessel operations manager can enter data for each pre-departure inspection item on the pre-departure inspection screen (see, for example, Figures 19, 20, and 52), which displays the data included in the departure schedule. As shown in Figure 52, on the pre-departure inspection screen, the recreational fishing vessel operations manager is automatically reflected and displayed as the person set in the departure schedule, but it is also possible to change the automatically reflected recreational fishing vessel operations manager to another manager associated with the same recreational fishing vessel operator. The recreational fishing vessel operations manager who records the pre-departure inspection must be the person who actually recorded the pre-departure inspection. Therefore, if a person other than the planned recreational fishing vessel operations manager performs the inspection (inspection) as the recreational fishing vessel operations manager, the actual recreational fishing vessel operations manager can be changed to create an appropriate pre-departure inspection record.

[0138] In other words, if the recreational fishing boat business manager set in the departure schedule actually inspects the boat as the recreational fishing boat business manager for that departure schedule, the recreational fishing boat business manager set in the departure schedule will also be registered as the recreational fishing boat business manager in the pre-departure inspection data (automatically reflected data is registered). On the other hand, if a person other than the recreational fishing boat business manager set in the departure schedule inspects the boat as the recreational fishing boat business manager, the recreational fishing boat business manager automatically reflected in the pre-departure inspection data will be changed to the recreational fishing boat business manager who actually inspected the boat and registered (automatically reflected data is changed and registered).

[0139] The system 100 may also accept the upload of a photograph of the recreational fishing vessel as data for the pre-departure inspection. The system 100 may store the uploaded photograph as part of the data for the pre-departure inspection.

[0140] Figure 53 shows the relationship between the departure schedule and crew record data. As shown in Figure 54, the recreational fishing boat operations manager can enter data for each item of the crew record on the crew record screen (see, for example, Figures 25 to 27, 54, and 55), which displays the data included in the departure schedule. As shown in Figure 54, on the crew record screen, the recreational fishing boat operations manager is automatically reflected and displayed as the person set in the departure schedule, but it is also possible to change the automatically reflected recreational fishing boat operations manager to another manager associated with the same recreational fishing boat operator. The recreational fishing boat operations manager who records the crew record must be the person who actually recorded the crew record. Therefore, if a person other than the planned recreational fishing boat operations manager boards the vessel as the recreational fishing boat operations manager, the actual recreational fishing boat operations manager can be changed to create an appropriate crew record.

[0141] In other words, if the recreational fishing boat operations manager set in the departure schedule actually boards the vessel as the recreational fishing boat operations manager for that departure schedule, the recreational fishing boat operations manager set in the departure schedule will also be registered as the recreational fishing boat operations manager in the crew record data (automatically reflected data is registered). On the other hand, if a person other than the recreational fishing boat operations manager set in the departure schedule boards the vessel as the recreational fishing boat operations manager, the recreational fishing boat operations manager automatically reflected in the crew record data will be changed to the recreational fishing boat operations manager who actually boarded the vessel and registered (automatically reflected data is changed and registered).

[0142] In addition, the "start time" and "end time" items in the crew record are automatically reflected and displayed based on the times set in the departure schedule. Therefore, if the departure and return are completed according to the departure schedule, there is no need to change the automatically reflected times, which is convenient. Furthermore, these times can be changed to the actual start and end times, so the actual times can be recorded.

[0143] It is also preferable to record the captain and employees in the crew record, as shown in Figure 54. Here, captains and / or employees belonging to the same recreational fishing boat operator are read from the database and displayed for selection, making it easy to input the captain and / or employees.

[0144] It is also preferable to record weather and sea conditions in the crew record, as shown in Figure 54. Weather and sea condition information may be manually entered by the recreational fishing boat operations manager, but the system 100 may also access a weather and sea condition database, obtain the necessary weather and sea condition data based on the date and time data and location (fishing ground) data set in the corresponding departure schedule, and automatically reflect the data on the screen in Figure 54.

[0145] Furthermore, as shown in Figure 55, it is preferable to record the fishing grounds and / or the main aquatic animals and plants caught in the crew record. Information on the fishing grounds and / or the main aquatic animals and plants caught is automatically reflected in the "fishing grounds" and / or "fishing target" data set in the corresponding departure schedule. Therefore, if not necessary, the recreational fishing boat operations manager can use the automatically reflected data as is, making input easier. Furthermore, the automatically reflected data may be changed.

[0146] In addition, in system 100, the data associated with each recreational fishing boat operator, such as departure schedules, boat rosters, pre-departure inspection data, and crew records, may be encrypted and stored in part or in whole so that only each recreational fishing boat operator can view them. In this case, even administrators of system 100 cannot access the data of each recreational fishing boat operator, so the data of each individual recreational fishing boat operator is protected. Furthermore, each recreational fishing boat operator (including the liaison officer and recreational fishing boat business manager) can share each data with external parties such as relevant government agencies under their control.

[0147] 56 to 58 are diagrams that supplement the explanation of the screen for registering a new departure schedule (the explanation of FIGS. 32 to 34).

[0148] On the home screen shown in Figure 56(A) (for example, the screen when logging in with the account of a recreational fishing boat operator X), if the logged-in user selects a date and then selects the "Add schedule" button, the screen shown in Figure 56(B) will be displayed.

[0149] On the screen of Figure 56(B), one or more recreational fishing boats (recreational fishing boats owned by recreational fishing boat company X: Wamaru and Wamaru II) associated with the logged-in user (recreational fishing boat company X) are displayed as selectable options. The user selects one of the displayed recreational fishing boats (for example, Wamaru) by clicking or tapping on it. The screen of Figure 57 is then displayed.

[0150] On the screen of Figure 57, data items other than "recreational fishing boat" are entered as data for the departure schedule. However, for each data item, data associated with the account of recreational fishing boat operator X or data included in other set departure schedules for recreational fishing boat operator X are displayed as options.

[0151] For example, the option display section for recreational fishing boat business managers ("Business Manager" in the figure) displays one or more recreational fishing boat business managers associated with recreational fishing boat company X (i.e., recreational fishing boat business managers belonging to recreational fishing boat company X). The user can select the recreational fishing boat business manager to be set for this departure schedule by clicking or tapping on one of the recreational fishing boat business managers displayed in the option display section.

[0152] The "fishing target" input section allows the input of the "fishing target" to be set for this departure schedule. The input may be text input, or the selection of a "fishing target" displayed in the "fishing target" option display section. The selected "fishing target" is reflected in the input section. The "fishing target" option display section may display one or more "fishing targets" included in other set departure schedules for recreational fishing boat operator X. The "fishing target" option display section may also display one or more "fishing targets" included in the departure schedule for the "recreational fishing boat" selected on the screen of Figure 56(B) from other set departure schedules for recreational fishing boat operator X. This is because the "fishing target" is often the same as a past "fishing target" for the same recreational fishing boat. The same applies to the "fishing grounds" in Figure 57.

[0153] Furthermore, the "fishing target" option display section may display one or more "fishing targets" included in the departure schedule for the "recreational fishing boat business manager" selected on the screen of Figure 57, among other set departure schedules for recreational fishing boat operator X. Furthermore, the "fishing target" option display section may display one or more "fishing targets" included in the departure schedule for the "recreational fishing boat" selected on the screen of Figure 56(B) and the "recreational fishing boat business manager" selected on the screen of Figure 57, among other set departure schedules for recreational fishing boat operator X. The same applies to the "fishing grounds" in Figure 57.

[0154] Furthermore, the input section for "fishing target" automatically reflects and displays one of one or more "fishing targets" (e.g., possible "fishing targets" to choose from) included in other set sailing schedules for recreational fishing boat operator X. For example, among other set sailing schedules for recreational fishing boat operator X, the "fishing target" included in the most recent sailing schedule for the "recreational fishing boat" selected on the screen of FIG. 56(B) is displayed. If the "fishing target" automatically reflected in the input section is also applicable to this sailing schedule, there is no need to input text into the input section, which is convenient. The same is true for the "fishing grounds" in FIG. 57.

[0155] The "departure time" and "return time" in Figure 57 and other data items as needed can also be automatically reflected (automatically displayed) in the same way as "fish to be caught" and "fishing grounds."

[0156] Therefore, if the departure schedule to be added is the same as the most recent departure schedule, when the screen of Figure 57 is displayed from Figure 56(B), the system 100 will display appropriate data as candidates for all data items. Therefore, in the case of the same departure schedule, the user can close the screen of Figure 57 (select "Next" in Figure 57) without performing operations such as inputting or selecting data for each data item in Figure 57.

[0157] When "Next" in FIG. 57 is selected, the confirmation screen in FIG. 58 is displayed, and when "Save" is selected, a departure schedule with the content shown in FIG. 58 is newly registered in the system 100.

[0158] 59 to 62 are supplementary figures for explaining the screens for inputting data for the pre-departure inspection (particularly checking for alcohol intoxication, etc.) (the explanation for FIGS. 19 to 22).

[0159] As shown in Figure 59, the input screen (input form) for entering data for the pre-departure inspection automatically reflects data, including the recreational fishing vessel business manager, from the departure schedule corresponding to that pre-departure inspection. In Figure 59, "Hirashima Takashi" is displayed as the recreational fishing vessel business manager automatically reflected from the departure schedule for that departure. Furthermore, the automatically reflected recreational fishing vessel business manager can be changed. System 100 displays one or more recreational fishing vessel business managers (here, "Hirashima Takashi" and "Yamada Taro") belonging to the logged-in recreational fishing vessel company X as options. The user can change the recreational fishing vessel business manager by selecting an option. The changed recreational fishing vessel business manager is registered as the recreational fishing vessel business manager corresponding to this pre-departure inspection; if not changed, the recreational fishing vessel business manager set in the departure schedule is registered as the recreational fishing vessel business manager corresponding to this pre-departure inspection.

[0160] As shown in Figure 60, the pre-departure inspection includes an inspection item for "checking whether or not the person is under the influence of alcohol and checking their health." The screen in Figure 60 is displayed following the screen in Figure 59. In the screen in Figure 59, it is assumed that "Hirashima Takashi" has been registered as the recreational fishing boat operations manager. "Checking whether or not the person is under the influence of alcohol and checking their health" must be carried out at least for the recreational fishing boat operations manager who will actually be on board. Therefore, in Figure 60, the recreational fishing boat operations manager registered in Figure 59 ("Hirashima Takashi") is displayed as the person to be inspected for "checking whether or not the person is under the influence of alcohol and checking their health."

[0161] More specifically, on the screen of Figure 60, one or more recreational fishing boat business managers associated with the logged-in recreational fishing boat operator X (here, "Hirashima Takashi" and "Yamada Taro") are displayed as options for the person to be inspected. Of the displayed "Hirashima Takashi" and "Yamada Taro," "Hirashima Takashi" registered on the screen of Figure 59 is automatically selected by the system 100. Therefore, the user does not need to perform any operation to select "Hirashima Takashi" as the person to be inspected. Note that the person to be inspected can also be selected by user operation. For example, on the screen of Figure 60, the user may perform an operation to change the person to be inspected to "Yamada Taro."

[0162] It is preferable that the "check for alcoholism and health" be conducted on other people actually on board (for example, the captain or other employees) in addition to the recreational fishing boat operations manager. In the system 100, if there are multiple people actually on board, each person can be entered as a person to be tested.

[0163] Figure 61 shows a screen for entering the second person to be inspected. In the input field for the second person to be inspected, one or more recreational fishing boat business managers (here, "Hirashima Takashi" and "Yamada Taro") associated with the logged-in recreational fishing boat operator X are displayed as options, along with the first "person to be inspected" (here, "Hirashima Takashi") (here, "Yamada Taro"). In addition, since it is possible that someone not associated with the logged-in recreational fishing boat operator X may be on board, it is also possible to enter an "other" person.

[0164] Figure 62 shows a screen for inputting the third test subject. The third person can be input as "Other."

[0165] The present invention is not limited to the above-described embodiment, and various modifications are possible.

[0166] The present disclosure also includes the following aspects.

[0167] (A) One aspect of the present disclosure is a computer-implemented method, a system configured to execute the method, or a computer program for causing a computer to execute the method. The method may include displaying an input screen on a terminal that allows a recreational fishing vessel operations manager to input at least one of pre-departure inspection data and crew record data, and registering the data entered on the input screen in a database. Displaying such an input screen allows the pre-departure inspection data or crew record data to be entered conveniently on the terminal.

[0168] (B) One aspect of the present disclosure is a computer-implemented method, a system configured to execute the method, or a computer program for causing a computer to execute the method. In the method, a recreational fishing boat operator's recreational fishing boat business manager is registered in the system in association with the recreational fishing boat operator, and the recreational fishing boat business manager registered in association with the recreational fishing boat operator may be displayed on a screen displayed on a terminal for inputting data on the recreational fishing boat operator's pre-departure inspection (pre-departure inspection) and / or crew record for the recreational fishing boat's departure. In this case, the recreational fishing boat business manager pre-associated with the recreational fishing boat operator is displayed on the screen for inputting data on the recreational fishing boat operator's pre-departure inspection (pre-departure inspection) and / or crew record, thereby eliminating or simplifying the need to input the name of the recreational fishing boat business manager. When displaying the recreational fishing boat business manager, it is preferable that one or more registered recreational fishing boat business managers be displayed as selectable.

[0169] (C) Multiple recreational fishing boat operators can be registered in the system. One or more recreational fishing boat business managers can be registered in association with each recreational fishing boat operator. Each recreational fishing boat operator has an account for logging in to the system. Each recreational fishing boat operator (or its affiliates) can log in to the system and set a departure schedule for themselves (their company). In this way, the system can be shared by multiple recreational fishing boat operators. The system can store the departure schedules of each of the multiple recreational fishing boat operators.

[0170] (D) Captains belonging to recreational fishing boat operators can be registered in the system in association with the recreational fishing boat operator. Captains registered in association with the recreational fishing boat operator can be displayed on the screen displayed on the terminal for inputting crew record data. In this case, inputting the captain's name, etc. is unnecessary or simplified. When displaying the captain, it is preferable that one or more registered captains be displayed so that they can be selected.

[0171] (E) The recreational fishing vessel business manager or the captain may be registered in the system in association with an account used to log in to the system (e.g., a recreational fishing vessel operator's account). In this case, if the user logs in with that account, the recreational fishing vessel business manager or the captain associated with the recreational fishing vessel operator can be identified from that account. For example, in any of (A) to (D) above, the recreational fishing vessel business manager or the captain can be identified by the account used to log in. [Explanation of symbols]

[0172] 10: Server 15: Network 20: Processor 21: Departure schedule creation module 22: Pre-departure inspection management module 23: Crew record management module 24: Harvest volume management module 25: Related government agency connection module 26: Shipboard manifest entry module 30: Storage device 31A: Recreational Fishing Boat Operator Database 31B: Recreational Fishing Vessel Database 32: Recreational Fishing Boat Business Manager Database 33: Departure schedule database 34: Pre-departure inspection database (record database) 35: Crew Record Database (Record Database) 36: Catching volume database (record database) 37: Database of relevant government agencies 38: User database 39: Passenger manifest database 40: Input device 50: Output device 100: System 101: Terminal 102: Terminal 105: Terminal 107: Terminal 200: Recording System 300: Data linkage system for related government agencies 400: Shipboard manifest system

Claims

1. 1. A computer-implemented method performed by a computer, comprising: When an input of a fishing boat departure schedule is received, the departure schedule is registered in a departure schedule database; An input screen for the recreational fishing boat operations manager to input data about the departure schedule registered in the departure schedule database is provided to the terminal of the recreational fishing boat operations manager so that the input screen can be displayed on the terminal of the recreational fishing boat operations manager; registering the data entered on the input screen in a record database; Prepare for this. The input screen is configured to allow the recreational fishing boat operations manager to input at least one of the following data as the data to be input by the recreational fishing boat operations manager: data on pre-departure inspection corresponding to the departure schedule; data on crew records corresponding to the departure schedule; and data on catch volume corresponding to the departure schedule. Computer-implemented methods.

2. The method further comprises displaying a schedule display screen showing one or more of the departure schedules registered in the departure schedule database on the terminal of the recreational fishing boat operations manager, The input screen is a screen for the recreational fishing boat operations manager to input data regarding the departure schedule selected on the schedule display screen. The computer-implemented method of claim 1 .

3. The timing of inputting the data is restricted based on the departure time indicated by the departure schedule, The data can be input at an input timing outside the limit. The computer-implemented method of claim 1 .

4. The data can only be entered by users who have been registered in advance as recreational fishing boat business managers. The computer-implemented method of claim 1 .

5. The recreational fishing boat operations manager is associated with the departure schedule, Only the recreational fishing boat business manager user associated with the departure schedule can input the data corresponding to the departure schedule. The computer-implemented method of claim 1 .

6. The computer system that executes the computer-implemented method of claim 1 can set the departure schedule for the recreational fishing boat of the recreational fishing boat operator by logging in with an account of the recreational fishing boat operator or a related person for logging in to the system. The computer-implemented method of claim 1 .

7. A computer system that executes the computer-implemented method according to claim 1 can be logged in with an account for logging in to the system, The input screen displays one or more pieces of data associated with the logged-in account. The computer-implemented method of claim 1 .

8. The data associated with the logged-in account includes the name of the recreational fishing vessel operations manager; The computer-implemented method of claim 7.

9. The recreational fishing boat operations manager is associated with the departure schedule, The input screen for the data corresponding to the departure schedule displays the recreational fishing boat operations manager associated with the departure schedule. The computer-implemented method of claim 1 .

10. registering the data in the record database includes registering the data entered on the input screen and the data included in the departure schedule in the record database. The computer-implemented method of claim 1 .

11. The passenger data regarding the departure schedule is received from the passenger's terminal and registered in a passenger list database. Further provided that: The computer-implemented method of claim 1 .

12. When an input of a fishing boat departure schedule is received, the departure schedule is registered in a departure schedule database; An input screen for the recreational fishing boat operations manager to input data about the departure schedule registered in the departure schedule database is provided to the terminal of the recreational fishing boat operations manager so that the input screen can be displayed on the terminal of the recreational fishing boat operations manager; registering the data entered on the input screen in a record database; configured to perform operations comprising: The input screen is configured to allow the recreational fishing boat operations manager to input at least one of the following data as the data to be input by the recreational fishing boat operations manager: data on pre-departure inspection corresponding to the departure schedule; data on crew records corresponding to the departure schedule; and data on catch volume corresponding to the departure schedule. system.

13. When an input of a fishing boat departure schedule is received, the departure schedule is registered in a departure schedule database; An input screen for the recreational fishing boat operations manager to input data about the departure schedule registered in the departure schedule database is provided to the terminal of the recreational fishing boat operations manager so that the input screen can be displayed on the terminal of the recreational fishing boat operations manager; registering the data entered on the input screen in a record database; A computer program that causes a computer to perform an operation comprising: The input screen is configured to allow the recreational fishing boat operations manager to input, as the data to be input by the recreational fishing boat operations manager, at least one of data on a pre-departure inspection corresponding to the departure schedule, data on a crew record corresponding to the departure schedule, and data on a catch amount corresponding to the departure schedule. Computer program.

Images