Failure managing system

Abstract

To provide a failure managing system that facilitates the management of an occurrence status of a failure.SOLUTION: According to an aspect of the present invention, there is provided a failure managing system. This failure managing system includes a processor. The processor is configured to execute a predicting step, a first accepting step, and a recording step. In the predicting step, a prediction value that is the possibility of a failure occurring on a plant life is transmitted to a first user terminal. In the first accepting step, input of an occurrence value representing the presence or absence of the occurrence of a failure having the prediction value transmitted is accepted from the first user terminal. In the recording step, the occurrence value is recorded together with the kind of the plant life associated with the prediction value, a growth site associated with the user ID of the first user terminal, and the input date and time of the occurrence value.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a fault management system. [Background technology]

[0002] As disclosed in the following documents, a device that predicts damage (diseases, pests, and physiological damage) that will occur in plants (crops) using a learning model is known. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-93957 Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned device has a function for the user to input whether or not a predicted problem will occur, but the user must register the type and habitat of the plant where the problem occurred.

[0005] In view of the above circumstances, the present invention provides a fault management system that can easily manage the occurrence status of faults. [Means for solving the problem]

[0006] According to one aspect of the present invention, there is provided a fault management system. The fault management system includes a processor. The processor is configured to execute a forecasting step, a first receiving step, and a recording step. In the forecasting step, a possibility of a fault occurring in a plant is transmitted to a first user terminal as a forecast value. In the first receiving step, an input of an occurrence value indicating whether or not the fault for which the forecast value was transmitted has occurred is received from the first user terminal. In the recording step, the occurrence value is recorded together with the type of plant linked to the forecast value, the habitat linked to the user ID of the first user terminal, and the input date and time of the occurrence value.

[0007] According to this embodiment, the occurrence or non-occurrence of a fault can be easily registered together with the type of plant, its habitat, and the date and time of occurrence by inputting a response to the forecast value transmitted to the first user terminal, which makes it easy to manage the occurrence of faults. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a configuration diagram illustrating a fault management system 1. [Diagram 2] 2 is a block diagram showing a hardware configuration of an information processing device 2. FIG. [Diagram 3] 2 is a block diagram showing the hardware configuration of a first user terminal 3 and a second user terminal 4. FIG. [Figure 4] 2 is a block diagram showing functions realized by an information processing device 2 (processor 23). FIG. [Diagram 5] FIG. 2 is a diagram showing an example of a disease forecast screen BD1 displayed on a first user terminal 3. [Figure 6] FIG. 2 is a diagram showing an example of a pest forecast screen BD2 displayed on the first user terminal 3. [Figure 7] 13A and 13B are diagrams showing an example of changes in an occurrence input button OB and a countermeasure input button CB. [Figure 8] FIG. 2 is a diagram showing an example of a pesticide input screen PR displayed on a first user terminal 3. [Figure 9] 13 is an example of a history screen HD displayed on the first user terminal 3. [Figure 10] 13 is an example of a map screen MD displayed on the first user terminal 3. [Figure 11] 1 is an activity diagram showing a flow of information processing (recording processing of a fault occurrence) executed by the fault management system 1. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

[0012] In addition, a circuit in the broad sense is a circuit realized by at least appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

[0013] 1. Hardware Configuration This section describes the hardware configuration.

[0014] <Fault Management System 1> 1 is a configuration diagram showing a fault management system 1. The fault management system 1 provides a service to multiple users for forecasting faults that occur in plants (mainly agricultural crops) and managing the fault occurrence status.

[0015] The fault management system 1 includes an information processing device 2, a first user terminal 3, and a second user terminal 4. The information processing device 2, the first user terminal 3, and the second user terminal 4 are configured to be able to communicate with each other via a telecommunication line. In one embodiment, the fault management system 1 is made up of one or more devices or components. For example, if the fault management system 1 is made up of only the information processing device 2, the fault management system 1 can be the information processing device 2. These components will be described below.

[0016] <Information processing device 2> 2 is a block diagram showing a hardware configuration of the information processing device 2. The information processing device 2 includes a communication bus 20, a communication unit 21, a storage unit 22, and a processor 23. The communication unit 21, the storage unit 22, and the processor 23 are electrically connected via the communication bus 20 inside the information processing device 2.

[0017] <Communications Division 21> The communication unit 21 is preferably a wired communication means such as USB, IEEE1394, Thunderbolt (registered trademark), wired LAN network communication, etc., but may also include wireless LAN network communication, mobile communication such as 3G / LTE / 5G, BLUETOOTH (registered trademark) communication, etc. as necessary. In other words, it is more preferable to implement it as a collection of multiple communication means. In other words, the information processing device 2 may communicate various information from the outside via the communication unit 21 and the network.

[0018] <Storage section 22> The storage unit 22 stores various information defined by the above description. This can be implemented, for example, as a storage device such as a solid state drive (SSD) that stores various programs and the like related to the information processing device 2 executed by the processor 23, or as a memory such as a random access memory (RAM) that stores temporarily required information (arguments, arrays, etc.) related to the program calculations. The storage unit 22 stores various programs, variables, etc. related to the information processing device 2 executed by the processor 23.

[0019] <Processor 23> The processor 23 processes and controls the overall operations related to the information processing device 2. The processor 23 is, for example, a central processing unit (CPU). The processor 23 realizes various functions related to the information processing device 2 by reading out a predetermined program stored in the storage unit 22. That is, information processing by software stored in the storage unit 22 can be specifically realized by the processor 23, which is an example of hardware, and executed as each functional unit included in the processor 23. These will be described in more detail in the next section. The processor 23 is not limited to being single, and may be implemented with multiple processors 23 for each function. Also, a combination of these may be used.

[0020] <First user terminal 3> Fig. 3 is a block diagram showing the hardware configuration of the first user terminal 3 and the second user terminal 4. As shown in Fig. 3A, the first user terminal 3 includes a communication bus 30, a communication unit 31, a storage unit 32, a processor 33, a display unit 34, and an input unit 35. The communication unit 31, the storage unit 32, the processor 33, the display unit 34, and the input unit 35 are electrically connected via the communication bus 30 inside the first user terminal 3. The description of the communication unit 31, the storage unit 32, and the processor 33 will be omitted because they are similar to the description of each unit in the information processing device 2.

[0021] <Display section 34> The display unit 34 displays a screen of a graphical user interface (GUI) that can be operated by the user. The display unit 34 may be included in the housing of the first user terminal 3, or may be attached externally. Specifically, the display unit 34 may be implemented as a display device such as a CRT display, a liquid crystal display, an organic EL display, or a plasma display. It is preferable that these display devices are implemented by selectively using them according to the type of the first user terminal 3.

[0022] <Input section 35> The input unit 35 accepts an operation input made by a user. The operation input is transferred as a command signal to the processor 33 via the communication bus 30. The processor 33 may execute a predetermined control or calculation based on the transferred command signal as necessary. The input unit 35 may be included in the housing of the first user terminal 3, or may be externally attached. For example, the input unit 35 may be implemented as a touch panel integrated with the display unit 34. When the input unit 35 is implemented as a touch panel, the user can input a tap operation, a swipe operation, or the like to the input unit 35. As the input unit 35, a switch button, a mouse, a QWERTY keyboard, or the like can be adopted instead of a touch panel.

[0023] <Second user terminal 4> 3B, the second user terminal 4 includes a communication bus 40, a communication unit 41, a storage unit 42, a processor 43, a display unit 44, and an input unit 45. The communication unit 41, the storage unit 42, the processor 43, the display unit 44, and the input unit 45 are electrically connected via the communication bus 40 inside the second user terminal 4. Descriptions of the communication unit 41, the storage unit 42, the processor 43, the display unit 44, and the input unit 45 will be omitted because they are the same as the descriptions of the respective units in the first user terminal 3.

[0024] The information processing device 2 may be an on-premise type or a cloud type. As the information processing device 2 in the cloud type, the above-mentioned functions and processes may be provided in the form of, for example, SaaS (Software as a Service) or cloud computing.

[0025] 2. Functional configuration In this section, the functional configuration of the present embodiment will be described. Information processing by software stored in the storage unit 22 is specifically realized by the processor 23, which is an example of hardware, and can be executed as each functional unit included in the processor 23.

[0026] 4 is a block diagram showing functions realized by the information processing device 2 (processor 23). Specifically, the information processing device 2 (processor 23) includes a registration unit 231, a forecast unit 232, a first reception unit 233, a recording unit 234, a history output unit 235, a reminding unit 236, a second reception unit 237, and a sharing unit 238.

[0027] <Registration 231> The registration unit 231 registers first users (mainly farmers) who use the first user terminal 3. Specifically, the registration unit 231 registers user data including a user ID, the type of plant (crop) being cultivated, and the managed habitat (address of the field) in addition to personal information (name, address, contact information, etc.) of the first user. For a first user who has multiple habitats, the registration unit 231 registers the addresses of the multiple habitats.

[0028] The registration unit 231 also registers second users (mainly farm instructors) who use the second user terminal 4. Specifically, the registration unit 231 registers personal information (organization, person in charge, contact information, etc.) and user IDs of the second users.

[0029] <Forecast Department> The forecast unit 232 transmits the possibility of damage occurring to the plant as a forecast value to the first user terminal 3. The damage includes disease, pests, and physiological damage. The physiological damage includes deficiency of components such as magnesium and calcium, water shortage, etc. The forecast unit 232 causes the first user terminal 3 to display a damage occurrence forecast including the forecast value.

[0030] The forecasting unit 232 predicts the possibility of occurrence of a problem for a "type of plant" (i.e., a forecast value) for each "type of problem." The "type of plant" is, for example, a variety such as strawberry, radish, onion, broccoli, cabbage, etc. Furthermore, the "type of plant" may be subdivided by subcategories such as a variety of crop such as onion, such as "Sonic" or "Neo Earth," or a harvest date such as "early" or "mid-season." The "type of problem" is, for example, a disease name such as black sooty mold or black rot, a pest name such as cutworm or aphid, or a physiological disease phenomenon name such as magnesium deficiency or water shortage.

[0031] The forecast unit 232 predicts the possibility of a failure using a learning model (artificial intelligence) that has undergone machine learning in advance. Specifically, the forecast unit 232 inputs the type of plant to be predicted, the region, and the date to the learning model, and causes the learning model to output at least one failure that may occur and the probability (forecast value) of occurrence of each of the at least one failure.

[0032] Specifically, the forecast unit 232 inputs the type and habitat of the plant included in the user data of the first user who is using the first user terminal 3 that transmits the forecast value, and the date on which the forecast value is to be issued, into the learning model. The forecast unit 232 also transmits the forecast value corresponding to the type of plant and the type of trouble output from the learning model to the first user terminal 3. In other words, the forecast unit 232 transmits the possibility of each of multiple types of trouble that may occur to the plant as a forecast value to the first user terminal 3.

[0033] The learning model used by the forecasting unit 232 is constructed by machine learning using, as training data, records associating the type of plant where a failure occurred in the past, the type of failure that occurred, the area where the plant grew, and the date of failure occurrence. Specific algorithms for machine learning include the nearest neighbor method, the naive Bayes method, a decision tree, a support vector machine, deep learning using a neural network, a regression model, and the like. This learning model can perform additional learning using data received from the first user terminal 3.

[0034] 5 is a diagram showing an example of a disease forecast screen BD1 displayed on the first user terminal 3. The forecast screen BD1 is created based on forecast values ​​transmitted from the forecast unit 232. The forecast screen BD1 includes a selection area SP for selecting a type of plant, and a disease display area DP1 for displaying diseases that may occur in the selected plant.

[0035] A plurality of plant icons are displayed in the selection area SP. The type of plant for which forecast values ​​are to be displayed is selected by pressing an icon through a pressing operation using an input device (e.g., a mouse, a trackpad, a touch panel, etc.) on the first user terminal 3. A selection mark SM is added to the icon of the selected plant.

[0036] Depending on the type of plant selected in the selection area SP, multiple disease display areas DP1 are displayed on the forecast screen BD1. Each disease display area DP1 includes a symptom photo CP, a disease name DT, a forecast value FV, a variation value CV, and an occurrence input button OB.

[0037] The forecast value FV is a probability indicating the possibility of occurrence of the disease displayed as the disease name DT, predicted by the forecast unit 232. In the disease display area DP1, a graph indicating the magnitude of the forecast value FV and a forecast level linked to the forecast value FV are displayed above the forecast value FV. The forecast level is displayed in stages, such as "watch", "caution", and "alert", according to the magnitude of the forecast value FV.

[0038] The variation value CV indicates the increase or decrease of the current (i.e., displayed in the disease display area DP1) forecast value FV relative to the past forecast value FV on a specific date (e.g., the day before or the day the forecast value FV was last displayed).

[0039] The occurrence input button OB is a button that the first user presses when a disorder (disease) displayed in the disease display area DP1 occurs in a habitat managed by the first user (i.e., the habitat for which a forecast value has been issued).

[0040] 6 is a diagram showing an example of a pest forecast screen BD2 displayed on the first user terminal 3. The forecast screen BD2 is created based on forecast values ​​transmitted from the forecast unit 232. The forecast screen BD2 includes a selection area SP for selecting a type of plant, and a pest display area DP2 for displaying pests that may occur in the selected plant.

[0041] The selection area SP is the same as the forecast screen BD1 in FIG. 5. Depending on the type of plant selected in the selection area SP, a plurality of pest display areas DP2 are displayed on the forecast screen BD2. Each pest display area DP2 includes a pest name PT, a photo of symptoms CP, a forecast value FV, a variation value CV, an occurrence input button OB, and a countermeasure input button CB. The forecast value FV, the variation value CV, and the occurrence input button OB are the same as those on the forecast screen BD1 in FIG. 5. The countermeasure input button CB is a button that the first user presses when taking countermeasures against a problem.

[0042] Note that a disease display area DP1 and a pest display area DP2 may be displayed in one forecast screen. Also, an area for displaying forecast values ​​of physiological disorders may be displayed on the forecast screen.

[0043] In addition to the forecast value, the forecast unit 232 may transmit information on the occurrence of a fault in a nearby habitat to the first user terminal 3. The fault occurrence information includes the type of fault occurring in the nearby habitat, the number of faults, the pesticide spraying status (type of pesticide, spraying date, etc.), and the like.

[0044] Furthermore, the forecast unit 232 may present measures to deal with the problem in addition to the forecast value. The measures include, for example, pesticides that are effective against the problem, fertilizers that contain the missing components, and the like.

[0045] <First Reception Section 233> The first reception unit 233 receives an input of an occurrence value indicating whether or not a fault for which a forecast value has been transmitted has occurred from the first user terminal 3. Specifically, in response to pressing of the occurrence input button OB in the disease display area DP1 or the pest display area DP2, the first reception unit 233 receives a value (code) indicating that "the corresponding fault has occurred" from the first user terminal 3.

[0046] When the occurrence input button OB is pressed, the first reception unit 233 may subsequently display a confirmation pop-up screen to receive the confirmation input (pressing the button), or may perform registration (receive the code) without displaying the pop-up screen. When the first reception unit 233 does not display the pop-up screen, it may display a message such as "Cabbage disease A has been registered at the current location" on the first user terminal 3 for a certain period of time (e.g., 3 seconds).

[0047] That is, the first reception unit 233 accepts input of the occurrence value by a single action (one button press) or a double action (two button presses) from a state in which the forecast value is displayed on the first user terminal 3 (a state in which the disease display area DP1 or the pest display area DP2 is displayed).

[0048] 7 is a diagram showing an example of changes in the occurrence input button OB and the countermeasure input button CB. When the occurrence input button OB is pressed, as shown in FIG. 7, the input reception by the first reception unit 233 is emphasized by changing the color, changing the size, adding an icon, etc.

[0049] The occurrence value may be selected from a range of options with degrees (for example, "large occurrence amount," "small occurrence amount," "no occurrence," etc.). The first receiving unit 233 may also receive an arbitrary numerical value (for example, a numerical value proportional to the degree of occurrence) input by the first user as the occurrence value.

[0050] The first reception unit 233 further receives input of the type and spraying date of the pesticide sprayed in response to the failure for which the forecast value was transmitted from the first user terminal 3. Specifically, the first reception unit 233 receives from the first user terminal 3 the type and spraying date of the pesticide input by the first user.

[0051] Fig. 8 is a diagram showing an example of a pesticide input screen PR displayed on the first user terminal 3. When the countermeasure input button CB shown in Fig. 6 is pressed, the pesticide input screen PR shown in Fig. 8A is displayed on the first user terminal 3. The pesticide input screen PR includes a habitat input field FI, a pesticide input field PI, a spraying date input field DI, a send button B1, and a cancel button B2.

[0052] The habitat input field FI accepts input of the habitat (field) where the pesticide was sprayed. In the initial state, the address of the managed habitat (i.e., the habitat where the forecast value was received) registered in the user data of the first user is input in the habitat input field FI. When the pesticide is sprayed in a habitat different from the registered habitat, the first user inputs the address of the habitat where the pesticide was sprayed by manual input or by linking with an external map application. The first reception unit 233 may display (i.e., input in advance) in the habitat input field FI the managed habitat registered in the user data that is closest to the location information transmitted from the first user terminal 3.

[0053] The pesticide input field PI accepts input of the type (product name) of the sprayed pesticide. The pesticide input field PI may be a pull-down menu for selecting and inputting from a plurality of pesticides registered in advance, or may be configured to open an input window PIW for accepting input of the name of the pesticide, as shown in Fig. 8B. When accepting input of the name, it is preferable that the first receiving unit 233 displays candidates for pesticides during input, as shown in Fig. 8B.

[0054] The first receiving unit 233 may display effective pesticide candidates according to the type of disorder and the type of plant. The pesticide candidates are extracted, for example, from a list of pesticides applicable by law to the type of disorder (disease or type of pest) and the type of plant.

[0055] The spraying date input field DI accepts input of the date on which the pesticide was sprayed. When the send button B1 is pressed, the input contents of each field are sent to the first reception unit 233. When the cancel button B2 is pressed, the pesticide input screen PR disappears. The first reception unit 233 may display the date of input as the spraying date in the spraying date input field DI (i.e., may input it in advance).

[0056] When the send button B1 is pressed and the pesticide spraying area, the type of pesticide, and the spraying date are received by the first receiving unit 233, a display PD of the type of pesticide and the spraying date is added to the pest display area DP2 as shown in Fig. 7. Also, the reception of input by the first receiving unit 233 is emphasized by changing the color of the countermeasure input button CB, changing the size, adding an icon, etc. Although the countermeasure input button CB is not displayed in the disease display area DP1 in Fig. 5, the countermeasure input button CB may be provided in the disease display area DP1.

[0057] <Recording Section 234> The recording unit 234 records the occurrence value together with the type of plant linked to the forecast value, the habitat linked to the user ID of the first user terminal 3, and the input date and time of the occurrence value. Specifically, the recording unit 234 records a record in which the type of plant, the type of disturbance, the habitat, the occurrence date and time, and the occurrence value are linked to one another. This record can be referenced from the first user terminal 3 or the second user terminal 4. Furthermore, by using this record as teacher data for a learning model used by the forecasting unit 232, the prediction accuracy of the forecasting unit 232 can be improved.

[0058] The recording unit 234 may record the habitat based on the location information transmitted from the first user terminal 3. This allows the second user to mainly register the occurrence or non-occurrence of a disturbance in a habitat other than the habitat registered in the user data. Also, the occurrence or non-occurrence of a disturbance can be recorded without registering the habitat in the user data. Note that the location information is not limited to a combination of latitude and longitude acquired by GPS, for example, and may be a representative value selected from map information (for example, the address of a farmland registered in a farmland map).

[0059] The recording unit 234 records, as the habitat included in the record, the one closest to the location information transmitted from the first user terminal 3 among the managed habitats registered in the user data by the registration unit 231. This can save the first user the trouble of inputting the habitat when recording the occurrence of a fault.

[0060] Furthermore, the recording unit 234 may record location information transmitted from the first user terminal 3 a certain number of times (e.g., three times) or more as the habitat. This can save the first user the trouble of inputting habitats other than those registered in the user data each time. Note that the "location information transmitted a certain number of times or more" does not necessarily have to be all identical location information, and also includes location information transmitted a certain number of times or more with a deviation on the order of several meters. Also, for example, if the same farmland is entered multiple times on a farmland map, the address of this farmland becomes the "location information transmitted a certain number of times or more."

[0061] Furthermore, the recording unit 234 records the type of pesticide and the date of application in association with the obstacle. Specifically, the recording unit 234 records a record in which the type of plant, the type of obstacle, the habitat, the type of pesticide, and the date of application are associated with each other. This makes it possible to collect and record pesticide application status data without imposing an operational burden on the first user.

[0062] Furthermore, the recording unit 234 records, among the multiple types of failures, failures for which pesticides are effective, in association with the type and spraying date of the pesticide. Specifically, when the type of pesticide input from the first user terminal 3 for the first failure is also effective for the second failure transmitted to the same first user terminal 3, the recording unit 234 records a first record in which the type of the first plant that is the target of the first failure, the type of the first failure, the habitat of the first plant, the type of pesticide, and the spraying date are linked to each other, and a first record in which the type of the second plant that is the target of the second failure, the type of the second failure, the habitat of the second plant, the type of pesticide, and the spraying date are linked to each other. The type and spraying date of the pesticide in the first record are common to the type and spraying date of the pesticide in the second record. As a result, the input of the spraying data of one pesticide records the spraying data of the pesticide for multiple failures, greatly reducing the effort of the first user to input.

[0063] For example, in Fig. 6, when spraying of pesticide A is input from the countermeasure input button CB in the pest display area DP2 for "cutworm," if this pesticide A is also effective against "aphids," the spraying of pesticide A is linked and recorded to both "cutworms" and "aphids." In addition to the countermeasure input button CB in the pest display area DP2 for "cutworms," ​​the countermeasure input button CB in the pest display area DP2 for "aphids" also changes to display "countermeasure completed" as shown in Fig. 7. The recording unit 234 refers to a database (table) prepared in advance to determine the disorders for which each pesticide is effective.

[0064] The first reception unit 233 may use the database to estimate the type of plant grown in the growing area from the type of pesticide input. This can save the first user from having to manually input and register a new plant when the first user starts growing the plant.

[0065] <History output section 235> The history output unit 235 outputs the history of the recorded occurrence value to the first user terminal 3. Specifically, the history output unit 235 causes the first user terminal 3 to display a list of occurrences of faults for each type of fault. This makes it easy for the first user to understand the history of fault occurrences in the first user's habitat. In addition, by displaying the history on the second user terminal 4 that has been given permission from the first user, it also becomes easy for the second user to understand the history of fault occurrences in the habitat that he or she is instructing.

[0066] FIG. 9 is an example of a history screen HD displayed on the first user terminal 3. The history screen HD displays, for each type of fault, the name BT of the fault that occurred in the habitat managed by the first user, the type of plant ST, the date of occurrence CT, and the location of occurrence LT. Note that, although only one fault is illustrated in FIG. 9, if multiple faults occur in the habitat managed by the first user, multiple faults are displayed. Note that the nickname (label) of the habitat is displayed at the location of occurrence LT. The nickname of the habitat can be arbitrarily set by the first user.

[0067] The history output unit 235 may display the history on a map or a calendar. Furthermore, the history output unit 235 may output history narrowed down by type of obstacle, type of plant, habitat, or the like.

[0068] Furthermore, the history output unit 235 outputs the fault occurrence history including other users to the first user terminal 3. FIG. 10 is an example of a map screen MD displayed on the first user terminal 3. The map screen MD displays a map, fault information HI, and a fault occurrence icon NI. The fault information HI displays the habitat of the first user, the type of fault, and the type of plant. The fault information HI is displayed when the fault occurrence icon NI is pressed. The fault occurrence icon NI is displayed superimposed on the habitat where the fault occurred (including habitats managed by users other than the first user). The fault occurrence icon NI indicates the number of faults that have occurred.

[0069] By narrowing down the types of faults and the types of plants in the first user terminal 3, any fault occurrence history (fault occurrence icon NI) is displayed on the map screen MD. Furthermore, the history output unit 235 may display only the fault occurrence icon NI corresponding to the faults that occurred during a period specified by the first user terminal 3.

[0070] In addition, the map screen MD may display the entire map divided into 1 km meshes, for example, with each section color-coded according to the presence or absence of a fault or the number of faults. This protects the privacy of users (farmers).

[0071] <Remind Section 236> The reminder unit 236 transmits a pesticide spray reminder to the first user terminal 3 when a predetermined number of days have passed since the date of pesticide spraying. The "predetermined number of days" is predefined for each type of pesticide. The "remind" includes, for example, the target growing area, the type of pesticide, and the scheduled spraying date (or the number of days since the pesticide was sprayed). This prevents forgetting to spray the pesticide and simplifies the management of the pesticide spraying schedule by the first user. The content of the reminder is, for example, "XX days have passed since the spraying of pesticide A." Note that the first user sprays a different pesticide from the one sprayed last time to avoid a reduction in the effect of the pesticide due to resistance. The first user can check the pesticide sprayed last time by the above-mentioned reminder.

[0072] <Second Reception Section 237> The second reception unit 237 receives sharing permission for the second user terminal 4 from the first user terminal 3. Specifically, the second reception unit 237 receives input of the user ID of the second user who is permitted to share the history of failure occurrences, etc., from the first user terminal 3. The first user performs permission setting input on the first user terminal 3 in response to the search result of the user ID or a permission request from the second user.

[0073] <Shared section 238> The sharing unit 238 transmits the recorded occurrence value to the second user terminal 4 that has been granted permission to share. Specifically, upon receiving a sharing request from the second user terminal 4, the sharing unit 238 causes the second user terminal 4 to display data such as the occurrence value transmitted and recorded from the first user terminal 3 (i.e., a record of the occurrence of a fault). This allows the second user who provides guidance to the first user to appropriately grasp the history of faults, thereby improving the effectiveness of guidance by the second user.

[0074] Furthermore, the sharing unit 238 may cause the generated value to be displayed on the second user terminal 4 by push notification. In this case, the second accepting unit 237 accepts permission for the push notification to the second user terminal 4 from the first user terminal 3 as “sharing permission”.

[0075] Furthermore, the sharing unit 238 notifies the second user terminal 4 of the input of the occurrence value indicating the occurrence of a fault from the first user terminal 3. Specifically, when the first receiving unit 233 receives the input of "Fault has occurred" from the first user terminal 3, the sharing unit 238 transmits a message to the second user terminal 4 indicating that a fault has occurred at the first user. At this time, the type of plant, the type of fault, the habitat, etc. are also transmitted. This enables the second user to give immediate guidance on how to respond.

[0076] 3. Fault management method This section describes a failure management method for the information processing device 2. This failure management method is executed by a computer, with each unit of the information processing device 2 acting as each step.

[0077] Specifically, this fault management method includes a forecasting step, a first receiving step, and a recording step. In the forecasting step, a possibility of a fault occurring in the plant is transmitted to the first user terminal 3 as a forecast value. In the first receiving step, an input of an occurrence value indicating whether or not a fault has occurred is received from the first user terminal 3 to which the forecast value has been transmitted. In the recording step, the occurrence value is recorded together with the type of plant linked to the forecast value, the habitat linked to the user ID of the first user terminal 3, and the input date and time of the occurrence value.

[0078] <Record of failure occurrence> 11 is an activity diagram showing the flow of information processing (recording processing of a fault occurrence) executed by the fault management system 1. The information processing will be described below along with each activity in this activity diagram.

[0079] The fault occurrence recording process starts with the processor 23 of the information processing device 2 predicting a forecast value (activity A110). At this time, the processor 23 stores the predicted forecast value in the storage unit 22. The processor 23 transmits the predicted forecast value to the first user terminal 3 via the communication unit 21 (activity A120). The information processing device 2 transmits at least one required forecast value to each of the multiple first user terminals 3 based on the user data of each first user terminal 3.

[0080] Next, the processor 33 of the first user terminal 3 receives the forecast value from the information processing device 2 via the communication unit 31 (activity A130). After receiving the forecast value, the processor 33 causes the display unit 34 to display the forecast value, for example, as in the forecast screen BD1 or BD2 of FIG. 5 or FIG. 6 (activity A140). After displaying the forecast value, the processor 33 accepts an input of the presence or absence of occurrence of the fault for which the forecast value was transmitted (occurrence value) from the input unit 35 (activity A150). After inputting the occurrence value, the processor 33 transmits the input occurrence value to the information processing device 2 via the communication unit 31 together with the type of fault, the type of plant, and the habitat of the target (activity A160).

[0081] Next, the processor 23 of the information processing device 2 receives data such as the occurrence value from the first user terminal 3 via the communication unit 21 (activity A170). After receiving the data, the processor 23 stores a record including the occurrence value, the type of disturbance, the type of plant, the habitat, and the input date and time of the occurrence value in the storage unit 22 (activity A180).

[0082] The record stored in the storage unit 22 is transmitted from the communication unit 21 to the first user terminal 3 or the second user terminal 4 in response to a request from the first user terminal 3 or the second user terminal 4.

[0083] 4. Effect The operation of this embodiment can be summarized as follows: The occurrence or non-occurrence of a fault can be easily registered together with the type of plant, its habitat, and the date and time of occurrence by inputting a response to the forecast value transmitted to the first user terminal 3. This makes it easy to manage the occurrence of faults.

[0084] In particular, the first user can register the above-mentioned information with one tap or two taps including a confirmation operation. Furthermore, since only the minimum necessary information is registered, communication costs can be reduced.

[0085] Although the embodiment of the present invention has been described above, the present invention is not limited to this, and can be modified as appropriate without departing from the technical concept of the invention.

[0086] 5.Other In the above embodiment, the information processing device 2 performs various storage and control, but multiple external devices may be used instead of the information processing device 2. That is, various information and programs may be distributed and stored in multiple external devices using block chain technology or the like.

[0087] The aspect of the present embodiment is not limited to the fault management system 1, and may be a fault management method or a program. The fault management method includes the steps of the fault management system 1. The program causes a computer to function as the fault management system 1.

[0088] The forecast unit 232 does not necessarily need to use a learning model. In other words, the forecast unit 232 may predict a forecast value using an algorithm constructed by a statistical method other than machine learning.

[0089] It may be provided in any of the following ways:

[0090] (1) A fault management system comprising a processor, the processor being configured to execute a forecasting step, a first receiving step, and a recording step, wherein in the forecasting step, a possibility of a fault occurring in a plant is transmitted to a first user terminal as a forecast value, in the first receiving step, an input of an occurrence value indicating whether or not the fault for which the forecast value was transmitted has occurred is received from the first user terminal, and in the recording step, the occurrence value is recorded together with a type of plant linked to the forecast value, a habitat linked to a user ID of the first user terminal, and a date and time when the occurrence value was input.

[0091] (2) In the fault management system described in (1) above, in the first reception step, the input of the occurring value is received by a single action or a double action from a state in which the forecast value is displayed on the first user terminal.

[0092] (3) In the fault management system according to (1) or (2) above, in the recording step, the habitat is recorded based on location information transmitted from the first user terminal.

[0093] (4) In the fault management system described in (3) above, the processor is further configured to execute a registration step, in which user data including the user ID and a managed habitat is registered in the registration step, and in the recording step, the managed habitat registered in the user data that is closest to the location information is recorded as the habitat.

[0094] (5) In the fault management system described in (3) above, in the recording step, the location information transmitted from the first user terminal a certain number of times or more is recorded as the habitat.

[0095] (6) In the fault management system described in any one of (1) to (5) above, the processor is configured to further execute a history output step, in which the history output step outputs the history of the recorded occurrence value to the first user terminal.

[0096] (7) A fault management system according to any one of (1) to (6) above, wherein in the first reception step, input of the type and date of spraying of the pesticide sprayed in response to the fault for which the forecast value was transmitted is received from the first user terminal, and in the recording step, the type and date of spraying of the pesticide are recorded in association with the fault.

[0097] (8) A fault management system as described in (7) above, wherein in the forecasting step, the probability of each of a plurality of types of faults occurring in plants being generated is transmitted to the first user terminal as the forecast value, and in the recording step, among the plurality of types of faults, faults for which the pesticide is effective are recorded in association with the type of pesticide and the date of spraying.

[0098] (9) In the fault management system described in (7) or (8) above, the processor is configured to further execute a reminder step, in which a reminder for pesticide spraying is sent to the first user terminal when a predetermined number of days have passed since the date of spraying of the pesticide.

[0099] (10) In the fault management system described in any one of (1) to (9) above, the processor is further configured to execute a second reception step and a sharing step, in which the second reception step receives sharing permission for a second user terminal from the first user terminal, and in the sharing step, transmits the recorded generation value to the second user terminal that has received the sharing permission.

[0100] (11) In the fault management system described above in (10), in the sharing step, the input of the occurrence value indicating the occurrence of the fault from the first user terminal is notified to the second user terminal. Of course, this is not the case.

[0101] Finally, although various embodiments according to the present disclosure have been described, these are presented as examples and are not intended to limit the scope of the invention. The novel embodiment can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The embodiments and their modifications are included within the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0102] 1: Fault management system 2: Information processing equipment 3: First user terminal 4: Second user terminal 20: Communication bus 21: Communications Department 22: Storage section 23: Processor 30: Communication bus 31: Communications Department 32: Storage section 33: Processor 34:Display section 35: Input section 40: Communication bus 41: Communications Department 42: Storage section 43: Processor 44: Display section 45: Input section 231: Registration Department 232: Forecast Department 233: First Reception Section 234: Recording Department 235: History output section 236: Remind Department 237: Second Reception Section 238: Common Department

Claims

1. 1. A fault management system, comprising: A processor is provided. The processor is configured to execute a forecasting step, a first receiving step, and a recording step; In the forecasting step, a possibility of damage occurring to the plant is transmitted to a first user terminal as a forecast value; In the first reception step, an input of an occurrence value indicating whether or not the failure has occurred and for which the forecast value has been transmitted is received from the first user terminal; A fault management system in which, in the recording step, the occurrence value is recorded together with the type of plant linked to the forecast value, the habitat linked to the user ID of the first user terminal, and the input date and time of the occurrence value.

2. 2. The fault management system according to claim 1, A fault management system, wherein the first receiving step receives input of the occurrence value by a single action or a double action from a state in which the forecast value is displayed on the first user terminal.

3. 2. The fault management system according to claim 1, In the recording step, the habitat is recorded based on location information transmitted from the first user terminal.

4. 4. The fault management system according to claim 3, The processor is further configured to perform a registration step; In the registration step, user data including the user ID and a managed habitat is registered, A fault management system, wherein in the recording step, a managed habitat that is closest to the location information among the managed habitats registered in the user data is recorded as the habitat.

5. 4. The fault management system according to claim 3, In the recording step, the location information transmitted from the first user terminal a certain number of times or more is recorded as the habitat.

6. 2. The fault management system according to claim 1, The processor is further configured to perform a history output step; A fault management system, wherein the history output step outputs the history of the recorded occurrence value to the first user terminal.

7. 2. The fault management system according to claim 1, In the first reception step, an input of a type of pesticide sprayed for the fault for which the forecast value was transmitted and a spraying date is received from the first user terminal, In the recording step, the type of pesticide and the date of application are recorded in association with the problem.

8. 8. The fault management system according to claim 7, In the forecasting step, a probability of each of a plurality of types of damage occurring to a plant is transmitted to the first user terminal as the forecast value; A problem management system in which, in the recording step, among the multiple types of problems, problems for which the pesticide is effective are recorded in association with the type of pesticide and the date of application.

9. 8. The fault management system according to claim 7, The processor is further configured to perform a reminding step; In the reminding step, a reminder for spraying the pesticide is sent to the first user terminal when a predetermined number of days have passed since the date of spraying the pesticide.

10. 2. The fault management system according to claim 1, The processor is configured to further perform a second receiving step and a sharing step; In the second receiving step, a sharing permission for a second user terminal is received from the first user terminal; In the sharing step, the recorded occurrence value is transmitted to the second user terminal that has been granted the sharing permission.

11. 11. The fault management system according to claim 10, The fault management system, in the sharing step, notifies the second user terminal of the input of the occurrence value indicating the occurrence of the fault from the first user terminal.

Images