Growth management system, and growth management method

Abstract

To carry out smooth transfer to others of a technique relating to growth of a marine product.SOLUTION: A growth management system according to the present invention has a user terminal and a growth management apparatus. The user terminal comprises an input reception unit for accepting an input of work information indicating a work content of a process unit during a unit growth period from commencement of growth of a growth target to cropping, and the growth management apparatus includes an information registration unit for acquiring the work information whose input has been accepted by the input reception unit to store the acquired work information in a storage unit.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a cultivation management system and a cultivation management method for cultivating marine products. [Background technology]

[0002] A technology is known that acquires field information corresponding to the current location determined by a field management terminal device from field information recorded in such a way that crop information, pesticide use information, etc. are associated with positions within the field (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-069450 Summary of the Invention [Problem to be solved by the invention]

[0004] For example, the cultivation (aquaculture) of marine products such as mozuku seaweed relies on the experience, intuition, and know-how of each producer, making it difficult to share techniques for improving the quality of mozuku seaweed and increasing production efficiency.

[0005] The present invention aims to facilitate the smooth transfer of techniques related to the cultivation of marine products to others. [Means for solving the problem]

[0006] One aspect of the present invention that solves the above-mentioned problems is a cultivation management system that includes a user terminal and a cultivation management device, and an input acceptance unit in the user terminal that accepts input of work information indicating the work content of each process unit in a unit cultivation period from the start of cultivation of the cultivation object to harvest, and an information registration unit in the cultivation management device that acquires the work information accepted as input by the input acceptance unit and stores the acquired work information in a memory unit.

[0007] One aspect of the present invention is a cultivation management method in a cultivation management system that includes a user terminal and a cultivation management device, and includes an input acceptance step in the user terminal, in which an input acceptance unit accepts input of work information that indicates the work content of each process unit in a unit cultivation period from the start of cultivation of the cultivation object to harvest, and an information registration step in the cultivation management device, in which an information registration unit acquires the work information that has been accepted by the input acceptance step and stores the acquired work information in a memory unit. [Effects of the Invention]

[0008] According to the present invention, it is possible to obtain an effect that techniques relating to the cultivation of marine products can be smoothly transferred to others. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of the overall configuration of an aquaculture management system in a first embodiment. [Figure 2] 3A and 3B are diagrams illustrating an example of an initial screen and a calendar screen according to the first embodiment. [Figure 3] 10A and 10B are diagrams showing an example of a work information registration screen and a calendar screen after work information registration in the first embodiment. [Figure 4] 3A and 3B are diagrams showing an example of a location information list screen and a location information registration screen in the first embodiment. [Figure 5] FIG. 4 is a diagram showing an example of a work information registration screen in the first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of the functional configuration of a user terminal according to the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the functional configuration of the aquaculture management device according to the first embodiment. [Figure 8] FIG. 3 is a diagram showing an example of information stored in the aquaculture management device in the first embodiment. [Figure 9]FIG. 4 is a sequence diagram showing an example of a processing procedure executed by a user terminal and an aquaculture management device in relation to the registration of work information in the first embodiment. [Figure 10] FIG. 4 is a sequence diagram showing an example of a processing procedure executed by a user terminal and an aquaculture management device in relation to the registration of location information in the first embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a work information registration screen in the second embodiment. [Figure 12] 10A to 10C are diagrams illustrating an example of a calendar screen, a location status screen, and a task list screen according to the second embodiment. [Figure 13] 10A to 10C are diagrams showing examples of a harvest record screen, a screen count history screen, and a process unit information screen in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] First Embodiment [Overall configuration example of aquaculture management system] 1 shows an example of the overall configuration of an aquaculture management system (an example of a cultivation management system) according to this embodiment. The aquaculture management system according to this embodiment manages and supports the cultivation (an example of cultivation) of edible seaweed (hereinafter referred to as "mozuku") that is distributed under the name "mozuku" or "mozuku" or the like. In the figure, users U are producers engaged in mozuku cultivation and perform work related to mozuku cultivation. Each user U possesses a user terminal 100. An application corresponding to cultivation management (a cultivation management application) is operable on the user terminal 100.

[0011] The user terminal 100 may be, for example, a smartphone. Alternatively, the user terminal 100 may be a tablet terminal, a personal computer, etc. In the following description, an example will be given in which the user terminal 100 is a smartphone. A user terminal 100 on which the aquaculture management application runs is communicably connected to the aquaculture management device 200 via a network.

[0012] The aquaculture management device 200 executes various processes corresponding to aquaculture management in cooperation with an aquaculture management application running on the user terminal 100. The aquaculture management device 200 may be configured as a server provided on a network, or may be configured as a cloud server.

[0013] [About the Mozuku cultivation process] Here, a series of steps in the cultivation of mozuku will be described. Mozuku cultivation is carried out, for example, in the following order: seedling collection, seeding, net transfer, netting, and harvesting. Seedling collection is the process of collecting natural mozuku seeds (spores) that grow naturally in the ocean. Seeding is the process of growing the mozuku seeds collected during the seedling collection process in a tank and attaching them to a net (seeding). Net transfer is the process of transferring the nets to which the mozuku seeds have been attached during the seeding process to a place in the ocean called a nursery or intermediate area where the waves are calm. The actual setting is the process of setting the net in the sea when the mozuku attached to the net that has been moved underwater by the net movement has grown to, for example, a few centimeters. Harvesting is the process of harvesting the mozuku that has grown on a permanently stretched net. After harvesting, the harvested mozuku is moved on to other processes such as processing.

[0014] For example, a producer as user U may carry out multiple unit cultivations in a multi-cropping manner, shifting the cultivation time by about one month during the period (unit cultivation period) during which cultivation (unit cultivation) is carried out through a series of processes from seedling collection to harvesting. By carrying out unit cultivation over multiple unit cultivation periods at different times in this way, it is possible to efficiently cultivate a large amount of mozuku using the same tanks and main areas.

[0015] [Regarding work and location information] The user U can input (register) work information indicating the work content of each process unit that the user has performed into the aquaculture management application running on the user terminal 100. The user U can also input (register) work information indicating the work content of each process unit that the user plans to perform in the future into the aquaculture management application running on the user terminal 100. Furthermore, the user U can input (register) information (location information) about the location where the mozuku seaweed is grown, for example, by operating an aquaculture management application running on the user terminal 100.

[0016] The aquaculture management device 200 stores the work information input to the user terminal 100 by operation of the user U. By storing the work information in this way, the work information input by the user U is registered. Furthermore, the aquaculture management device 200 stores the location information input to the user terminal 100 by the operation of the user U. By storing the location information in this manner, the location information input by the user U to the user terminal 100 is registered.

[0017] An example of an operation procedure that the user U performs on the aquaculture management application of the user terminal 100 in response to the registration of work information and location information will be described with reference to FIGS. 2(A) shows an example of an initial screen that is displayed first as an application screen on the display surface serving as a touch panel of the user terminal 100 when the aquaculture management application is launched. The initial screen includes a chat area AR1 and a registration transition button BT1. The chat area AR1 is an area used, for example, for a conversation between a chatbot and a user U in the form of a text chat. In the chat area AR1, for example, information notifying the user U about the growth of mozuku may be presented. Furthermore, the chat area AR1 may be used so that when the user U inputs a message to the chatbot asking a question about, for example, the weather, the chatbot will present a text answer to the question.

[0018] The registration transition button BT1 is a button that is operated to transition to an application screen where task information and location information can be registered. When the registration transition button BT1 is operated, a calendar screen including a calendar is displayed as the application screen.

[0019] 2(B) shows an example of a calendar screen, which includes a calendar area AR11, a registration button BT11, a calendar transition button BT12, and a location registration transition button BT13. The calendar area AR11 is an area where a calendar is displayed. The calendar area AR11 in the figure displays a monthly calendar, but may be configured to display a weekly calendar instead. The calendar area AR11 in the figure displays the current day in a highlighted background color different from the other days. The registration button BT11 is a button that is operated when transitioning to the registration of work information. The calendar transition button BT12 is a button that is operated to return the display to the calendar area AR11 when the area corresponding to the calendar area AR11 is displaying something other than a calendar. The location registration transition button BT13 is a button that is operated when transitioning to location information registration.

[0020] For example, when the user U completes work corresponding to a certain process, the user U is required to register work information indicating the details of the work. Therefore, the user U displays the calendar screen of FIG. 2(B) on his / her user terminal 100. The user U specifies the date to be registered on the calendar displayed on the calendar screen, and then operates the registration button BT11 arranged on the calendar screen. In response to the operation of the registration button BT11, the application screen of the aquaculture management application transitions to a work information registration screen.

[0021] Fig. 3(A) shows an example of a work information registration screen. The work information registration screen in the same figure has a date area AR15. The date area AR15 indicates the date to which the work information being registered corresponds. The date shown in the date area AR15 reflects the date specified on the calendar when the registration button BT11 on the calendar screen (Fig. 2(B)) is operated.

[0022] The work information registration screen also has a "work type" input area AR20. The "work type" input area AR20 is used to select a work type corresponding to each process of mozuku cultivation. In this case, the "work type" input area AR20 is configured to select a work type using a pull-down menu. The "work type" input area AR20 may allow selection of a work type corresponding to each process of seedling collection, seed planting, net movement, main setting, and harvesting. Furthermore, depending on the process, two or more work types may be provided as options.

[0023] The work type "Tank loading" selected in the "Work type" input area AR20 in the figure corresponds to the seeding process. In the seeding process, nets with mozuku attached during the seedling collection process are loaded into tanks filled with seawater installed on land. When the work type "Tank loading" is selected in the "Work type" input area AR20, the "Number of nets" input area AR21-1, the "How many times has this work been done?" input area AR21-2, and the "Work notes" input area AR21-3 are also displayed.

[0024] The "Number of Nets" input area AR21-1 is an area where a numerical value indicating the number of nets placed in the tank during the current seeding operation is input. In this case, the "Number of Nets" input area AR21-1 allows the numerical value to be input by, for example, entering text.

[0025] In the "What number of times is this operation?" input area AR21-2, a number indicating the number of times the insemination operation has been carried out this time (i.e., the number of unit farming it is) is input. In this case, the input area AR21-2 allows the user to select a number using a pull-down menu.

[0026] The "Work Memo" input area AR21-3 is an area where the user U can input in text any matters that he or she wishes to record as a memorandum about the seeding work that he or she has just performed.

[0027] The figure shows the state in which user U has selected "Tank loading" as the work type, and has entered information in the "Number of nets" input area AR21-1, the "How many times has this work been done?" input area AR21-2, and the "Work notes" input area AR21-3 based on the results of the work performed in the seeding process this time. In this state, if the user U operates the registration button BT22, the work information reflecting the input contents shown in the figure is registered in the aquaculture management device 200. Furthermore, if the user U wishes to clear the content entered on the work information registration screen in the same figure, the user U operates the back button BT21. In response to the operation of the back button BT21, the content entered on the work information registration screen in the same figure is cleared, and the display returns to the calendar screen in FIG. 2(B).

[0028] In addition, the work information registration screen may also allow the input of, for example, seawater temperature, sunshine hours, and seawater salinity.

[0029] When the registration button BT22 is operated in the state shown in Fig. 3(A), the screen returns to the calendar screen as shown in Fig. 3(B), and a work information list area AR12 including list items for the currently registered work information is additionally displayed on the calendar screen. The work information list area AR12 is an area where list items corresponding to each piece of work information that the user U has registered up to that point are displayed.

[0030] When an operation such as tapping is performed to select an item from the list items arranged in the work information list area AR12, a work information confirmation screen showing the content of the work information corresponding to the selected list item may be displayed. The user U can check the content registered as work information on the displayed work information confirmation screen. Furthermore, the content of the work information may be changed by operating the work information confirmation screen.

[0031] In addition, in the calendar area AR11 on the calendar screen after the task information has been registered, the badge BG placed in the area of the registration date reflects that the task information for which the current registration operation was performed has been registered. In the same figure, an example is shown in which the badge BG displays a number indicating the number of task information registered for the corresponding date.

[0032] When a tap operation is performed on the date portion with the badge BG in this way, for example, an aquaculture management information list screen (not shown) may be displayed in which each list item of the work information registered corresponding to the date on which the tap operation was performed is arranged. Then, when the user U performs an operation of selecting one of the list items arranged on the aquaculture management information list screen by tapping, a work information confirmation screen showing the content of the work information corresponding to the selected list item is displayed.

[0033] When a list item in the work information list area AR12 is selected, for example by tapping, a work information editing screen corresponding to the selected list item is displayed (not shown). The user U can change the content of the registered work information as needed by operating the work information editing screen.

[0034] Furthermore, when the user U registers location information, the user U operates the location registration transition button BT13 (FIG. 2(B)). In response to the operation of the location registration transition button BT13, the application screen of the aquaculture management application transitions to a location information list screen.

[0035] 4A shows an example of a location information list screen. In a location information list area AR35 of the location information list screen, a list of location information that has been registered up to now is arranged. When the user U wants to register new location information, the user U operates the location registration button BT30 arranged on the location information list screen. In response to the operation of the location registration button BT30, the application screen of the aquaculture management application transitions to a location information registration screen.

[0036] Figures 4(B) and 4(C) show examples of location information registration screens. The location information registration screen is configured such that the area shown in Figure 4(C) continues below the area shown in Figure 4(B), and the screen can be scrolled up and down. A map area AR30 is arranged on the location information registration screen. A map is displayed in the map area AR30. The user U can perform an operation to specify a point to be registered as location information on the map displayed in the map area AR30. Specifically, the point specified as location information corresponds to a location to which the net will be moved (a place in the sea where Mozuku is grown), etc. When the user U wants to change the scale of the map, he / she operates the map display button BT31. In response to the operation of the map display button BT31, the application screen of the aquaculture management application transitions to a map screen in which the map area AR30 is enlarged. An operation to specify a position is also possible on the map screen. A predetermined operation on the map screen can be performed to return to the location information registration screen.

[0037] The location information registration screen also includes a location name input area AR31-1, a water depth input area AR31-2, a bottom sediment input area AR31-3, a rock quantity input area AR31-4, aquatic plant quantity input area AR31-5, a fish quantity input area AR31-6, and a memo input area AR31-7.

[0038] The place name input area AR31-1 is an area where the user U performs an operation to input the name of a place using an arbitrary text string. The locations in the ocean used for Mozuku cultivation are often given names by the producers themselves for their own convenience. Therefore, by allowing text to be entered in the location name input area AR31-1, the user U can manage the locations with their own unique names.

[0039] The water depth input area AR31-2 is used to select the water depth of the corresponding location. For example, water depth can affect the growth of Mozuku seaweed in the sea after the net is moved. Therefore, the location information includes information on the water depth of the corresponding location. The bottom sediment input area AR31-3 is used to select the bottom sediment of the corresponding location. The bottom sediment options in the bottom sediment input area AR31-3 include, for example, "sand," "mud / clay," "stone," "rock," and "coral / shell." The quality of the seabed can affect the growth of Mozuku in the sea. Therefore, the location information includes information about the bottom sediment of the corresponding location.

[0040] The rock quantity input area AR31-4 is an area where the amount of rock in the corresponding location is input. In the figure, an example is shown in which the amount of rock is input by selecting from three options: "few," "medium," and "large." The growth of Mozuku in the sea can be affected by the amount of rock in the corresponding location.

[0041] The aquatic plant quantity input area AR31-5 is an area where the amount of aquatic plants in the corresponding location is input. The figure shows an example in which the amount of aquatic plants is input by selecting from three options: "few," "medium," and "many." The growth of Mozuku in the sea can be affected by the amount of aquatic plants in the corresponding location.

[0042] The fish quantity input area AR31-6 is an area where the operation to input the amount of fish in the corresponding location is performed. In the same figure, an example is shown in which the amount of fish is input by selecting from three options: "low," "medium," and "high." The growth of Mozuku in the sea can be affected by the amount of fish in the corresponding location.

[0043] The memo input area AR31-7 is an area where the user U can input any matter relating to the corresponding location in text.

[0044] The user U specifies a position corresponding to the location on the map as described above, inputs the location name, water depth, bottom quality, amount of rocks, amount of aquatic plants, amount of fish, memos, etc., and then operates the register button BT33. In response to the operation of the register button BT33, new location information including the information just input is registered. When the register button BT33 is operated, the application screen of the aquaculture management application returns to displaying the location information list screen (FIG. 4(A)). At this time, a list item of the newly registered location information is added to the location information list area AR35 of the displayed location information list screen.

[0045] When an operation such as tapping is performed to select one list item from the list items arranged in the location information list area AR35, a location information confirmation screen is displayed showing the content of the location information corresponding to the selected list item. The user U can check the content of the location information he or she has registered by looking at the location information confirmation screen. At this time, the location information confirmation screen may display the specified point on a map. Furthermore, the location information confirmation screen may be configured to allow an operation to change the content of the location information.

[0046] 5(A) and 5(B) show an example of a work information registration screen when "Network Move" is entered in the "Work Type" input area AR20 during the work information registration operation. When "Network Move" is selected as the "Work Type" in this way, an information input area AR40 is displayed on the work information registration screen, where information corresponding to "Network Move" can be entered. Below the information input area AR40, an input area AR21-2 for "What time has this work been done?" and an input area AR21-3 for "Work Notes" are arranged.

[0047] The work information registration screen corresponding to such "network movement" is configured such that the area shown in Figure 5(B) continues below the area shown in Figure 5(A), and it is possible to scroll up and down.

[0048] In the information input area AR40, there are arranged a "net location" input area AR41-1, a "destination" input area AR41-2, and a "number of nets to move" input area AR41-3. The "net location" input area AR41-1 is used to input the location of the net before it was moved in the net movement that was performed this time. In this case, the "net location" input area AR41-1 allows the user to select a location from the options presented in a pull-down menu. The "destination" input area AR41-2 is used to input the location of the network to be moved to during the current network move. Specifically, as a mode of inputting the destination location into the "destination" input area AR41-2, the user U may perform an operation to specify one piece of location information from among the registered location information. In this case, the location corresponding to the specified location information is input as the destination. The "Number of nets to move" input area AR41-3 is used to input the number of nets moved in the current net movement. The "Number of nets to move" input area AR41-3 may be used to input a number corresponding to the number of nets, for example, by text.

[0049] Furthermore, user U may enter a numerical value (digit) indicating which unit of aquaculture the net movement performed this time corresponds to in the ``What number of tasks is this?'' input area AR21-2, and may also enter text as necessary in the ``Work notes'' input area AR21-3.

[0050] In this case as well, the user U inputs each piece of information as described above and then operates the registration button BT22. In response to the operation of the registration button BT22, the work information of "moving the net" that reflects the content input on the work information registration screen as shown in Figures 5(A) and 5(B) is registered in the aquaculture management device 200. In addition, in response to the operation of the registration button BT22, the application screen of the aquaculture management application transitions from the work information registration screen to the work information registration screen, and the work information list area AR12 of the transitioned work information registration screen is arranged so that the list item of the work information for "net movement" that has just been registered is added.

[0051] Note that the manner of input operation for the input areas arranged on the application screens shown in Figures 3 to 5 is one example. For example, instead of the input areas as pull-down menus shown in Figures 3 to 5, an input area where text such as letters and numbers can be input may be arranged, or instead of the input area where text can be input, an input area with a pull-down menu, buttons, etc. where an operation of selecting from predetermined options can be performed may be arranged.

[0052] When inputting work information, for example, user U can manage the number of times a work has been performed for each process in one unit of aquaculture by entering a number in the "How many times has this work been performed?" input area AR21-2. However, one user U may manage multiple unit of aquacultures collectively. In this case, work information corresponding to each process in multiple unit of aquacultures may be registered. Therefore, when user U registers work information, user U may be able to enter information identifying which of the multiple unit of aquacultures currently being performed or planned to be performed by user U corresponds to the process corresponding to the work information to be registered. For example, the work information registration screen may allow an operation to input a name, number, symbol, or the like assigned to the unit of aquaculture. By including information identifying the unit of aquaculture in the work information in this way, the aquaculture management device 200 can, for example, present the work information for each process unit registered by user U on the screen of the aquaculture management application of the user terminal 100 in a manner that allows distinction for each unit of aquaculture.

[0053] [Example of functional configuration of user terminal] An example of the functional configuration of the user terminal 100 will be described with reference to Fig. 6. The user terminal 100 may be configured with hardware such as a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and storage devices such as HDD (Hard Disk Drive) and SSD (Solid State Drive). The functions of the user terminal 100 shown in the figure are realized by the CPU provided in the user terminal 100 executing a program.

[0054] The user terminal 100 in the figure includes a communication unit 101, a user interface unit 102, a control unit 103, and a storage unit 104.

[0055] The communication unit 101 is communicably connected to the aquaculture management device 200 via a network.

[0056] The user interface unit 102 includes an input device operated by the user U, a display unit that outputs information to the user U, and an audio output unit. The user interface unit 102 may include a touch panel that allows operations on the display surface.

[0057] The control unit 103 executes various controls in the user terminal 100. The control unit 103 includes an application support processing unit 131 (an example of an input receiving unit). The application processing unit 131 executes processing corresponding to the aquaculture management application. The application processing unit 131 displays the application screen of the aquaculture management application on the display unit in the user interface unit 102. The application processing unit 131 also accepts input operations on the application screen for registering work information and location information. The application processing unit 131 transmits the input work information or location information from the communication unit 101 to the aquaculture management device 200. The aquaculture management device 200 registers the received work information and location information.

[0058] Furthermore, the application processing unit 131 accepts an operation to change the information content on the work information confirmation screen or the location information confirmation screen, and transmits change information indicating the changed information content to the aquaculture management device 200. The aquaculture management device 200 updates the corresponding work information or location information so as to reflect the change in the information content indicated by the received change information.

[0059] The storage unit 104 stores various types of information corresponding to the user terminal 100 .

[0060] [Example of functional configuration of aquaculture management device] An example of the functional configuration of the aquaculture management device 200 will be described with reference to Fig. 7. The aquaculture management device 200 may be configured to include, as hardware, a CPU, a ROM, a RAM, a storage device such as an HDD or an SSD (Solid State Drive), etc. The functions of the aquaculture management device 200 shown in the figure are realized by the CPU provided in the aquaculture management device 200 executing a program.

[0061] The aquaculture management device 200 in the figure includes a communication unit 201, a control unit 202, and a storage unit 203. The communication unit 201 is connected to the user terminal 100 via a network so that communication can be performed.

[0062] The control unit 202 executes various controls in the aquaculture management device 200. The control unit 202 includes an information registration unit 221 and an information presentation unit 222.

[0063] The information registration unit 221 registers the work information and location information transmitted from the user terminal 100 as aquaculture management information. The information registration unit 221 registers the aquaculture management information by storing the work information and location information transmitted from the user terminal 100 in the storage unit 203.

[0064] The information presentation unit 222 controls so that various information is presented on the user terminal 100. For example, the information presentation unit 222 transmits the aquaculture management information (work information, location information) stored in the storage unit 203 in response to a request from the user terminal 100, thereby presenting the aquaculture management information (work information, location information) on the user terminal 100.

[0065] The storage unit 203 stores various types of information corresponding to the aquaculture management device 200. The storage unit 203 includes an aquaculture management information storage unit 231 and a branch information storage unit 232. The aquaculture management information storage unit 231 stores aquaculture management information for each user. The branch information storage unit 232 stores information about each branch (branch information). The aquaculture management system of this embodiment is targeted at, for example, a fisheries cooperative that cultivates mozuku seaweed in a certain area. The fisheries cooperative is divided into multiple branches (an example of a group) according to, for example, the fishing port nearest to the area, and the user U belongs to one of the branches. Note that if aquaculture management does not need to be performed on a branch-by-branch basis, it is not necessary to store branch information, and therefore the branch information storage unit 232 may be omitted.

[0066] FIG. 8(A) shows an example of the user-specific aquaculture management information stored in the aquaculture management information storage unit 231 in association with one user U. The user-specific aquaculture management information in the figure includes fields for user account, user basic information, affiliated branch, registered work information, registered location information, and registered performance information. The user account field stores a user account. The user account includes, for example, a user ID, a password, etc. The user account is used by the user U to log in to the aquaculture management application. The user basic information field stores user basic information, which may include information such as the name (user name) of the user U, phone number, gender, age, and address. The field of the affiliated branch stores the branch ID indicating the branch to which the corresponding user U belongs. The registered work information field stores one or more pieces of work information registered by the corresponding user U. The registered location information field stores one or more pieces of location information registered by the corresponding user U.

[0067] The registered performance information field stores one or more pieces of performance information that record the performance of the corresponding user U regarding mozuku cultivation. Although not illustrated, the user U can input information related to the performance of the cultivated mozuku as performance information by operating the cultivation management application running on the user terminal 100. Specifically, the user U may be able to input the harvest date and time of the mozuku, the harvest location, the harvest amount, the quality of the harvested mozuku, etc., as performance information. Furthermore, the quality may be the degree of maturity, taste, color, thickness, shape, etc. Furthermore, the performance information may be information managed for each unit of aquaculture, with the performance information for each unit of aquaculture being input. The performance information for one unit of aquaculture may include the total number of nets thrown into the tank in the corresponding unit of aquaculture (number of nets thrown into the tank), the harvest volume in the corresponding unit of aquaculture (e.g., total harvest volume, harvest volume per location, etc.), and the number of landing nets in the corresponding unit of aquaculture (e.g., total number of landing nets, number of landing nets per location, etc.). The aquaculture management application transmits the input performance information to the aquaculture management device 200. The aquaculture management device 200 stores the received performance information in the field of the registered performance information of the corresponding user U.

[0068] FIG. 8(B) shows an example of work information corresponding to the work type "tank loading" as one piece of work information stored in the registered work information field (FIG. 8(A)) in the aquaculture management information. The work information corresponding to the work type "tank loading" includes fields for the work date, work type, number of nets, work times, and work notes.

[0069] The work date field stores the date (work date) on which the corresponding work was performed. The work date stored in the work date field is specified on the calendar on the calendar screen by the user U, and reflects the date displayed in the date area AR15 on the work information registration screen (FIG. 3(A)).

[0070] The work type field stores the work type "tank loading" input by the user U in the "work type" input area AR20 on the work information registration screen (FIG. 3(A)).

[0071] The number of nets field stores the number of nets that were put into the tank in the corresponding work. In other words, the number of nets field stores the value entered by the user U in the "number of nets" input area AR21-1 on the work information registration screen (FIG. 3(A)).

[0072] The work count field stores the number of times that the corresponding tank loading work has been carried out in the unit of aquaculture that has been carried out so far. In other words, the work count field stores the number entered by user U in the "How many times is this work?" input area AR21-2 on the work information registration screen (Figure 3(A)).

[0073] The work memo field stores the text (work memo) entered by the user U in the "work memo" input area AR21-3 on the work information registration screen (FIG. 3(A)).

[0074] FIG. 8(C) shows an example of work information in which the work type of “moving a net” is selected as one piece of work information stored in the field of registered work information (FIG. 8(A)) in the aquaculture management information. The work information corresponding to the work type "net movement" includes fields for the work date, work type, net location, movement destination, number of nets, work times, and work notes.

[0075] The work date field stores the date (work date) on which the corresponding work was performed. The work date stored in the work date field is specified on the calendar on the calendar screen by the user U, and reflects the date displayed in the date area AR15 on the work information registration screen (FIGS. 5(A) and 5(B)).

[0076] The work type field stores the work type "network movement" input by the user U in the "work type" input area AR20 on the work information registration screen (FIG. 3(A)).

[0077] The net location field stores location information input by the user U in the "net location" input area AR41-1 on the work information registration screen (FIGS. 5(A) and 5(B)). When an operation to input a location name using text, for example, is performed in the "net location" input area AR41-1, the location field of the net stores the location name using the input text. On the other hand, when an operation is performed to specify one piece of location information from among the registered location information as the "location where the net is located" in the "location where the net is located" input area AR41-1, the location field of the net stores the location information ID of the specified location information.

[0078] The destination field stores destination information input by the user U in the "destination" input area AR41-2 on the work information registration screen (FIGS. 5(A) and 5(B)). When an operation to input a place name in text, for example, is performed in the "destination" input area AR41-2, the destination field stores the place name in the input text. On the other hand, when an operation is performed to specify one piece of location information from among the registered location information as the "destination" in the "destination" input area AR41-2, the destination field stores the location information ID of the specified location information.

[0079] The mesh number field stores the numerical value input by the user U in the "number of meshes to be moved" input area AR41-3 on the work information registration screen (FIGS. 5(A) and 5(B)).

[0080] The work number field stores the numerical value input by the user U in the "How many times has this work been done?" input area AR21-2 on the work information registration screen (FIGS. 5(A) and 5(B)).

[0081] The work memo field stores the text (work memo) entered by the user U in the "work memo" input area AR21-3 on the work information registration screen (FIGS. 5(A) and 5(B)).

[0082] FIG. 8(D) shows an example of one piece of location information stored in the field of registered location information (FIG. 8(A)) in the aquaculture management information. The location information includes fields for registration date, location information ID, location name, position information, water depth, bottom sediment, amount of rocks, amount of aquatic plants, and amount of fish. The registration date field stores the date (or date and time) when the corresponding location information was registered as the registration date. The location information ID field stores the location information ID attached to the corresponding location information. The location information ID may be generated when the information registration unit 221 stores the corresponding location information in the aquaculture management information. The place name field stores the place name input by the user U in the place name input area AR31-1 of the place information registration screen (FIGS. 4(B) and 4(C)). The location field stores, for example, latitude and longitude, indicating a location specified by the user U in the map area AR30 of the location information registration screen (FIGS. 4B and 4C). The water depth field stores the water depth value input by the user U in the water depth input area AR31-2 on the location information registration screen (FIGS. 4(B) and 4(C)). The bottom sediment field stores bottom sediment information input by the user U in the bottom sediment input area AR31-3 on the location information registration screen (FIGS. 4(B) and 4(C)). The rock quantity field stores information about the amount of rock input by the user U in the rock quantity input area AR31-4 on the location information registration screen (FIGS. 4(B) and 4(C)). The field for the quantity of aquatic plants stores information on the quantity of aquatic plants input by the user U in the aquatic plant quantity input area AR31-5 on the location information registration screen (FIGS. 4(B) and 4(C)). The field for the amount of fish stores information about the amount of fish input by the user U in the fish amount input area AR31-6 on the location information registration screen (FIGS. 4(B) and 4(C)).

[0083] 8(E) shows an example of branch information stored in association with one branch in the branch information storage unit 232. The branch information in the figure includes fields for branch ID, branch name, target value, and rank (an example of performance). The branch ID field stores the branch ID indicating the corresponding branch. The branch name field stores the name of the corresponding branch (branch name). The target value field stores a target value for aquaculture set by the corresponding branch. The target value may be, for example, the harvest amount set as a target by the corresponding branch, or the quality of the mozuku set as a target by the corresponding branch.

[0084] The rank field stores the rank assigned to the corresponding branch. When branches compete with each other in terms of harvest volume, quality, etc., a rank is assigned based on the performance of the corresponding branch. The information presentation unit 222 in the aquaculture management device 200 may assign a rank based on the results of aggregating the registered performance information for each user U stored in the aquaculture management information by branch.

[0085] The aquaculture management system of this embodiment configured as described above allows a user U, who is a mozuku producer, to register the details of the work he or she has done for each mozuku cultivation process as work information. In other words, each user U can record the work he or she has done for mozuku cultivation. Furthermore, the work information recorded in this way can be displayed on the user terminal 100 and viewed by the user U. For example, mozuku cultivation up until now has relied on the experience and intuition of producers. This has made it difficult to accurately and efficiently transfer techniques related to mozuku cultivation to others. In the cultivation management system of this embodiment, by later checking the contents of the work information that records the work results of each mozuku cultivation process, it is possible to analyze how to perform each process in the cultivation without relying on experience or intuition, and to easily and smoothly transfer this information to others.

[0086] Furthermore, the aquaculture management system of this embodiment is also capable of registering work information for work to be carried out in the future. By being able to register future work registration information in this way, it becomes easy to schedule the processes in a unit aquaculture.

[0087] Furthermore, in the aquaculture management system of this embodiment, it is possible to register location information for the location where work related to Mozuku aquaculture is carried out. The location indicated by this location information is indicated by position information specified on a map by the user U, and therefore can be accurately identified by, for example, latitude and longitude. As described above, the location information confirmation screen, which is an application screen of the aquaculture management application, shows a point corresponding to the location information on a map. By moving to a point shown on the map on the location information confirmation screen as a destination, the user U can accurately move to the corresponding location.

[0088] [Example of processing procedure] An example of a processing procedure executed by the user terminal 100 and the aquaculture management device 200 in relation to the registration of work information will be described with reference to the sequence diagram of FIG.

[0089] Step S100: The user U operates the aquaculture management application running on the user terminal 100 to display the work information registration screen (FIG. 3(A)) as the application screen. In response to this operation, the application processing unit 131 of the user terminal 100 displays the work information registration screen on the display unit.

[0090] Step S102: The user U performs an operation to input information into each input area (AR20, AR21-1 to AR21-3) on the displayed work information registration screen. The application processing unit 131 of the user terminal 100 receives the information input operation into each input area, thereby acquiring the information input into each input area. When operating the input areas, the user U can input information into each input area in any order. The user U can also perform an operation to re-input information into an input area into which information has already been input.

[0091] Step S104: When the user U has finished inputting information into each input area on the work information registration screen, the user U operates the registration button BT22. In response to the operation of the registration button BT22, the application-related processing unit 131 of the user terminal 100 transmits work information including the information acquired in response to step S102 to the aquaculture management device 200. The user ID of the user U is assigned to the transmitted work information.

[0092] Step S106: In the aquaculture management device 200, the information registration unit 221 registers the work information transmitted from the user terminal 100 in step S104. That is, the information registration unit 221 stores the work information transmitted in step S104 in the aquaculture management information of the corresponding user U, and stores it in the aquaculture management information storage unit 231.

[0093] An example of a processing procedure executed by the user terminal 100 and the aquaculture management device 200 in relation to the registration of location information will be described with reference to the sequence diagram of FIG. Step S200: The user U operates the aquaculture management application running on the user terminal 100 to display the location information registration screen (FIG. 3(A)) as the application screen. In response to this operation, the application processing unit 131 of the user terminal 100 displays the location information registration screen on the display unit.

[0094] Step S202: The user U performs an operation to specify a point on the map displayed in the map area AR30 on the displayed location information registration screen (point specification operation). The application processing unit 131 of the user terminal 100 receives the point specification operation and acquires the coordinates (latitude and longitude) of the specified point.

[0095] Step S204: The user U performs an operation to input information into each input area (AR31-1 to AR31-7) on the location information registration screen. The application processing unit 131 of the user terminal 100 receives the information input operation into each input area, thereby acquiring the information input into each input area.

[0096] The location designation operation and the information input operation for each input area may be performed in any order. For example, it may be possible to perform the location designation operation after performing the information input operation for some input areas, and then perform the information input operation for the remaining input areas after the location designation operation. It may also be possible to perform an operation to input information again into an input area into which information has already been input.

[0097] Step S206: When the user U has finished inputting information into each input area (AR20, AR21-1 to AR21-3) on the location information registration screen, the user U operates the registration button BT22. In response to the operation of the registration button BT22, the application-compatible processing unit 131 of the user terminal 100 transmits location information including the information acquired in response to step S102 to the aquaculture management device 200. The user ID of the user U is assigned to the transmitted location information.

[0098] Step S208: In the aquaculture management device 200, the information registration unit 221 registers the location information transmitted from the user terminal 100 in step S206. That is, the information registration unit 221 stores the location information transmitted in step S206 in the aquaculture management information of the corresponding user U, and stores it in the aquaculture management information storage unit 231.

[0099] Second Embodiment Hereinafter, another example of the configuration of the application screen of the aquaculture management application that operates on the user terminal 100 will be described as a second embodiment. Fig. 11 shows an example of a work information registration screen in this embodiment, in which the same parts as those in Fig. 3(A), Fig. 5(A), and Fig. 5(B) are given the same reference numerals. The work information registration screen in the figure has a date area AR15. The date area AR15 indicates the date to which the work information being registered corresponds. The date shown in the date area AR15 may reflect the date specified on the calendar when the registration button BT11 on the calendar screen (FIG. 12(A)) of this embodiment, which will be described later, is operated.

[0100] The work information registration screen in the figure also has a "Work Type" input area AR20. The "Work Type" input area AR20 is used to select a work type corresponding to each process in the cultivation of mozuku. In this embodiment, as in the first embodiment, the "Work Type" input area AR20 is used to select a work type using a pull-down menu. The "Work Type" input area AR20 may be configured to allow selection of a work type corresponding to each process of seedling collection, sowing, net movement, final setting, and harvesting. Furthermore, depending on the process, two or more work types may be provided as options.

[0101] The work information registration screen in the figure shows an example of what happens when "Network Move" is entered in the "Work Type" input area AR20. When "Network Move" is selected as the "Work Type" in this way, various areas are provided below the "Work Type" input area AR20 on the work information registration screen where information corresponding to "Network Move" can be entered.

[0102] Specifically, in the same figure, in the area below the "Work type" input area AR20, there are arranged, in order, a "What time is this work?" input area AR21-2, an information input area AR40, a "Number of nets to move" input area AR41-3, a growth status input area AR41-4, a water temperature input area AR21-5, a "Work notes" input area AR21-3, a back button BT21, and a registration button BT22.

[0103] In the "What number of times is this operation?" input area AR21-2, a numerical value (digit) indicating which unit aquaculture period the net movement performed this time corresponds to is input.

[0104] The information input area AR40 is an area where information corresponding to "network movement" can be input. In the information input area AR40, a "network location" input area AR41-1, a "destination" input area AR41-2, and an add location button BT23 are arranged. In the "net location" input area AR41-1, an operation is performed to input the location of the net before the movement that was performed in the current net movement, for example, by selecting an option from a pull-down menu. In the "destination" input area AR41-2, an operation is performed to input the location of the network destination in the network movement currently performed, for example, by selecting an option from a pull-down menu. The add location button BT23 is a button that the user U operates when inputting the destination location of the network in the currently performed network move and there is no corresponding location in the options of the pull-down menu in the "network destination" input area AR41-2. For example, when the add location button BT23 is operated, the display transitions to the location information registration screen (FIGS. 4(B) and 4(C)). The user U can register a new location on the displayed location information registration screen. In this case, when the register button BT33 on the location information registration screen is operated, the display returns to the work information registration screen of FIG. 11. The name of the registered location is displayed in the "network destination" input area AR41-2 on the displayed work information registration screen.

[0105] The "Number of nets to move" input area AR41-3 is used to input the number of nets moved in the current net movement. The "Number of nets to move" input area AR41-3 may be used to input a number corresponding to the number of nets, for example, by text.

[0106] The growth status input area AR41-4 is used to input the growth status of the mozuku seaweed attached to the net during the current net movement. Specifically, in the growth status input area AR41-4 in the same figure, for example, five stages of growth status are set, and options for each set growth status are arranged horizontally. Each option is provided with a facial image showing an expression corresponding to the corresponding growth status. The user U determines which of the options arranged in this way corresponds to the actual growth status and then selects the corresponding option. The selected option is highlighted in a predetermined manner to indicate the selected growth status. The growth status information input in this manner may be stored, for example, in the corresponding work information (Figures 8(B) and 8(C)), or may be stored in association with the corresponding work information in the registered performance information.

[0107] The water temperature input area AR21-5 is used to input information about the water temperature at the current net move. The water temperature input area AR21-5 may be configured to allow input of information about the water temperature using text. For example, the user U can input information about the water temperature at the destination location of the current net move.

[0108] The "Work Memo" input area AR21-3 is an area where the user U can input, in text, any matters that he or she wishes to record as a memorandum regarding the network movement work that he or she has just performed.

[0109] Furthermore, when the user U wants to clear the content input on the work information registration screen in the same figure, the user U operates the back button BT21. In response to the operation of the back button BT21, the content input on the work information registration screen in the same figure is cleared, and the display returns to the calendar screen in Fig. 12(A) described below.

[0110] Furthermore, when the user U wishes to register the work information input on the work information registration screen in the same figure, the user U operates the registration button BT22. In response to the operation of the registration button BT22, the work information of "moving the net" reflecting the content input on the work information registration screen as shown in Figure 11 is registered in the aquaculture management device 200. Furthermore, when the registration button BT22 is operated, the display returns to the calendar screen in Figure 12(A) described below, and a work information list area AR12 including a list item of the work information registered this time is additionally arranged on the calendar screen.

[0111] Fig. 12(A) shows an example of a calendar screen in this embodiment, in which the same parts as those in Fig. 3(B) are given the same reference numerals. The calendar screen in the figure includes a calendar area AR11, a work information list area AR12, a calendar transition button BT12, a location status screen transition button BT14, and a harvest record screen transition button BT15.

[0112] The calendar area AR11 is an area where a calendar is displayed. The work information list area AR12 is an area where list items for each piece of work information that has been registered so far are presented. When one of the list items presented in the work information list area AR12 is selected and operated, the display transitions to a work information registration screen where the work information corresponding to the operated list item has already been entered. In this case, the user U can edit the registered work information, such as by correcting or changing it, by operating the displayed work information registration screen.

[0113] The calendar transition button BT12 is a button that is operated to return the display to the calendar area AR11 when the area corresponding to the calendar area AR11 is displaying something other than a calendar.

[0114] The location situation screen transition button BT14 is a button for performing an operation to transition to a location situation screen shown in FIG. 12(B) described later. The harvest record screen transition button BT15 is a button that is operated to transition to the harvest record screen shown in FIG. 13(A) described below.

[0115] Fig. 12(B) shows an example of a location status screen. The location status screen is a screen that presents the work status for each location registered as a location status. The location status screen of this embodiment is a screen that replaces the location information list screen (Fig. 4(A)) in the first embodiment. In this embodiment, the location may be registered by operating a location information registration screen similar to those shown in FIGS. 4(B) and 4(C) to register the location information.

[0116] 12(B), a list item LT1 is arranged for each registered location. Each list item LT1 shows the name of the registered location, the type of work last performed at the registered location ("Recent Work"), and the date on which the "Recent Work" was performed ("Work Date").

[0117] A work list button BT51 is arranged in list item LT1. When the work list button BT51 is operated, the screen transitions to the display of a work list screen that presents a list of the work performed at the corresponding location.

[0118] Additionally, an edit button BT52 is arranged in list item LT1. When the edit button BT52 is operated, the display transitions to a location information registration screen (FIGS. 4(B) and 4(C)) in which information about the corresponding location has already been entered. The user U can edit the registered location information by operating the displayed location information registration screen, such as correcting or changing it.

[0119] Additionally, the location status screen has a location registration ("add work location") button BT30. When the location registration button BT30 is operated, the screen transitions to the location information registration screen (FIGS. 4(B) and 4(C)).

[0120] Also, similar to FIG. 12(A), a calendar transition button BT12, a location status screen transition button BT14, and a harvest record screen transition button BT15 are arranged below the location status screen.

[0121] Fig. 12(C) shows an example of the work list screen. As described above, the work list screen is displayed in response to the operation of the work list button BT51 located on the list item LT1 of the location status screen of Fig. 12(B).

[0122] The work list screen of Fig. 12(C) has a list item LT2 for each work (process unit) registered as having been performed at the corresponding location. The work information for each list item LT2 may be registered by operating the work information registration screen of Fig. 11. The location associated with the registered work information may be the location entered in the "Location where the net is located" input area AR41-1 and the "Location where the net is located" input area AR41-1 in the information input area AR40 of the work information registration screen of Fig. 11.

[0123] List item LT2 presents the name of the corresponding work type, the number of times the corresponding work has been performed, the date on which the corresponding work was last performed (the most recent work date), the source and destination of the network (if the corresponding work type is a network move), and notes (the content entered in the "Work notes" input area AR21-3 on the work information registration screen). Furthermore, at the left end of list item LT2, a work type identification mark MK is arranged in the vertical direction to indicate the work type by color coding.

[0124] 12(C) has a descending order button BT61-1 and an ascending order button BT61-2 arranged. When the descending order button BT61-1 is operated, the list items LT2 are sorted in descending order of the most recent work date. When the ascending order button BT61-2 is operated, the list items LT2 are sorted in ascending order of the most recent work date. Furthermore, one of the descending order button BT61-1 and the ascending order button BT61-2 is highlighted depending on whether the list items LT2 are currently sorted in descending order or ascending order of the most recent work date.

[0125] Furthermore, the task list screen of FIG. 12(C) has a year selection section PM61. The year selection section PM61 is a section where an operation is performed to switch the list items presented on the task list screen by year. In the example of the same figure, the year selection section PM61 presents options for the presented period based on year units using a pull-down menu. The options may include, for example, a period of multiple consecutive years or a period of all years in addition to a single year. The task list screen of FIG. 12(C) has a list item LT2 of tasks whose most recent work date falls in the year selected by an operation on the year selection section PM61.

[0126] In addition, since the registration button BT11 is also located on the work list screen of FIG. 12(C), the user can operate the registration button BT11 to transition from the work list screen to the work information registration screen (FIG. 11).

[0127] By viewing the location status screen (FIG. 12(B)) on which list item LT1 is arranged as described above, user U can check the registered locations in a list. Furthermore, the content presented in list item LT1 allows the user U to roughly grasp the status of work for each registered location. Then, by operating the work list button BT51 arranged in list item LT1 and viewing the displayed work list screen (FIG. 12(C)), user U can grasp the history of each work performed at the corresponding location.

[0128] As the number of places registered by the user U increases, the number of list items LT1 arranged on the place status screen (FIG. 12(B)) also increases, making it difficult for the user U to quickly find the list item for the place he or she wants to check. Therefore, for example, an operation to input place extraction conditions may be possible as an operation on the place status screen, and list items LT1 extracted as matching the input place extraction conditions may be presented on the place status screen. The place extraction conditions may be, for example, the name of the place input by character input, or may be, for example, a range specified on a map.

[0129] Fig. 13(A) shows an example of the harvest record screen. The harvest record screen is displayed in response to operation of the harvest record screen transition button BT15 located on the calendar screen (Fig. 12(A)) or the location status screen (Fig. 12(B)). The harvest performance screen includes a year selection section PM71 and a number of times selection section PM72. The year selection section PM71 is used to select the year to which the harvest record displayed on the harvest record screen corresponds. In the figure, an example is shown in which the year selection section PM71 is in the form of a pull-down menu. The number of times selection unit PM72 is used to select the unit of aquaculture that corresponds to the harvest record presented on the harvest record screen. In the same figure, an example is shown in which the number of times selection unit PM72 is in the form of a pull-down menu. Here, an operation is performed to select a number indicating the number of times (or the order) that the unit of aquaculture has been carried out in the year selected by the operation on the year selection unit PM71.

[0130] The harvest performance screen displays the harvest performance of the unit of aquaculture selected by operating the number of times selection unit PM72 for the year selected by operating the year selection unit PM71. Specifically, in Fig. 12(A), the following items are displayed as harvest performance: "Number of nets thrown into tank," "Harvest volume," "Number of landing nets," "Number of landing nets / Number of nets thrown into tank," and "Harvest volume / Number of landing nets." The item "Number of nets added to tank" indicates the number of nets added to the tank in the corresponding unit of aquaculture. The "Yield" item indicates the total yield for the corresponding unit of aquaculture. The "Number of nets landed" item indicates the number of nets landed in the corresponding unit of cultivation. Among the nets thrown into the tank, there may be some that are broken for some reason and cannot be used for growing Mozuku, and therefore cannot be landed. For this reason, the "Number of nets landed" may be less than the "Number of nets thrown into the tank." The item "Number of nets landed / Number of nets thrown into tank" indicates the ratio of the number of nets landed to the number of nets thrown into the tank in the corresponding unit of aquaculture. "Yield / number of nets landed" indicates the yield per unit of net landed (e.g., one net). "Number of nets landed / number of nets placed in tank" and "harvest yield / number of nets landed" are indicators showing the yield situation based on the number of nets used for aquaculture.

[0131] The harvest record presented on such a harvest record screen may be displayed based on the registered record information (FIG. 8(A)).

[0132] On the harvest record screen, a screen count history screen transition button BT71 is arranged. When the screen count history screen transition button BT71 is operated, the display transitions to the screen count history screen.

[0133] Figure 13(B) shows an example of the screen for the history of net count. The screen for the history of net count shows the number of nets used for cultivating Mozuku in the corresponding unit of cultivation for each work process. The screen for the history of net count in the same figure shows the number of nets used, the total harvest amount, the release date of the corresponding unit of cultivation, and the corresponding number of times (order) of the unit of cultivation at the top. On the screen count history screen, boxes BX (BX-1 to BX-7 (examples of layout elements)) corresponding to each process unit are arranged in a flow chart-like fashion from top to bottom in the chronological order of the processes. Following the process of moving the screen to location N2 indicated by box BX-3, two boxes BX-4 and BX-6 are connected in parallel, indicating that the screen used in the two processes of final laying at location A and final laying at location C has been divided. Furthermore, each box BX displays the name of the corresponding process, the location where the corresponding process was performed, the number of nets used in the corresponding process, and the date on which the work in the corresponding process was performed. The screen count history screen can be scrolled up and down. For example, by scrolling the screen upward from the state shown in the figure, a box BX corresponding to a subsequent process can be displayed. The box BX may be configured differently depending on the type of process. For example, the color of the border of the box BX or the inside of the box BX may be different for each type of process.

[0134] By looking at the screen count history screen in this manner, user U can easily understand the changes in the number of nets used at each process in the process flow of the unit aquaculture.

[0135] Furthermore, by operating the box BX, a process unit information screen is displayed that presents information on the corresponding process. Figure 13(C) shows an example of the process unit information screen P81. The process unit information screen P81 in the figure is a screen displayed by operating box BX-6 on the halftone sheet count history screen in Figure 13(B). In this case, the process unit information screen P81 is shown as being superimposed on the halftone sheet count history screen. The process unit information screen P81 displays the name of the corresponding process ("Main laying (placement)"), the location where the corresponding process was performed, the number of screen sheets used in the corresponding process, the harvest yield in the corresponding process, the start date of the corresponding process, the end date of the corresponding process, and the work period. The information presented on this process unit information screen P81 may be presented based on the registered work information (FIGS. 8(B) and 8(C)). In this case, the work date field in the work information may be structured to store the work start date and work end date. By viewing the process unit information screen P81, the user U can understand the relationship between the number of nets and the harvest amount in each process unit.

[0136] As described above, the screens shown in Figures 13(A), 13(B), and 13(C) allow accurate understanding of the relationship between the number of nets used and the harvest yield for each process in each unit of cultivation. This allows, for example, user U to more effectively formulate future mozuku cultivation plans, while utilizing, for example, experience and intuition. Furthermore, when filing a mutual aid claim in the event of a harvest failure due to damage to many nets caused by a typhoon or other event, proof of data showing the harvest yield and the impact of the preceding steps is required. In this embodiment, the information presented on the screens shown in Figures 13(A), 13(B), and 13(C) can be used to easily prove the data required for a mutual aid claim.

[0137] <Overview of various functions in the aquaculture management system> As described above, the aquaculture management system of each embodiment allows user U to register work information and location information for each process, and the registered work information and location information can be displayed on the application screen of an aquaculture management application running on user terminal 100. In addition, the aquaculture management system of this embodiment may be implemented with various functions such as those described below.

[0138] [Lunar calendar display on calendar screen] The calendar displayed in the calendar area AR11 of the calendar screen shown in FIG. 2(A) and other figures is the Gregorian calendar. However, the calendar displayed in the calendar area AR11 may be, for example, the lunar calendar. In the lunar calendar, the length of a month is determined according to the phases of the moon. In other words, the divisions of months in the lunar calendar correspond to the ocean tides. Because most of the processes for producing mozuku are carried out at sea, some users U, who are producers, desire to carry out their work according to the lunar calendar rather than the Gregorian calendar. If the calendar screen is displayed according to the lunar calendar, this desire of users U can be met. On the other hand, even if a user U uses the lunar calendar for mozuku cultivation work, there may be cases where the user U needs to refer to dates in the Gregorian calendar, or some users U may wish to work in the Gregorian calendar rather than the lunar calendar. Therefore, the calendar display in the calendar area AR11 may be switchable between the Gregorian calendar and the lunar calendar, for example, in response to an operation by the user U. Even when switching between the Gregorian calendar and the lunar calendar as described above, the current date may be highlighted on both the Gregorian calendar and the lunar calendar. Also, even when switching between the Gregorian calendar and the lunar calendar, a badge BG indicating that task information has been registered may be placed on the corresponding date on both the Gregorian calendar and the lunar calendar.

[0139] [Information sharing function] The aquaculture management system of this embodiment may allow users U to share aquaculture management information (work information, location information). In this case, for example, the aquaculture management device 200 may store shared user information indicating the relationship between users U who can share the aquaculture management information in the storage unit 203. The users U who can share the aquaculture management information may be set by the users U operating the aquaculture management application running on the user terminal 100. Among users U who have a relationship in which they can share information, for example, the aquaculture management information of the other users U that can share information can be displayed on the user terminal 100 of one user U. At this time, in response to a request for shared information from the aquaculture management application of the user terminal 100, the information presentation unit 222 of the aquaculture management device 200 refers to the shared user information to identify the other users U who have an information sharing relationship with the user U corresponding to the requesting aquaculture management application. The information presentation unit 222 acquires the aquaculture management information of the identified other users U from the aquaculture management information storage unit 231 and transmits the acquired aquaculture management information to the requesting user terminal 100. The aquaculture management application of the requesting user terminal 100 displays the received aquaculture management information of the other users U. In this way, by allowing aquaculture management information to be shared between users, the work content, techniques, work locations, etc. of each process in aquaculture can be communicated to others more smoothly.

[0140] Note that some users U may not want their own aquaculture techniques to be known to other users U. To accommodate such cases, for example, each user U may be able to set whether or not to share the aquaculture management information that he or she has registered. The user U can perform an operation to set whether or not sharing is possible for the aquaculture management application running on the user terminal 100. The information registration unit 221 of the aquaculture management device 200 stores sharing possibility information indicating whether or not sharing is possible, which is set by the operation, in the storage unit 203. As an example, the sharing possibility information may be stored so as to be included in the aquaculture management information of the corresponding user U.

[0141] [About work notification] Task information can also be registered to correspond to a future date rather than the current date. In other words, user U can register task information that is scheduled to be performed in the future by specifying a future date on the calendar screen. The information presentation unit 222 of the aquaculture management device 200 may be configured to notify (remind) the corresponding user U that the work should be performed at a predetermined timing corresponding to the work date indicated in the work information registered as a future schedule in this way, on the user terminal 100 of the corresponding user U. Such notification may be made as a notification on the aquaculture management application by push notification or the like, or may be sent by email to the email address registered by the user U. The timing of the notification may be predetermined, for example, a predetermined date corresponding to the date when the work is to be performed, or may be set by the user U's operation on the aquaculture management application running on the user terminal 100. The information registration unit 221 of the aquaculture management device 200 stores the notification timing set by the user U's operation in the storage unit 203. Specifically, the notification timing information indicating the notification timing set by the user U's operation may be stored in the aquaculture management information of the corresponding user.

[0142] [About group grade presentation] As shown in Fig. 8(E), the branch information stores a target value. The information presentation unit 222 of the aquaculture management device 200 may obtain the achievement status of the branch with respect to the target value. The aquaculture management device 200 may transmit the obtained achievement status to the user terminal 100 of the user U who belongs to the corresponding branch, so that the achievement status of the branch is presented in the aquaculture management application. In addition, the branch information stores a rank. Therefore, the information presenting unit 222 may notify the assigned rank to the user U via the aquaculture management application of the user terminal 100 of the user U who belongs to the corresponding branch.

[0143] In addition, it is possible to set target values and ranks for each user U, and then apply the above configuration so that the achievement status and rank for each user U are presented in the aquaculture management application.

[0144] [Visualization of performance information] The information presentation unit 222 of the aquaculture management device 200 may visualize the results based on the registered results information stored in the aquaculture management information for each user U and present the results on the aquaculture management application of the user terminal 100. As a specific example, the information presenting unit 222 may generate a performance screen showing, for example, a harvest volume by year using a graph or the like based on the registered performance information stored in the aquaculture management information for each user U, and the generated performance screen may be presented on the user terminal 100. Such a performance screen may correspond to any of a user unit, a branch unit, a fisheries cooperative unit, a region unit, a predetermined region unit, etc. Furthermore, it may be possible to specify the unit of the performance screen to be presented by operating the aquaculture management application.

[0145] In addition, the information presentation unit 222 may visualize, for example, production conditions for each unit of aquaculture based on registration work information and registration location information stored in the aquaculture management information for each user U, and present them on the aquaculture management application of the user terminal 100. As a specific example, the production conditions may indicate the dates on which each process was carried out for the time series of the target unit aquaculture, and may present the location and location environment (water depth, bottom sediment, amount of rocks, amount of aquatic plants, amount of fish, water temperature, hours of sunlight, etc.) corresponding to each process. The information presentation unit 222 generates production condition information presenting the above-mentioned production conditions in response to a request from the user terminal 100, for example, and transmits the information to the user terminal 100. The aquaculture management application of the user terminal 100 displays a screen showing the received production condition information. In this way, by visualizing and presenting information such as past aquaculture performance and production conditions to user U, user U can accurately grasp information about past performance and production conditions and use it as a reference for future aquaculture.

[0146] [Proposal for growing conditions] The information presentation unit 222 may estimate optimal conditions for the growth of Mozuku based on the registration record information, registration work information, registration location information, etc. stored in the aquaculture management information. When estimating the optimal conditions, the information presentation unit 222 may also use, in addition to the aquaculture management information, weather information and sea state information provided on the network as open data, for example. When estimating the optimal conditions, the information presentation unit 222 may use a trained model that has been trained to estimate optimal conditions for the growth of Mozuku in response to input of aquaculture management information, weather information, sea state information, etc. Optimal conditions for growing Mozuku may include, for example, the timing of each process in one unit of cultivation, the location where each process is carried out, the ideal seawater temperature, weather, tides, and the number of workers. The information presenting unit 222 may transmit the estimated optimal conditions to the user terminal 100, so that the optimal conditions are presented on the user terminal 100. If the user U refers to the presented optimal conditions when carrying out future work on cultivating mozuku, improvements in harvest yield, performance, etc. can be expected.

[0147] [About traceability] Based on the aquaculture management information of this embodiment, it is possible to ascertain the time and place where each process in the unit aquaculture was carried out for each user U. In other words, it is possible to track the process in the aquaculture of mozuku. Furthermore, if the work information includes the process of processing after harvesting, it is also possible to track the process from the start of aquaculture to processing. Such information regarding the traceability of cultivation for each user U may be linked to producer information when selling mozuku, for example. Specifically, for example, a two-dimensional code for accessing producer information may be provided on the packaging of the mozuku being sold or on the shelves on which the mozuku is displayed. Consumers can display producer information on their smartphones by reading the two-dimensional code with a smartphone or the like. By viewing the displayed producer information, consumers can understand by which producer the mozuku they are purchasing was cultivated, and at what time and place. This makes it possible, for example, to increase the reliability of the quality of the mozuku produced and promote branding.

[0148] [Linkage with quality inspection equipment] The aquaculture management system of this embodiment may be provided with a quality inspection device that inspects the quality of harvested or processed mozuku. One example of a quality inspection device may be one that irradiates light onto the mozuku to be inspected and inspects the maturity of the mozuku based on the degree of diffusion of the reflected light of the irradiated light (amount of light diffusion). When the aquaculture management system is provided with a quality inspection device in this way, the quality inspection device may be configured to be able to cooperate with the aquaculture management application. As a specific example, the aquaculture management device 200 may store the inspection results of the quality inspection device in association with the user U, who is the producer of the product being inspected, or the branch office or fishery cooperative. The user U performs an operation to instruct the aquaculture management application running on the user terminal 100 to display the quality inspection results. In response to the operation, the user terminal 100 requests the quality inspection results from the aquaculture management device 200. The aquaculture management application of the user terminal 100 displays the received quality inspection results on the application screen.

[0149] [About the target plant] The cultivation object compatible with the cultivation management system of this embodiment is not limited to mozuku, but may be anything that can be cultivated and grown as a marine product. For example, seaweeds such as wakame, kelp, sea lettuce, nori, hijiki, and akamoku have processes and operations similar to those of mozuku, and are therefore suitable for management by the cultivation management system of this embodiment. Furthermore, the cultivation management system of this embodiment may be adapted to handle seaweeds other than those mentioned above, and may be configured to handle the cultivation of, for example, seafood. Furthermore, the cultivation object compatible with the cultivation management system of this embodiment is not limited to those compatible with seawater, but may also be, for example, freshwater fish, shellfish compatible with freshwater, moss, algae, etc.

[0150] [About seaweed attachment materials] In the above embodiments, an example was given in which a net was used as an attachment material to which the Mozuku seaweed, which is the cultivation target, is attached during the seeding work. When seaweed such as Mozuku seaweed is cultivated, an attachment material other than a net, such as a rope, may be used to attach the seaweed.

[0151] Note that a program for implementing the functions of the user terminal 100, the aquaculture management device 200, etc. may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be loaded into a computer system and executed to perform the processing of the user terminal 100, the aquaculture management device 200, etc. Here, "loading a program recorded on a recording medium into a computer system and executing it" includes installing the program on a computer system. The term "computer system" here includes hardware such as an OS and peripheral devices. The term "computer system" may also include multiple computer devices connected via a network, including communication lines such as the Internet, WAN, LAN, and dedicated line. The term "computer-readable recording medium" refers to portable media such as floppy disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as HDDs and SSDs built into a computer system. Thus, a recording medium storing a program may be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code executable on the terminal device. In other words, the format in which the program is stored on the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a form that is executable on the terminal device. The program may be divided into multiple parts, each of which may be downloaded at different times and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a storage medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be one that realizes part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program).

[0152] <Additional Notes> (1) One aspect of this embodiment is a cultivation management system that includes a user terminal and a cultivation management device, and includes an input reception unit in the user terminal that receives input of work information indicating the work content of each process unit in a unit cultivation period from the start of cultivation of the cultivation object to harvest, and an information registration unit in the cultivation management device that acquires the work information input and accepted by the input reception unit and stores the acquired work information in a memory unit.

[0153] (2) One aspect of this embodiment is the development management system described in (1), in which the input receiving unit may receive input of work information indicating the work content associated with the specified date in response to the specification of a date on a calendar.

[0154] (3) One aspect of this embodiment is a cultivation management system described in (1) or (2), wherein the input receiving unit may, in addition to receiving input of work information indicating the work content of the process unit, also receive input of the cultivation status of the object to be cultivated when the process corresponding to the process unit is performed.

[0155] (4) One aspect of this embodiment is a cultivation management system described in any one of (1) to (3), wherein the cultivation object is algae, the process units in the unit cultivation period include at least sowing, main laying, harvesting, and landing, and the input receiving unit may receive a designation of the process unit to which the work information to be input corresponds.

[0156] (5) One aspect of this embodiment is a training management system described in any one of (1) to (4), wherein the information registration unit may be configured so that work information acquired from the user terminal of each of the multiple users and stored in the memory unit can be displayed on each of the user terminals of the multiple users.

[0157] (6) One aspect of this embodiment is the development management system described in (5), in which the information registration unit may be configured to prevent work information associated with a user who has been set as not shareable from being displayed on the user terminal of other users.

[0158] (7) One aspect of this embodiment is a development management system described in any one of (1) to (6), wherein the input receiving unit is capable of receiving input of a location specified on a map, and the information registration unit may store location information indicating the location where the input receiving unit received the input in a memory unit.

[0159] (8) One aspect of this embodiment is the development management system described in (7), in which the information registration unit may store the input location information in the memory unit in association with the work information in response to the input of location information to be associated with the work information being accepted by the input accepting unit.

[0160] (9) One aspect of this embodiment is a development management system described in any one of (1) to (8), wherein the development management device may further include an information presentation unit that presents work information stored in the memory unit on a display unit of the user terminal.

[0161] (10) One aspect of this embodiment is the development management system described in (9), wherein the information presentation unit may display work information associated with a specified date on the display unit in response to a date being specified on a calendar.

[0162] (11) One aspect of this embodiment is the development management system described in (9) or (10), in which the information presentation unit may be configured to execute a notification on the user terminal to prompt the execution of the corresponding process unit based on the date associated with the work information.

[0163] (12) One aspect of this embodiment is a training management system described in any one of (9) to (11), wherein the information registration unit stores performance information indicating training performance corresponding to the unit training period for which the input receiving unit received input in a memory unit, and the information presentation unit may present results associated with the user based on the performance information on the user terminal.

[0164] (13) One aspect of the present embodiment is the cultivation management system according to (12), wherein the input receiving unit may receive input of the performance information including a harvest yield of the cultivation target object.

[0165] (14) One aspect of this embodiment is the development management system described in (12) or (13), in which the information presentation unit may be configured to present on the user terminal the results associated with the groups to which multiple users each belong.

[0166] (15) One aspect of this embodiment is a cultivation management system described in any one of (1) to (14), wherein the cultivation object is algae, and the input receiving unit may receive input of work information including the number of nets to be put into the tank and the number of times it is performed, corresponding to the process unit of tank loading in seedbed installation.

[0167] (16) One aspect of this embodiment is a cultivation management system described in any one of (1) to (15), wherein the cultivation object is algae, and the input receiving unit may receive input of work information including the location of the net from which the net is to be moved, the destination, the number of nets to be moved, and the number of times the work is to be performed, corresponding to the process unit of net movement in seedbed installation.

[0168] (17) One aspect of this embodiment is a cultivation management system according to any one of (1) to (16), wherein the object to be cultivated is algae, and the input receiving unit receives input of work information including the number of algae attachment materials to be added to the tank in each step of tank addition in seedbed installation, which is included in the work information, and the number of attachment materials landed during harvesting, and the information presenting unit may present the yield status of the object to be cultivated (for example, “Number of nets landed / Number of nets added to tank” on the harvest performance screen (Figure 12(A))) based on the ratio between the number of attachment materials included in the work information and the number of attachment materials landed during harvesting.

[0169] (18) One aspect of this embodiment is a cultivation management system according to any one of (1) to (17), in which the cultivation object is algae, the input receiving unit receives input of performance information including the harvest amount and input of work information including the number of attached materials landed during harvesting, and the information presenting unit may present the harvest amount per unit number of landed attached materials as a yield status (for example, “Harvest amount / Number of pieces landed” on the harvest performance screen (Figure 12(A))).

[0170] (19) One aspect of this embodiment is a cultivation management system according to any one of (1) to (18), wherein the cultivation object is algae, the input receiving unit receives input of work information including the number of algae attachment materials used for each process unit, and the information presentation unit presents the number of attachment materials used for each process unit by presenting corresponding placement elements (e.g., boxes BX) arranged in chronological order for the process units.

[0171] (20) One aspect of this embodiment is the training management system according to (19), wherein the information presentation unit may present the placement elements in different formats for each type of process unit.

[0172] (21) One aspect of this embodiment is a cultivation management system according to any one of (1) to (20), wherein the cultivation object is algae, and the input receiving unit is capable of receiving input of additional information, in addition to a location specified on a map, including at least one of the name of the location, water depth, bottom sediment, amount of rocks, amount of aquatic plants, and amount of fish, and the information registration unit may store location information including the location and additional information input by the input receiving unit in a memory unit.

[0173] (22) One aspect of this embodiment is a cultivation management method in a cultivation management system that includes a user terminal and a cultivation management device, the cultivation management method including: an input reception step in which an input reception unit in the user terminal receives input of work information indicating the work content of each process unit in a unit cultivation period from the start of cultivation of the cultivation object to harvest; and an information registration step in the cultivation management device, in which an information registration unit acquires the work information that has been input and accepted by the input reception step, and stores the acquired work information in a memory unit. [Explanation of symbols]

[0174] 100 User terminal, 101 Communication unit, 102 User interface unit, 103 Control unit, 104 Memory unit, 131 Application processing unit, 200 Aquaculture management device, 201 Communication unit, 202 Control unit, 203 Memory unit, 221 Information registration unit, 222 Information presentation unit, 231 Aquaculture management information memory unit, 232 Branch information memory unit

Claims

1. a user terminal and a cultivation management device for managing the cultivation of aquatic products; an input receiving unit in the user terminal that receives input of work information indicating work content for each process in a unit growing period from the start of growing the object to harvest; an information registration unit in the development management device that acquires work information input by the input acceptance unit and stores the acquired work information in a storage unit; A development management system equipped with the above.

2. The input receiving unit receives input of work information indicating work content associated with the specified date in response to the date being specified on the calendar. The training management system according to claim 1 .

3. The input receiving unit receives input of work information indicating the work content of the process unit, as well as input of the growing status of the growing object when the process corresponding to the process unit is performed. The system for managing the development of a plant according to claim 1 or 2.

4. The object to be cultivated is algae, The process units in the unit growing period include at least sowing, main planting, harvesting, and landing, and the input receiving unit receives designation of the process unit corresponding to the work information to be input. The system for managing the development of a plant according to claim 1 or 2.

5. The information registration unit sets the work information acquired from the user terminals of the plurality of users and stored in the storage unit so that the work information can be displayed on each of the user terminals of the plurality of users. The system for managing the development of a plant according to claim 1 or 2.

6. The information registration unit sets the work information associated with the user set as not shareable so that the work information cannot be displayed on the user terminal of another user. The training management system according to claim 5 .

7. the input receiving unit is capable of receiving an input of a position designated on a map, The information registration unit stores location information indicating a location where the input receiving unit received the input in a storage unit. The system for managing the development of a plant according to claim 1 or 2.

8. When the input receiving unit receives input of location information to be associated with work information, the information registration unit stores the input location information in a storage unit in association with the work information. The system for managing the development of animals according to claim 7 .

9. The development management device further includes an information presentation unit that causes the work information stored in the storage unit to be presented on the display unit of the user terminal. The system for managing the development of a plant according to claim 1 or 2.

10. The information presenting unit, in response to a date being specified on the calendar, causes the display unit to display task information associated with the specified date. The breeding management system according to claim 9 .

11. The information presentation unit causes a notification to be issued to the user terminal, urging the user to carry out the corresponding process unit, based on the date associated with the work information. The breeding management system according to claim 9 .

12. The information registration unit stores, in a storage unit, performance information indicating performance related to training corresponding to the unit training period for which the input is received by the input receiving unit; The information presentation unit presents the results associated with the user based on the performance information on the user terminal. The breeding management system according to claim 9 .

13. The input receiving unit receives input of the performance information including the harvest yield of the cultivation object. The development management system according to claim 12 .

14. The information presentation unit presents the results associated with each group to which a plurality of users belong on the user terminal. The development management system according to claim 12 .

15. The object to be cultivated is algae, The input receiving unit receives input of work information including the number of algae attachment materials to be added to the tank and the number of times the work is to be performed, in accordance with the step unit of adding the algae to the tank in the seedbed installation. The system for managing the development of a plant according to claim 1 or 2.

16. The object to be cultivated is algae, The input receiving unit receives input of work information including the location of the source material, the destination material, the number of materials to be moved, and the number of times the work is to be performed, corresponding to the process unit of the algae material movement in the seedbed installation. The system for managing the development of a plant according to claim 1 or 2.

17. The object to be cultivated is algae, The input receiving unit receives input of work information including the number of algae-attached materials to be put into the tank for each step of tank-attaching in seedbed installation, and the number of algae-attached materials landed during harvesting; The information presentation unit presents the yield status of the cultivation object based on the ratio between the number of attached materials included in the work information and the number of attached materials landed at the time of harvesting. The breeding management system according to claim 9 .

18. The object to be cultivated is algae, the input receiving unit receives input of performance information including harvest volume and input of work information including the number of attached materials landed during harvesting, The information presentation unit presents the harvest amount per unit number of landed adhesive material as a yield status. The breeding management system according to claim 9 .

19. The object to be cultivated is algae, the input receiving unit receives input of work information including the number of algae adhesion materials used for each process unit; The information presentation unit presents the arrangement elements corresponding to each process unit that presents the number of adhesive materials used, arranged in chronological order of the process units. The breeding management system according to claim 9 .

20. The information presentation unit presents the layout elements in different forms for each type of process unit. The development management system according to claim 19.

21. The object to be cultivated is algae, the input receiving unit is capable of receiving input of at least one of additional information of the location designated on the map, name of the location, water depth, bottom quality, amount of rocks, amount of aquatic plants, and amount of fish; The information registration unit stores location information including the position where the input receiving unit received the input and additional information in a storage unit. The system for managing the development of a plant according to claim 1 or 2.

22. A training management method in a training management system including a user terminal and a training management device, an input receiving step in which an input receiving unit in the user terminal receives input of work information indicating work content for each process in a unit growing period from the start of growing the growing object to harvesting; an information registration step in which an information registration unit acquires the work information inputted and accepted by the input acceptance step, and stores the acquired work information in a storage unit; A development management method comprising:

Images