Agricultural land issue management system, and method thereof
The agricultural land issue management system addresses the challenge of managing facility failures and pests by using a terminal-server system for workers to report issues, which are then classified and prioritized by managers, ensuring efficient and reliable issue resolution and minimizing economic losses.
Patent Information
- Application Number
- PCT/KR2024/006193
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-05-02
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-14
AI Technical Summary
Agricultural land managers face challenges in quickly and reliably managing issues such as facility failures and pests across large farms or greenhouses, leading to potential economic losses due to inefficient labor distribution and inaccurate issue reporting by non-specialized workers.
A system comprising a worker terminal and a manager terminal connected to a server, allowing workers to easily generate and transmit issue information, which is then classified and managed by managers for prioritization and resolution, with features like urgent indicators and status pages to ensure timely action.
This system enables reliable and efficient issue management across agricultural land, minimizing damage and optimizing labor by providing clear, prioritized information for managers, thus maximizing economic benefits.
Smart Images

Figure KR2024006193_14112024_PF_FP_ABST
Abstract
Description
Agricultural land issue management system and method thereof
[0001] The present invention relates to a system and method for managing issues occurring in farmland, and more specifically, to a farmland issue management system and method in which a worker terminal generates issue occurrence information regarding issues occurring in farmland, and an administrator terminal determines whether to register the issue occurrence information.
[0002] When growing crops in large farms or greenhouses, issues such as facility failures or pests must be quickly identified and appropriately addressed. Failure to respond quickly can result in damage to the entire crop, resulting in significant economic losses.
[0003] To prevent this, managers of agricultural lands such as farms or greenhouses have been going around all areas of the farmland to manage issues such as facility breakdowns or pests. However, the larger the area of agricultural land, the more managers are needed, which results in excessive labor costs. Or, for practical reasons, issues in agricultural lands are not properly managed, and when problems arise, they are resolved after the fact.
[0004] Meanwhile, workers who directly grow crops on large farms or in greenhouses outnumber managers and move around various areas of the farmland to perform assigned tasks.
[0005] Accordingly, there have been attempts to use the information obtained from workers for farmland management by providing programs that allow workers to walk around farmland and register issues such as facility failures or pests.
[0006] However, because workers without specialized knowledge about farms or greenhouses could not accurately determine issues such as facility breakdowns or pests, when managing farms or greenhouses based on the issues registered by workers, unreliable information about issues increased, and problems such as spraying pesticides in unnecessary locations or hiring repair personnel when the facilities were not broken actually occurred.
[0007] In this way, in order to maximize economic benefits in managing agricultural land, it was necessary to develop a system to manage issues within agricultural land with guaranteed reliability.
[0008] One object of the present invention is to provide a system and method for quickly and reliably managing issues in the entire agricultural land by allowing workers who move around various areas of agricultural land, such as farmland and greenhouses, to easily generate issue occurrence information on issues occurring in the agricultural land in order to perform work, and allowing managers with expertise in agricultural land management to easily decide whether to register issue occurrence information.
[0009] Another object of the present invention is to provide a system and method for providing an issue occurrence status page reflecting issue occurrence information to an administrator, in which unconfirmed issues are displayed separately and urgent issues are displayed with a separate indicator, thereby enabling the administrator to easily manage issues in farmland without missing any issues.
[0010] The problems to be solved by the present invention are not limited to the problems described above, and problems not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention pertains from this specification and the attached drawings.
[0011] According to one embodiment of the present invention, an issue management system including an administrator terminal, an operator terminal, and a server comprises: at least one operator terminal assigned to an operator who is guided to perform work within a greenhouse according to a set schedule; at least one administrator terminal assigned to an administrator who oversees the status of work within the greenhouse and the progress of work within the greenhouse; And a server that is communicatively connected to the worker terminal and the administrator terminal, and stores and manages information about the greenhouse; wherein the worker terminal transmits first issue occurrence information generated according to a first input of a user to the server, and the first issue occurrence information includes at least a type of issue, an occurrence location of the issue, a photo of the issue, and whether the issue is urgent, and the first input is acquired through an issue input interface provided on the worker terminal, and the server stores at least the first issue occurrence information received from the worker terminal, and classifies and stores the first issue occurrence information as an unconfirmed issue until an issue registration decision for the first issue occurrence information is received from the administrator terminal, and in response to a trigger received from the administrator terminal, provides one or more stored issue occurrence information to the administrator terminal, and the administrator terminal displays an issue occurrence status page in which the one or more issue occurrence information received is reflected, and the issue occurrence status page displays one or more issue items representing the one or more issue occurrence information, and the one or more issue items are displayed and classified according to the type, and the one or more issue items are classified and displayed as unconfirmed issues. An issue management system may be provided in which an issue item indicating issue occurrence information is displayed as an unconfirmed issue regardless of the above type, and an issue item indicating issue occurrence information including the above emergency is displayed together with an emergency indicator indicating the above emergency.
[0012] The solution to the problem of the present invention is not limited to the above-described solution, and solution means not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention pertains from this specification and the attached drawings.
[0013] According to the present invention, a worker who moves around various areas of farmland, such as farmland and greenhouses, to perform work can easily create issue occurrence information on issues occurring within the farmland, and a manager with expertise in farmland management can easily decide whether to register issue occurrence information, so that issues across the farmland can be managed quickly and reliably.
[0014] In addition, according to the present invention, an issue issuance status page reflecting issue occurrence information is provided to the administrator, and an issue occurrence status page is provided to the administrator in which unconfirmed issues are displayed separately and urgent issues are displayed with a separate indicator, so that the administrator can flexibly manage issues in farmland in order of priority while minimizing damage.
[0015] The effects of the present invention are not limited to the effects described above, and effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention pertains from this specification and the attached drawings.
[0016] Figure 1 is a drawing to explain the farming environment within farmland.
[0017] FIGS. 2 and 3 are diagrams of an issue management system according to one embodiment.
[0018] Figure 4 is a drawing showing the configuration of a worker terminal according to one embodiment.
[0019] FIG. 5 and FIG. 6 are diagrams showing an issue input page according to one embodiment.
[0020] Figure 7 is a diagram showing the configuration of an administrator terminal according to one embodiment.
[0021] FIG. 8, FIG. 9, FIG. 10, FIG. 11, FIG. 12, FIG. 13, and FIG. 14 are diagrams showing an issue status page according to one embodiment.
[0022] FIG. 15, FIG. 16, FIG. 17, FIG. 18, and FIG. 19 are diagrams showing issue detail pages according to one embodiment.
[0023] Figure 20 is a diagram showing the configuration of a server according to one embodiment.
[0024] Figures 21, 22, 23, 24, 25 and 26 are flowcharts illustrating an issue management method according to one embodiment.
[0025] The embodiments described in this specification are intended to clearly explain the idea of the present invention to a person having ordinary skill in the art to which the present invention pertains, and the present invention is not limited to the embodiments described in this specification, and the scope of the present invention should be interpreted to include modified or altered examples that do not depart from the idea of the present invention.
[0026] The terms used in this specification have been selected from widely used terms, as much as possible, considering their functions in the present invention. However, these terms may vary depending on the intentions of those skilled in the art, customs, or the emergence of new technologies. However, if a specific term is defined and used with an arbitrary meaning, the meaning of that term will be described separately. Therefore, the terms used in this specification should be interpreted based on their actual meaning and the overall content of this specification, rather than simply their names.
[0027] The drawings attached to this specification are intended to facilitate explanation of the present invention, and the shapes depicted in the drawings may be exaggerated as necessary to help understand the present invention, and therefore the present invention is not limited by the drawings.
[0028] If it is determined that a detailed description of the configuration or function of a known matter related to the present invention in this specification may obscure the gist of the present invention, a detailed description thereof may be omitted as necessary.
[0029] According to one embodiment of the present invention, an issue management system including an administrator terminal, an operator terminal, and a server comprises: at least one operator terminal assigned to an operator who is guided to perform work within a greenhouse according to a set schedule; at least one administrator terminal assigned to an administrator who oversees the status of work within the greenhouse and the progress of work within the greenhouse; And a server that is communicatively connected to the worker terminal and the administrator terminal, and stores and manages information about the greenhouse; wherein the worker terminal transmits first issue occurrence information generated according to a first input of a user to the server, and the first issue occurrence information includes at least a type of issue, an occurrence location of the issue, a photo of the issue, and whether the issue is urgent, and the first input is acquired through an issue input interface provided on the worker terminal, and the server stores at least the first issue occurrence information received from the worker terminal, and classifies and stores the first issue occurrence information as an unconfirmed issue until an issue registration decision for the first issue occurrence information is received from the administrator terminal, and in response to a trigger received from the administrator terminal, provides one or more stored issue occurrence information to the administrator terminal, and the administrator terminal displays an issue occurrence status page in which the one or more issue occurrence information received is reflected, and the issue occurrence status page displays one or more issue items representing the one or more issue occurrence information, and the one or more issue items are displayed and classified according to the type, and the one or more issue items are classified and displayed as unconfirmed issues. An issue management system may be provided in which an issue item indicating issue occurrence information is displayed as an unconfirmed issue regardless of the above type, and an issue item indicating issue occurrence information including the above emergency is displayed together with an emergency indicator indicating the above emergency.
[0030] The above administrator terminal may display an issue detail page for the first issue item when the first issue item is selected based on the user's second input, and the issue detail page may display the type, occurrence location, and photo corresponding to the selected first issue item.
[0031] When the first issue item is an issue item classified as an unconfirmed issue, an issue registration interface is further provided on the issue detail page, and when the administrator terminal obtains an issue registration decision for the first issue item through the issue registration interface, the issue registration decision is transmitted to the server, and the server can reclassify issue occurrence information classified as an unconfirmed issue corresponding to the first issue item into a registered issue.
[0032] When the first issue item is an issue item indicating issue occurrence information classified as the registered issue, an issue resolution interface is further provided on the issue detail page, and when an issue resolution decision for the first issue item is obtained through the issue resolution interface, the administrator terminal transmits the issue resolution decision to the server, and the server can reclassify the issue occurrence information classified as the registered issue corresponding to the first issue item as a resolved issue.
[0033] Issue items indicating issue occurrence information classified as resolved issues above may be displayed as resolved issues on the issue occurrence status page above, regardless of the type.
[0034] The above-described administrator terminal transmits second issue occurrence information generated according to a third input of a user to the server, the second issue occurrence information including at least a type of issue and an occurrence location of the issue, the third input being obtained through an issue input interface provided on the administrator terminal, and the server stores the second issue occurrence information received from the administrator terminal, but can classify and store the second issue occurrence information as a registered issue even if an issue registration decision for the second issue occurrence information is not received.
[0035] The above issue input interface may include an interface for selecting the location of occurrence of the issue, an interface for selecting the type of the issue, an interface for entering a photo related to the issue, an interface for selecting an emergency of the issue, and an interface for entering a description related to the issue.
[0036] The above occurrence location selection interface can be deactivated if there is location information corresponding to the QR code acquired through the worker terminal.
[0037] The above occurrence location selection interface may be provided to display a list of preset locations and allow one of them to be selected.
[0038] The above occurrence location selection interface may include at least one of a zone selection interface that displays preset zone tabs so that one of them can be selected, a line selection interface that displays preset line lists existing within a zone so that one of them can be selected, and a location selection interface within a line so that preset approximate location tabs within a line can be selected.
[0039] The above type selection interface may be provided to display preset issue type tabs so that one of them can be selected, the photo input interface may be provided to input a photo acquired from a photographing module of the worker terminal, the emergency selection interface may be provided to display preset emergency setting tabs so that one of them can be selected, and the description input interface may be provided to input a message through an input unit of the worker terminal.
[0040] The above types include at least pests and facility failures, and the issue occurrence status page may display an issue item indicating issue occurrence information classified as unconfirmed, an issue item indicating issue occurrence information regarding the pests, and an issue item indicating issue occurrence information regarding the facility failure.
[0041] The above issue occurrence status page may display the number of issue occurrence information classified as unconfirmed issues among the one or more issue occurrence information and the number of issue occurrence information by type.
[0042] The above occurrence location is divided into zones within the greenhouse, and the issue occurrence status page may display one or more issue items divided into zones.
[0043] The above issue occurrence information may further include the creation date of the issue, and the issue occurrence status page may separately display an issue item indicating issue occurrence information that includes the urgency among the one or more issue occurrence information and has the creation date of today.
[0044] The above administrator terminal, when a second issue item is selected according to a fourth input of the user, displays an issue detail page for the second issue item, and a reminder setting interface is provided on the issue detail page. When the administrator terminal obtains reminder date information for the second issue item through the reminder setting interface, the administrator terminal transmits the reminder date information to the server, and the server can set a reminder including the reminder date information in issue occurrence information corresponding to the second issue item.
[0045] In the above issue occurrence status page, an issue item that indicates issue occurrence information for which a reminder has been set may be displayed together with a reminder indicator.
[0046] The above administrator terminal can provide an alarm if there is issue occurrence information with a reminder set that includes reminder date information corresponding to today's date among the one or more issue occurrence information.
[0047] The above administrator terminal, when a third issue item is selected according to a fifth input of the user, displays an issue detail page for the third issue item, and a message input interface is provided on the issue detail page. When the administrator terminal obtains an additional message for the third issue item through the message input interface, the additional message is transmitted to the server, and the server can include the additional message in issue occurrence information corresponding to the third issue item.
[0048] The above issue detail page may display the above additional message included in the issue occurrence information corresponding to the third issue item.
[0049]
[0050] 1. Farming environment within farmland
[0051] Below, we describe the farming environment within the farmland.
[0052] Agricultural land according to the present disclosure may refer to a farm or greenhouse for growing crops. However, this is not limited to the above, and agricultural land may refer to a specific area designated for growing crops.
[0053] (1) Farmland
[0054] Figure 1 is a drawing for explaining the farming environment in farmland (10).
[0055] Referring to Fig. 1, crops (12) and facilities (15) can be placed within the farmland (10).
[0056] The crop (12) according to the present disclosure may refer to a crop to be cultivated within the farmland (10). For example, the crop (12) may refer to a cereal crop, a grain crop, a vegetable crop, and / or a fruit crop, regardless of type, such as rice, wheat, corn, potatoes, beans, paprika, strawberries, tomatoes, and / or cucumbers.
[0057] The crop (12) according to the present disclosure can be cultivated at a preset location within the farmland (10).
[0058] For example, crops (12) may be placed and grown in preset zones within farmland (10). In this case, multiple zones may be set within farmland (10).
[0059] For another example, crops (12) may be cultivated by being placed in preset lines within the farmland (10). In this case, multiple lines may be set within the farmland (10). Alternatively, multiple lines may be set within a specific area within the farmland (10).
[0060] Referring to Fig. 1, facilities (15) can be placed within agricultural land (10).
[0061] The facility (15) according to the present disclosure may refer to a device for operating farmland (10) and / or a device for managing crops (12). For example, an air conditioning device for managing the air in the farmland (10), a pump for watering crops (12), and / or a temperature measuring device for detecting the temperature of the farmland (10) may be placed within the farmland (10). Meanwhile, the type of the facility (15) is not limited to the examples described above, and may include various facilities, devices, and / or instruments for maintaining, managing, protecting, improving, and / or cultivating farmland (10) and / or crops (12).
[0062] (2) Worker
[0063] Referring to Fig. 1, a worker (20) performing work within the farmland (10) can be placed in the farmland (10).
[0064] For example, a worker (20) performing agricultural work on crops (12) may be deployed in the farmland (10). As another example, a worker (20) performing work to operate and / or manage a facility (15) may be deployed in the farmland (10). The work performed by the worker (20) is not limited to the examples described above, and may include various types of work within the farmland (10).
[0065] A worker (20) according to the present disclosure can perform work within the farmland (10) according to a set schedule. In this case, the schedule may be determined by a manager (30) as described below, but is not limited thereto.
[0066] A worker (20) according to the present disclosure can recognize issues within farmland (10) and report them to a manager (30). The worker (20) can use an issue management system to report issues. Details regarding the issue management system will be described later.
[0067] An issue according to this disclosure may refer to a problem occurring within agricultural land (10).
[0068] For example, an issue may refer to a problem occurring in a crop (12). For a more specific example, an issue may refer to a condition in which a pest or disease has occurred in a crop (12).
[0069] For another example, an issue may refer to a problem occurring in a facility (15). For a more specific example, an issue may refer to a malfunctioning humidity control device.
[0070] For another example, the issue could refer to a problem occurring in farmland (10). For a more specific example, the issue could refer to a broken glass side wall of a glass greenhouse.
[0071] The issues are not limited to the examples described above, and the issues may refer to various types of problems, such as temporary or permanent damage to crops (12) or reduced work efficiency of workers when performing work in agricultural land (10).
[0072] Meanwhile, according to the present disclosure, one or more workers (20) may be deployed in the farmland (10).
[0073] (3) Administrator
[0074] Referring to Fig. 1, a manager (30) who manages the farmland (10) can be placed in the farmland (10).
[0075] The manager (30) according to the present disclosure can oversee the work status and / or work progress within the farmland (10). For example, the manager (30) can set work areas for workers (20), create work schedules, instruct workers on work, inspect and / or evaluate the work status of workers, or monitor the status of the farmland (10). The tasks performed by the manager (30) are not limited to the examples described above, and the manager (30) can perform various tasks related to the farmland (10) in a way that can increase profits from the farmland (10).
[0076] The manager (30) according to the present disclosure can utilize an issue management system to manage issues within agricultural land (10). Specific details regarding the issue management system will be described later.
[0077] Meanwhile, one manager (30) may be assigned to each farmland (10). This is not limited to this, and more than one manager (30) may be assigned to each farmland (10).
[0078]
[0079] 2. Issue Management System
[0080] Below, an issue management system and method according to one embodiment are described.
[0081] (1) Components of the issue management system
[0082] Figure 2 is a diagram of an issue management system according to one embodiment.
[0083] Referring to FIG. 2, an issue management system according to one embodiment may include a worker terminal (100), an administrator terminal (200), and a server (300). The issue management system may manage issues occurring in farmland using the worker terminal (100), the administrator terminal (200), and the server (300).
[0084] (2) Main functions of the worker terminal
[0085] The worker terminal (100) according to the present disclosure means a terminal provided to a worker.
[0086] For example, the worker terminal (100) may refer to a terminal directly provided to the worker. As another example, the worker terminal (100) may refer to a terminal logged in with the worker's ID. In this case, the worker ID may be an ID assigned to each worker or an ID assigned to a worker group. The present invention is not limited thereto, and the worker terminal (100) may refer to various types of terminals that the worker can use.
[0087] The worker terminal (100) can be used by the worker to perform work. Details related to the worker's work have been described above in 1. Agricultural work environment within farmland, so further explanation will be omitted.
[0088] For example, the worker terminal (100) can be used by the worker to check the work schedule, check the work to be performed, record the work performed, or check the location where the work will be performed.
[0089] For a specific example, the worker terminal (100) can recognize a QR code (Quick Response code) provided for each crop location in the farmland to check the work content, record the work performed, or identify the current location.
[0090] For another example, the worker terminal (100) can be used to register issues discovered by workers in farmland with the server. Details related to these issues have already been described in detail in the section 1. Farming Environments in Farmland, so further explanation will be omitted. Details regarding registering issues in the issue management system will be described later.
[0091] The contents of use of the worker terminal (100) are not limited to the examples described above, and the worker terminal (100) can perform various operations to assist the worker's work.
[0092] The worker terminal (100) can transmit information related to work and / or information related to issues to the server (300) or receive such information from the server (300).
[0093] (3) Main functions of the administrator terminal
[0094] The administrator terminal (200) according to the present disclosure means a terminal assigned to an administrator.
[0095] For example, the administrator terminal (200) may refer to a terminal directly provided to the administrator. As another example, the administrator terminal (200) may refer to a terminal logged in with the administrator's ID. In this case, the administrator's ID may be an ID assigned to each administrator or an ID assigned to an administrator group. The present disclosure is not limited thereto, and the administrator terminal (200) may refer to various types of terminals that the administrator can use.
[0096] The administrator terminal (200) can be used by the administrator to perform his / her duties. The contents related to the administrator's duties have been described above in 1. Agricultural work environment within farmland, so a duplicate description will be omitted.
[0097] For example, the administrator terminal (200) can be used by the administrator to check the status of work in the farmland, check the progress of work, instruct workers to perform work, or create a work schedule.
[0098] For another example, the administrator terminal (200) can be used by the administrator to identify, register, and manage issues within farmland. Details regarding issues have been previously described in the section 1. Farming Environments within Farmland, so further explanation will be omitted. Details regarding identifying, registering, and managing issues will be described later.
[0099] The contents of use of the administrator terminal (200) are not limited to the examples described above, and the administrator terminal (200) can perform various operations to assist the administrator's work.
[0100] The administrator terminal (200) can transmit work-related information and / or issue-related information to the server (300) or receive information from the server (300).
[0101] (4) Main functions of the server
[0102] The server (300) according to the present disclosure means a device that stores and manages data within an issue management system.
[0103] Specifically, the server (300) can store information related to work and / or information related to issues received from the worker terminal (100). The server (300) can transmit the information stored in the server (300) to the worker terminal (100).
[0104] Additionally, the server (300) can store information related to work and / or information related to issues received from the administrator terminal (200). The server (300) can transmit the information stored in the server (300) to the administrator terminal (200).
[0105] Meanwhile, the server (300) can change stored data, add settings to data, or reclassify data according to a request from the administrator terminal (200).
[0106] According to one embodiment, the server (300) may receive and store issue occurrence information generated from the worker terminal (100). In this case, the issue occurrence information may be classified as an unconfirmed issue and stored in the server (300).
[0107] According to one embodiment, the server (300) can transmit stored issue occurrence information to the administrator terminal (200).
[0108] When the server (300) according to one embodiment obtains a registration decision for an unconfirmed issue from the administrator terminal (200), the server (300) can reclassify issue occurrence information stored as an unconfirmed issue into a registered issue.
[0109] When the server (300) according to one embodiment obtains a resolution decision for a registration issue from the administrator terminal (200), the server (300) can reclassify issue occurrence information classified as a registration issue and stored as a resolution issue.
[0110] When the server (300) according to one embodiment obtains a decision to delete an issue from the administrator terminal (200), the server (300) can delete the stored issue occurrence information.
[0111] According to one embodiment, the server (300) may receive and store issue occurrence information generated from the administrator terminal (100). In this case, the issue occurrence information may be classified as a registered issue and stored in the server (300). Details will be described later.
[0112] According to one embodiment, the server (300) can receive a reminder setting request from the administrator terminal (100) and set a reminder for issue occurrence information.
[0113] According to one embodiment, the server (300) can receive an additional message from the administrator terminal (100) and store it in the issue occurrence information.
[0114] Specific details regarding the operation of the server (300) will be described later.
[0115] (5) Additional examples of issue management systems
[0116] Meanwhile, in FIG. 2, the issue management system is illustrated as including one worker terminal (100) and one administrator terminal (200), but the number of worker terminals (100) and the number of administrator terminals (200) are not limited to the example described above.
[0117] FIG. 3 is a diagram of an issue management system according to one embodiment.
[0118] Referring to FIG. 3, an issue management system according to one embodiment may include a plurality of worker terminals (100-1, 100-2, …, 100-n), a plurality of administrator terminals (200-1, 200-2, …, 200-n), and a server (300).
[0119] Referring to FIG. 3, a plurality of worker terminals (100-1, 100-2, …, 100-n) according to one embodiment may belong to one worker terminal group (101). This is not limited thereto, and a plurality of worker terminal groups may exist.
[0120] Referring to FIG. 3, a plurality of administrator terminals (200-1, 200-2, …, 200-n) according to one embodiment may belong to one administrator terminal group (201). This is not limited thereto, and multiple administrator terminal groups may exist.
[0121]
[0122] 3. Worker terminal
[0123] Below, a worker terminal according to the present disclosure is described.
[0124] The worker terminal according to the present disclosure may refer to a terminal used by a worker. Since details regarding the worker terminal have been described above in 2. Issue Management System, any duplicate details will be omitted or briefly explained below.
[0125] (1) Components of the worker terminal
[0126] Figure 4 is a drawing showing the configuration of a worker terminal (100) according to one embodiment.
[0127] Referring to FIG. 4, a worker terminal (100) according to one embodiment may include a communication unit (110), an input unit (120), an output unit (130), a photographing module (140), a memory (150), and a processor (160). However, the present invention is not limited thereto, and the worker terminal (100) may further include other components or may be provided in a form in which some of the aforementioned components are omitted.
[0128] The communication unit (110) of the worker terminal (100) can transmit and / or receive data and / or information to and / or from the outside via wired and / or wireless communication. The worker terminal (100) can perform data communication with the administrator terminal (200) and / or the server (300) via the communication unit (110).
[0129] The input unit (120) of the worker terminal (100) can receive various user operations and transmit them to the processor (160) described later. The input unit (120) can receive user operations through an interface provided to the user via the output unit (130) described later. The input unit (120) can be implemented as a touchpad, keypad, mouse, and / or microphone.
[0130] The output unit (130) of the worker terminal (100) can output results according to the operation of the processor (160) described below. The output unit (130) can display various pages, interfaces, and / or indicators to the user. The output unit (130) can be implemented as a display, touch screen, and / or speaker.
[0131] The camera module (140) of the worker terminal (100) can capture photos, videos, and / or images, or recognize QR codes. The worker terminal (100) can acquire photos, videos, and / or images of the surrounding environment, or recognize QR codes, through the camera module (140). The camera module (140) can be implemented as a camera and / or camcorder, etc.
[0132] The memory (150) of the worker terminal (100) can store various processing programs, parameters for performing processing of the programs, and / or processing result data, etc. For example, the memory (150) can store instructions for the operation of the processor (160) to be described later, photos, videos, and / or images acquired through the shooting module (140), a method for generating issue occurrence information, a method for transmitting issue occurrence information, a method for displaying issue occurrence information, and / or a method for displaying an issue input page, etc. The memory (150) can be implemented as a nonvolatile semiconductor memory, a hard disk, a flash memory, a RAM (Random Access Memory), a ROM (Read Only Memory), an EEPROM (Electrically Erasable Programmable Read-Only Memory), or other types of (tangible) nonvolatile recording media.
[0133] The processor (160) of the worker terminal (100) may operate according to instructions and / or methods stored in the memory (150). In the following, operations of the worker terminal may be interpreted as being performed by the processor (160) of the worker terminal or under the control of the processor (160) unless otherwise stated. The processor (160) may be implemented as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a state machine, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), and a combination thereof.
[0134] Hereinafter, unless otherwise specified, the operation of the worker terminal (100) can be understood as being performed by the processor (160).
[0135] (2) Registering work details
[0136] The worker terminal according to the present disclosure can display the worker's work content and register the work content on a server. In this case, the worker terminal can display the worker's work content through an output unit and transmit the work content to the server through a communication unit.
[0137] According to one embodiment, a user of a worker terminal can check a work schedule and / or a work list and perform tasks through the worker terminal. The user of the worker terminal can also register the details of the tasks performed on the server through the worker terminal.
[0138] In one embodiment, a user of a worker terminal can perform a task by recognizing a QR code placed near the work area via the worker terminal. For example, a user of a worker terminal can register the start and / or end of a task, or register the work location, by recognizing a QR code placed near the work area.
[0139] (3) Creation of issue occurrence information
[0140] The worker terminal according to the present disclosure can generate information regarding issues within the farmland.
[0141] Specifically, the worker terminal can generate issue occurrence information based on user input. More specifically, the worker terminal provides the user with an issue entry page. When the user enters information related to the issue through an interface included in the issue entry page, issue occurrence information can be generated based on the entered information. In this case, the worker terminal can display the issue entry page through the output section and acquire user input through the input section to generate issue occurrence information.
[0142] Issue occurrence information according to the present disclosure may include various information for identifying and explaining specific issues that have occurred in agricultural land.
[0143] For example, issue occurrence information may include at least the type of issue, the location where the issue occurred, a photo related to the issue, a description related to the issue, whether the issue is urgent, the date the issue occurred, the date the issue occurrence information was created, and / or the name of the registrant of the issue occurrence information.
[0144] According to one embodiment, a worker terminal may generate issue occurrence information by obtaining the type of issue, the location where the issue occurred, a photo related to the issue, a description related to the issue, whether the issue is urgent, the date of occurrence of the issue, the date of creation, and / or the name of the registrant based on a user's input.
[0145] Meanwhile, according to one embodiment, the worker terminal can determine some of the issue occurrence information based on information stored in the worker terminal. In this case, some of the issue occurrence information can be determined and / or generated without user input.
[0146] For example, when a worker terminal obtains work location information via a QR code while the worker is performing a given task, and information regarding an issue is entered by the worker terminal, the worker terminal can determine the work location information obtained via the QR code as the location where the issue occurred. For another example, the worker terminal can determine the registrant name based on the user information logged into the terminal. For another example, the worker terminal can determine the creation date based on the date information set in the terminal. The information determined by the worker terminal is not limited to the examples described above, and some of the issue occurrence information may be determined based on information preset in the worker terminal related to the issue.
[0147] (4) Transmission of issue occurrence information
[0148] The worker terminal according to the present disclosure can transmit generated issue occurrence information to a server and / or an administrator terminal. In this case, the worker terminal can transmit the issue occurrence information to the server and / or an administrator terminal via a communication unit.
[0149] Specifically, users can transmit issue information to the server and / or administrator terminal via their worker terminal. This allows workers to report issues within their farmland to the administrator or store them on the server.
[0150] (5) Display of issue occurrence information
[0151] The worker terminal according to the present disclosure can display issue occurrence information. In this case, the worker terminal can display issue occurrence information through an output unit.
[0152] Specifically, the worker terminal can receive issue occurrence information from the server and display a page reflecting the received issue occurrence information. More specifically, the worker terminal can generate a page displaying issue items representing the issue occurrence information received from the server and provide the page to the user. In this case, the issue occurrence information received from the server may be issue occurrence information registered by workers and / or managers who have discovered issues within the farmland.
[0153] In one embodiment, a worker terminal can only display issue occurrence information generated by the worker terminal and transmitted to the server. In other words, an issue management system may be implemented to allow workers to check issue occurrence information. However, the issue management system may be implemented so that workers cannot check issue occurrence information for the entire farmland, but only the issue occurrence information they have entered. This is not limited to this, and the worker terminal may also be implemented to display issue occurrence information for the entire farmland, or the worker terminal may not display issue occurrence information.
[0154] The issue management system according to the present disclosure can classify issue occurrence information obtained from worker terminals and store it as unconfirmed issues until an issue registration or deletion decision is received from the administrator terminal. Accordingly, the worker terminal can display issue occurrence information classified as unconfirmed issues separately.
[0155] The issue management system according to the present disclosure can classify and store issue occurrence information obtained from worker terminals, issue occurrence information for which an issue registration decision is obtained from an administrator terminal, and issue occurrence information obtained from the administrator terminal as registered issues. Accordingly, the worker terminal can display issue occurrence information classified as registered issues separately.
[0156] (6) Issue input page
[0157] User input for generating issue occurrence information according to one embodiment can be obtained through an issue input page provided on the worker terminal.
[0158] An issue entry page according to one embodiment may include at least one issue entry interface for entering issue occurrence information.
[0159] An issue input interface according to one embodiment may include an occurrence location selection interface, a type selection interface, a photo input interface, an emergency selection interface, and / or a description input interface.
[0160] The contents of each interface are described with reference to FIGS. 5 and 6.
[0161] FIG. 5 is a diagram illustrating an issue input page according to one embodiment.
[0162] An occurrence location selection interface according to one embodiment may be provided to display a list of preset locations so that one of them can be selected.
[0163] Specifically, referring to FIG. 5, the occurrence location selection interface according to one embodiment may include at least a zone selection interface (1010), a line selection interface (1040), and a location selection interface within a line (1050).
[0164] A zone selection interface (1010) according to one embodiment may display a preset zone list and / or zone tabs, allowing one of the zones to be selected. For example, the zone list and / or zone tabs may be zones that divide agricultural land, such as Building A, Building B, and Building C. In another example, the zone list and / or zone tabs may be zones that divide spaces within agricultural land, such as Zone 1, Zone 2, Zone 3, and Zone 4. The number of zones and the number of zones divided are not limited to the examples described above, and may be set in various ways depending on the condition and / or current status of the agricultural land.
[0165] A line selection interface (1040) according to one embodiment may be provided to display a list of preset lines, one of which may be selected. Specifically, the line selection interface (1040) may be provided to display a list of preset lines existing within a region selected via the region selection interface (1010), one of which may be selected.
[0166] FIG. 6 is a diagram illustrating an issue input page according to one embodiment. Specifically, the issue input page of FIG. 6 may be displayed when the line selection interface (1040) of FIG. 5 is selected.
[0167] Referring to FIG. 6, an issue input page according to one embodiment may provide a zone selection interface (1110) and / or a line selection interface (1120).
[0168] A zone selection interface (1110) according to one embodiment may be provided to display preset zone tabs so that one of them can be selected. For example, referring to FIG. 6, the zone selection interface (1110) may be provided so that one of zones 1, 2, 3, 4, and 5 can be selected, and the selected zone may be displayed in a dark font color and / or bold letters.
[0169] A line selection interface (1120) according to one embodiment may display a preset line list (1130) and provide one of them for selection. For example, referring to FIG. 6, the line selection interface (1120) may display a line list (1130) including lines 101-right, 102-right, 102-left, 103-right, and 103-left, and when one of them is selected, the selected line may be provided to be displayed on the line selection interface (1120).
[0170] An issue entry page according to one embodiment may be provided with a confirmation interface (1140). When a user inputs a confirmation decision through the confirmation interface (1140), the area and / or line selected through the area selection interface (1110) and / or line selection interface (1120) are determined as the location where the issue occurred, and the worker terminal may display the issue entry page of FIG. 5.
[0171] Referring again to FIG. 5 , the line location selection interface (1050) according to one embodiment may display preset approximate location tabs, one of which may be selected. In this case, the approximate location tab may be a tab indicating a location on the line. More specifically, the approximate location tab may include Front, Middle, and Back tabs.
[0172] Meanwhile, the occurrence location selection interface according to one embodiment may be deactivated if location information corresponding to the QR code obtained through the worker terminal exists. In this case, information regarding the occurrence location of the issue may be determined based on the location information corresponding to the QR code.
[0173] Alternatively, the occurrence location selection interface according to one embodiment may be deactivated if location information corresponding to the worker information logged into the worker terminal exists. In this case, information regarding the occurrence location of the issue may be determined based on the location information corresponding to the worker information.
[0174] Referring to FIG. 5, a type selection interface (1020) according to one embodiment may display preset issue type tabs so that one of them can be selected. Specifically, the type selection interface (1020) according to one embodiment may display a pest tab and a facility failure tab so that one of them can be selected. The issue type tabs are not limited to the examples described above, and may be set in various ways depending on the condition of the farmland, the type of farmland, the type of crop, the type of facility, the weather in the area where the farmland is located, the characteristics of the area where the farmland is located, and / or the surrounding environment of the area where the farmland is located.
[0175] Referring to FIG. 5, a photo input interface (1030) according to one embodiment may be provided to input photos acquired using a worker terminal. Specifically, the photo input interface (1030) according to one embodiment may be provided to input photos, videos, and / or images acquired through a photographing module of the worker terminal.
[0176] Referring to FIG. 5, an emergency selection interface (1060) according to one embodiment may display preset emergency setting tabs, one of which may be selected. Specifically, the emergency selection interface (1060) according to one embodiment may display an On tab and an Off tab, one of which may be selected.
[0177] Referring to FIG. 5, a description input interface (1070) according to one embodiment may be provided to allow a message to be entered based on a user's input. Specifically, the description input interface (1070) according to one embodiment may be provided to allow a message to be entered through an input unit of a worker terminal.
[0178] Referring to FIG. 5, an issue entry page according to one embodiment may include an issue creation interface (1080). When a user inputs an issue creation decision through the issue creation interface (1080), the worker terminal may generate issue occurrence information based on information selected and / or input through interfaces on the issue entry page.
[0179]
[0180] 4. Administrator terminal
[0181] Below, an administrator terminal according to the present disclosure is described.
[0182] The administrator terminal according to the present disclosure may refer to a terminal used by an administrator. Since the administrator terminal has been described above in 2. Issue Management System, any duplicate information will be omitted or briefly explained below.
[0183] (1) Components of the administrator terminal
[0184] Figure 7 is a drawing showing the configuration of an administrator terminal (200) according to one embodiment.
[0185] Referring to FIG. 7, an administrator terminal (200) according to one embodiment may include a communication unit (210), an input unit (220), an output unit (230), a memory (240), and a processor (250). However, the present invention is not limited thereto, and the administrator terminal (200) may further include other components or may be provided in a form in which some of the aforementioned components are omitted.
[0186] The communication unit (210) of the administrator terminal (200) can transmit and / or receive data and / or information to and / or from the outside via wired and / or wireless communication. The administrator terminal (200) can perform data communication with the worker terminal (100) and / or the server (300) via the communication unit (210).
[0187] The input unit (220) of the administrator terminal (200) can receive various user operations and transmit them to the processor (250) described later. The input unit (220) can receive user operations through an interface provided to the user via the output unit (230) described later. The input unit (220) can be implemented as a touchpad, keypad, mouse, and / or microphone, etc.
[0188] The output unit (230) of the administrator terminal (200) can output results according to the operation of the processor (250) described below. The output unit (230) can display various pages, interfaces, and / or indicators to the user. The output unit (230) can be implemented as a display, touch screen, and / or speaker.
[0189] The memory (240) of the administrator terminal (200) can store various processing programs, parameters for performing the processing of the programs, and / or processing result data, etc. For example, the memory (240) can store instructions for the operation of the processor (250) described below, a method for generating issue occurrence information, a method for transmitting issue occurrence information, a method for displaying issue occurrence information, a method for managing issue occurrence information, a method for transmitting issue management content, a method for displaying an issue input page, a method for displaying an issue status page, and / or a method for displaying an issue detail page, etc. The memory (240) can be implemented as a nonvolatile semiconductor memory, a hard disk, a flash memory, a RAM, a ROM, an EEPROM, or other types of nonvolatile recording media.
[0190] The processor (250) of the administrator terminal (200) may operate according to instructions and / or methods stored in the memory (240). In the following, operations of the administrator terminal may be interpreted as being performed by the processor (250) of the administrator terminal or under the control of the processor (250) unless otherwise stated. The processor (250) may be implemented as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing unit (DSP), a state machine, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), and a combination thereof.
[0191] Hereinafter, unless otherwise specified, the operation of the administrator terminal (200) can be understood as being performed by the processor (250).
[0192] (2) Task management
[0193] The administrator terminal according to the present disclosure can manage information related to work within the farmland. In this case, the administrator terminal can display information related to work within the farmland via an output unit.
[0194] According to one embodiment, the administrator terminal can display the task status and / or task progress based on the task content registered by the worker on the server.
[0195] According to one embodiment, a user of an administrator terminal can manage work within a farmland by checking information related to work within the farmland through the administrator terminal. For example, a user of an administrator terminal can set and / or register a work schedule, set and / or register an area where work is to be performed, set and / or register a worker to perform the work, or set and / or register the work to be performed by the worker through the administrator terminal.
[0196] (3) Creation of issue occurrence information
[0197] The administrator terminal according to the present disclosure can generate information regarding issues within agricultural land.
[0198] Specifically, the administrator terminal can generate issue occurrence information based on user input. More specifically, the administrator terminal provides the user with an issue entry page. When the user enters information related to the issue through an interface included in the issue entry page, issue occurrence information can be generated based on the entered information. In this case, the administrator terminal can display the issue entry page through the output section and acquire user input through the input section to generate issue occurrence information.
[0199] Specific details related to the issue occurrence information generation and issue input page according to one embodiment have been described above in 3. Worker Terminal, so a duplicate description will be omitted.
[0200] Meanwhile, issue occurrence information generated from an administrator terminal may be simpler than that generated from a worker terminal. For example, because issue occurrence information generated from an administrator terminal does not require administrator confirmation, it may not include photos related to the issue.
[0201] (4) Transmission of issue occurrence information
[0202] The administrator terminal according to the present disclosure can transmit generated issue occurrence information to a server and / or other administrator terminals. In this case, the administrator terminal can transmit the issue occurrence information to the server and / or other administrator terminals via a communication unit.
[0203] Specifically, users can transmit issue-related information to the server and / or other administrator terminals via the administrator terminal. This allows administrators to register information about issues within their farmland on the server and share it with other administrators.
[0204] (5) Display of issue occurrence information
[0205] The administrator terminal according to the present disclosure can display issue occurrence information. In this case, the administrator terminal can display the issue occurrence information through an output unit.
[0206] According to one embodiment, the administrator terminal may request issue occurrence information from the server to display issue occurrence information. Specifically, the administrator terminal may transmit a trigger to the server for requesting issue occurrence information.
[0207] For example, the administrator terminal may transmit a trigger to the server when it starts operating. For another example, the administrator terminal may transmit a trigger along with data transmission to the server. For another example, the administrator terminal may transmit a trigger to the server at preset time intervals. For another example, the administrator terminal may transmit a trigger to the server in response to a user's update request. In this case, the user may enter an update request through an update interface displayed on the administrator terminal.
[0208] The server may provide one or more issue occurrence information stored on the server to the administrator terminal in response to a trigger.
[0209] According to one embodiment, the administrator terminal can display an issue occurrence status page reflecting issue occurrence information. Specifically, the administrator terminal can create and provide a user with an issue occurrence status page displaying issue items representing issue occurrence information received from the server. In this case, the issue occurrence information received from the server may be issue occurrence information registered by workers and / or administrators who have discovered issues within the farmland.
[0210] In one embodiment, the administrator terminal can display an issue occurrence status page that allows users to easily check the overall status of issues in the farmland. For example, the administrator terminal can display all issues in the farmland on the issue occurrence status page, only issues from a specific period, only issues within a specific area, only issues classified by a specific type, or only the number of issues. Specific details regarding the issue occurrence status page are described below.
[0211] According to one embodiment, the administrator terminal can display detailed information about issue occurrence information on an issue details page. Specifically, when a user selects a specific issue item, the administrator terminal can display an issue details page containing issue occurrence information for the selected issue item. Specific details regarding the issue details page will be described below.
[0212] (6) Issue occurrence information management
[0213] The administrator terminal according to the present disclosure can manage issue occurrence information. In this case, the administrator terminal can display issue occurrence information through an output unit and obtain user input through an input unit to manage issue occurrence information.
[0214] According to one embodiment, an administrator terminal can display an issue detail page for issue occurrence information and obtain input for managing issue occurrence information from a user through the issue detail page.
[0215] In one embodiment, the administrator terminal can change information contained in issue occurrence information. For example, the administrator terminal can change the issue type, issue occurrence location, issue-related photo, issue-related description, issue urgency, and / or issue occurrence date based on user input.
[0216] According to one embodiment, an administrator terminal can classify issue occurrence information. For example, the administrator terminal can classify issue occurrence information classified as an unconfirmed issue based on user input into a registered issue. Furthermore, the administrator terminal can classify issue occurrence information classified as a registered issue based on user input into a resolved issue. Furthermore, the administrator terminal can delete issue occurrence information classified as an unconfirmed issue based on user input. Furthermore, the administrator terminal can delete issue occurrence information classified as a registered issue based on user input.
[0217] According to one embodiment, the administrator terminal can set a reminder for issue occurrence information. For example, the administrator terminal can obtain reminder date information for issue occurrence information based on user input, and set a reminder for issue occurrence information based on the obtained reminder date information.
[0218] According to one embodiment, the administrator terminal can generate an alarm if issue occurrence information includes a reminder date corresponding to today's date among the issue occurrence information. In this case, today's date can be determined based on the date information set on the administrator terminal.
[0219] In one embodiment, an administrator terminal may store an additional message in issue occurrence information. For example, the administrator terminal may obtain an additional message for issue occurrence information based on a user input and store the obtained additional message in the issue occurrence information. In another example, if the issue occurrence information is reclassified, the administrator terminal may store an additional message corresponding to the reclassification in the issue occurrence information. Specifically, if the issue occurrence information is reclassified as a registered issue, the administrator terminal may store an additional message indicating that the issue occurrence information is classified as a registered issue in the issue occurrence information. If the issue occurrence information is reclassified as a resolved issue, the administrator terminal may store an additional message indicating that the issue occurrence information is classified as a resolved issue in the issue occurrence information. If the issue occurrence information is deleted, the administrator terminal may store an additional message indicating that the issue occurrence information has been deleted in the issue occurrence information.
[0220] According to the present disclosure, by storing additional messages related to issue occurrence information, communication between managers regarding the issue can be facilitated. For example, by storing additional messages in the issue occurrence information, managers can share the status of issue processing with other managers and / or workers, or record additional information about the issue. In another example, managers can determine and notify the manager responsible for handling the issue by storing additional messages in the issue occurrence information. In another example, managers can track the history of an issue based on the additional messages stored in the issue occurrence information.
[0221] (7) Transmission of issue management contents
[0222] The administrator terminal according to the present disclosure can transmit setting information and / or changes regarding issue occurrence information to the server. In this case, the administrator terminal can transmit setting information and / or changes regarding issue occurrence information to the server via the communication unit.
[0223] In one embodiment, the administrator terminal may transmit changes to information included in the issue occurrence information to the server, thereby causing the server to change the information included in the issue occurrence information. For example, based on user input, the administrator terminal may transmit changes to the type of issue, the location of the issue, a photo related to the issue, a description related to the issue, the urgency of the issue, and / or the issue occurrence date included in the issue occurrence information to the server. The server may then change the information included in the issue occurrence information based on the received information.
[0224] In one embodiment, an administrator terminal may transmit a classification decision regarding issue occurrence information to a server, thereby causing the server to classify the issue occurrence information. For example, the administrator terminal may obtain an issue registration decision regarding issue occurrence information classified as an unconfirmed issue based on a user's input and transmit the decision to the server, and the server may classify the issue occurrence information as a registered issue based on the received decision to register the issue. In addition, the administrator terminal may obtain an issue resolution decision regarding issue occurrence information classified as a registered issue based on a user's input and transmit the decision to the server, and the server may classify the issue occurrence information as a resolved issue based on the received decision to resolve the issue. In addition, the administrator terminal may obtain an issue deletion decision regarding issue occurrence information classified as an unconfirmed issue based on a user's input and transmit the decision to the server, and the server may delete the issue occurrence information based on the received decision to delete the issue. In addition, the administrator terminal may obtain an issue deletion decision regarding issue occurrence information classified as a registered issue based on a user's input and transmit the decision to the server, and the server may delete the issue occurrence information based on the received decision to delete the issue.
[0225] In one embodiment, the administrator terminal may transmit reminder date information for issue occurrence information to a server, thereby allowing the server to set a reminder for the issue occurrence information. For example, the administrator terminal may obtain reminder date information for issue occurrence information based on user input and transmit it to the server, and the server may set a reminder for the issue occurrence information based on the received reminder date information.
[0226] In one embodiment, an administrator terminal may transmit an additional message regarding issue occurrence information to a server, thereby causing the server to store the additional message in the issue occurrence information. For example, the administrator terminal may obtain an additional message regarding issue occurrence information based on a user input and transmit the message to the server, and the server may store the received additional message in the issue occurrence information. In another example, the administrator terminal may obtain an issue registration decision regarding issue occurrence information and transmit the decision to the server, and the server may store an additional message indicating that the issue occurrence information is classified as a registered issue in the issue occurrence information. The administrator terminal may obtain an issue resolution decision regarding issue occurrence information and transmit the decision to the server, and the server may store an additional message indicating that the issue occurrence information is classified as a resolved issue in the issue occurrence information. The administrator terminal may obtain an issue deletion decision regarding issue occurrence information and transmit the decision to the server, and the server may store an additional message indicating that the issue occurrence information has been deleted in the issue occurrence information.
[0227] (8) Issue Status Page
[0228] 1) Issue item
[0229] In one embodiment, the issue status page may display issue items indicating issue occurrence information. In this case, the issue items may be displayed in a format that allows users to easily recognize issue occurrence information.
[0230] In one embodiment, an issue item may refer to at least one piece of information that can represent an issue selected from among the information included in the issue occurrence information. For example, an issue item may refer to an occurrence location included in the issue occurrence information. In another example, an issue item may refer to an indication of the type of issue included in the issue occurrence information. In another example, an issue item may refer to an indication of the issue creation date included in the issue occurrence information. In yet another example, an issue item may refer to an indication of a photo related to an issue included in the issue occurrence information. This is not limited to the above, and an issue item may refer to a combination of information included in the issue occurrence information.
[0231] An issue status page according to one embodiment may display issue items for all issue occurrence information within the farmland.
[0232] An issue status page according to one embodiment may display issue entries for issue occurrence information generated during a specific period.
[0233] According to one embodiment, the issue status page may display issue items for issue occurrence information in specific zones. For example, issue items indicating issue occurrence information in Zone 1, issue items indicating issue occurrence information in Zone 2, issue items indicating issue occurrence information in Zone 3, and / or issue items indicating issue occurrence information in Zone 4 may be displayed separately. The criteria for identifying the location where an issue occurred are not limited to the examples described above.
[0234] In one embodiment, the issue status page may display issue items for issue occurrence information separately based on the type of issue included in the issue occurrence information. For example, issue items indicating issue occurrence information related to pests and / or issue items indicating issue occurrence information related to facility failures may be displayed separately.
[0235] In one embodiment, the issue status page may display issue items for issue occurrence information separately based on the classification status of the issue occurrence information. For example, issue items representing issue occurrence information classified as unconfirmed issues, issue items representing issue occurrence information classified as registered issues, and / or issue items representing issue occurrence information classified as resolved issues may be displayed separately.
[0236] 2) Issue classification indicator
[0237] An issue status page according to one embodiment may display an issue classification indicator that distinguishes issue occurrence information.
[0238] According to one embodiment, the issue status page may display an issue classification indicator that classifies issue occurrence information based on the type of issue included in the issue occurrence information. In this case, the issue classification indicator may include a pest classification indicator and / or a facility failure classification indicator.
[0239] According to one embodiment, the issue status page may display an issue classification indicator that classifies issue occurrence information based on the classification status of the issue occurrence information. In this case, the issue classification indicator may include an unconfirmed issue classification indicator, a registered issue classification indicator, and / or a resolved issue classification indicator.
[0240] According to one embodiment, the issue status page may display an issue classification indicator that classifies issue occurrence information based on the location of the issue occurrence included in the issue occurrence information. In this case, the issue classification indicator may include a farmland classification indicator, a zone classification indicator, and / or a line classification indicator.
[0241] In one embodiment, an issue classification indicator may be provided as an issue classification interface. In this case, the issue status page may display issue occurrence information classified according to the issue classification selected through the issue classification interface.
[0242] An issue classification interface according to one embodiment may be provided to display a preset list of issue classifications and / or issue classification tabs, one of which may be selected.
[0243] 3) Number of issues indicator
[0244] An issue status page according to one embodiment may display an issue count indicator indicating the number of issue occurrence information.
[0245] According to one embodiment, the issue status page may display an issue count indicator that counts issue occurrence information based on the type of issue included in the issue occurrence information. In this case, the issue count indicator may include a pest count indicator and / or a facility failure count indicator.
[0246] According to one embodiment, the issue status page may display an issue count indicator that counts issue occurrence information based on the status of issue occurrence information classification. In this case, the issue count indicator may include an unconfirmed issue count indicator, a registered issue count indicator, and / or a resolved issue count indicator.
[0247] According to one embodiment, the issue status page may display an issue count indicator that counts issue occurrence information based on the location of occurrence of the issue included in the issue occurrence information. In this case, the issue count indicator may include an issue count indicator by farmland, an issue count indicator by zone, and / or an issue count indicator by line.
[0248] 4) Heatmap
[0249] An issue status page according to one embodiment may display a heatmap based on the number of issue occurrences.
[0250] In one embodiment, a heatmap may refer to a map that displays different colors at locations corresponding to specific areas on a map representing the entire agricultural land area, depending on the number of issue occurrences occurring in that area. In this case, the color may have higher saturation and / or brightness as the number of issues increases. This is not a limitation, and the color may have lower saturation and / or brightness as the number of issues increases.
[0251] In one embodiment, a heatmap may refer to a map that displays different colors at locations corresponding to specific lines on a map corresponding to a specific area within farmland, based on the number of issue occurrences occurring on that line. In this case, the color may have higher saturation and / or brightness as the number of issues increases. This is not a limitation, and the color may have lower saturation and / or brightness as the number of issues increases.
[0252] A heatmap according to one embodiment can be displayed on the Web.
[0253] 5) Emergency indicator
[0254] An issue status page according to one embodiment may display an emergency indicator indicating urgency.
[0255] An emergency indicator according to one embodiment may be displayed together with an issue item indicating issue occurrence information including an emergency.
[0256] According to one embodiment, an emergency indicator may be displayed together with an issue count indicator that counts issue occurrence information including emergency.
[0257] 6) Reminder indicator
[0258] An issue status page according to one embodiment may display a reminder indicator indicating a reminder.
[0259] A reminder indicator according to one embodiment may be displayed together with an issue item indicating issue occurrence information for which a reminder has been set.
[0260] According to one embodiment, a reminder indicator may be displayed together with an issue count indicator that counts the occurrence information of an issue for which a reminder has been set.
[0261] According to one embodiment, a reminder indicator may display a different color depending on the reminder date information. For example, when the reminder date information and today's date are the same, the reminder indicator may be displayed in a color with higher saturation and / or brightness than when the reminder date information and today's date are different. This is not limited to the above, and when the reminder date information and today's date are the same, the reminder indicator may be displayed in a color with lower saturation and / or brightness than when the reminder date information and today's date are different.
[0262] For another example, the reminder indicator may be displayed in a color with higher saturation and / or brightness as the difference between the reminder date information and today's date information decreases. This is not a limitation, and the reminder indicator may be displayed in a color with lower saturation and / or brightness as the difference between the reminder date information and today's date information decreases.
[0263] 7) Today's urgent issues
[0264] In one embodiment, the issue status page may display today's urgent issues separately. In this case, "today's urgent issue" may refer to issue occurrence information that includes the word "urgent" and is created today. This is because issue occurrence information created on a worker's terminal with an urgent setting is classified as "unconfirmed" and stored, which could cause the manager to miss the timing of the issue response. Furthermore, even if the manager makes the mistake of visiting the location of the issue as an emergency, the loss is minimal. Therefore, issue occurrence information created on the worker's terminal with an urgent setting is displayed with confidence.
[0265] In one embodiment, the issue status page may display a separate issue item representing today's urgent issue.
[0266] In one embodiment, the issue status page may separately display the count of today's urgent issues.
[0267] 8) Update interface
[0268] An issue status page according to one embodiment may provide an update interface.
[0269] An update interface according to one embodiment may be provided to update issue occurrence information. For example, a user may select the update interface to send a trigger to the server to receive the latest issue occurrence information. In another example, a user may select the update interface to transmit changed issue occurrence information to the server from the administrator terminal.
[0270] An issue status page according to one embodiment may provide an interface linking to an issue entry page.
[0271] 9) Example of an issue status page
[0272] Below, the issue status page is described with reference to FIGS. 8 to 14.
[0273] Figure 8 is a diagram showing an issue status page according to one embodiment.
[0274] Referring to FIG. 8, an issue status page according to one embodiment may display a farmland classification interface (1210), a zone classification indicator (1220), an unconfirmed issue count indicator (1230), a pest and facility failure count indicator (1240), an emergency indicator (1250), a lime indicator (1260), a today's urgent issue interface (1270) that links to an issue status page displaying today's urgent issues, an update interface (1280), and an issue creation interface (1290) that links to an issue input page.
[0275] Referring to FIG. 8, the farmland classification interface (1210) according to one embodiment may display preset farmland tabs so that one of them can be selected. For example, the farmland classification interface (1210) may be provided so that one of Building A, Building B, and Building C can be selected.
[0276] Referring to FIG. 8, a zone division indicator (1220) according to one embodiment may be displayed to distinguish zones within an agricultural field. For example, the zone division indicator (1220) may be displayed to distinguish zones 1, 2, 3, 4, 5, and 6.
[0277] Referring to FIG. 8, the unconfirmed issue count indicator (1230) according to one embodiment may display the count of issue occurrence information classified as unconfirmed. Specifically, the count of issue occurrence information classified as unconfirmed may be displayed for each zone classified by the zone classification indicator (1220).
[0278] Referring to FIG. 8, the pest and facility failure count indicator (1240) according to one embodiment may display the counted number of pest-related issue occurrence information and the counted number of facility failure-related issue occurrence information. Specifically, the counted number of pest-related issue occurrence information and the counted number of facility failure-related issue occurrence information may be displayed for each zone classified by the zone classification indicator (1220).
[0279] Referring to FIG. 8, an emergency indicator (1250) according to one embodiment may be displayed together with an issue count indicator in which issue occurrence information including an emergency is counted. Specifically, if issue occurrence information including an emergency exists among issue occurrence information regarding pests in each zone classified by a zone classification indicator (1220), a circular emergency indicator (1250) may be displayed on the issue count indicator (1240) regarding pests in each zone. Alternatively, if issue occurrence information including an emergency exists among issue occurrence information regarding facility failure in each zone classified by a zone classification indicator (1220), a circular emergency indicator (1250) may be displayed on the issue count indicator (1240) regarding facility failure in each zone. Alternatively, if there is issue occurrence information including emergency among the issue occurrence information classified as unconfirmed issues by zone classified by zone classification indicator (1220), a circular emergency indicator (1250) may be displayed on the unconfirmed issue count indicator by zone (1230).
[0280] Referring to FIG. 8, a reminder indicator (1260) according to one embodiment may display issue occurrence information for which a reminder is set together with a counted issue count indicator. Specifically, if issue occurrence information for which a reminder is set exists in issue occurrence information for each zone classified by a zone classification indicator (1220), reminder indicators (1261, 1262) may be displayed for each corresponding zone.
[0281] FIG. 8 according to one embodiment illustrates an issue status page when a reminder is set for at least one of the issue occurrence information belonging to zones 1, 2, 5, and 6. Specifically, FIG. 8 illustrates an issue status page in which at least one of the issue occurrence information belonging to zone 2 has issue occurrence information in which reminder date information identical to today's date is set, and thus a dark-colored reminder indicator (1262) is displayed, and in which at least one of the issue occurrence information belonging to zones 1, 5, and 6 has issue occurrence information in which a reminder date different from today's date is set, and thus a light-colored reminder indicator (1261) is displayed.
[0282] Referring to FIG. 8, an interface for today's urgent issues (1270) may be provided via the issue status page. The administrator terminal may display today's urgent issues based on user input via the interface for today's urgent issues (1270).
[0283] Referring to FIG. 8, an update interface (1280) may be provided via the issue status page. The administrator terminal may update issue occurrence information based on user input via the update interface (1280).
[0284] Referring to FIG. 8, an issue creation interface (1290) may be provided via an issue status page. The administrator terminal may display the issue status page based on user input via the issue creation interface (1290).
[0285] Figure 9 is a diagram showing an issue status page according to one embodiment.
[0286] Referring to FIG. 9, an issue status page according to one embodiment may display a zone classification indicator (1310), an issue classification interface (1320), an issue item (1330) indicating issue occurrence information classified as an unconfirmed issue, a facility failure classification indicator (1340), and a pest classification indicator (1350).
[0287] Referring to FIG. 9, a zone classification indicator (1310) according to one embodiment may indicate the zone to which issue items appearing on the issue status page belong. For example, the zone classification indicator (1310) may indicate that issue items appearing on the issue status page are issues occurring in Zone 1 of Building A.
[0288] Referring to FIG. 9, an issue classification interface (1320) according to one embodiment may display preset issue classification tabs, allowing selection of one of them. For example, the issue classification interface (1320) may allow selection of one of the following: an unconfirmed issue, a confirmed and registered issue, or a resolved issue.
[0289] Referring to FIG. 9, an issue item (1330) according to one embodiment may represent issue occurrence information classified into an issue status selected through the issue classification interface (1320). For example, the issue item (1330) may represent issue occurrence information classified into an unconfirmed issue selected through the issue classification interface (1320). An issue item may refer to a form displayed so that a user can easily recognize issue occurrence information, and since specific details have been described above, a duplicate description will be omitted.
[0290] Referring to FIG. 9, a facility failure classification indicator (1340) may be displayed in an issue item indicating information regarding the occurrence of an issue related to a facility failure. Since the facility failure classification indicator has been described above, a detailed explanation will be omitted.
[0291] Referring to FIG. 9, a pest classification indicator (1350) may be displayed in an issue item indicating information on the occurrence of an issue related to a pest. Since the pest classification indicator has been described above, a duplicate explanation will be omitted.
[0292] Figure 10 is a diagram showing an issue status page according to one embodiment.
[0293] Referring to FIG. 10, an issue status page according to one embodiment may display a zone classification indicator (1610), an issue classification interface (1620), an issue item (1630) indicating issue occurrence information classified as a confirmed and registered issue, a facility failure classification indicator (1640), an emergency indicator (1650), and a reminder indicator (1660).
[0294] The contents related to the zone classification indicator (1610), issue classification interface (1620), and facility failure classification indicator (1640) according to one embodiment have been described above in FIG. 9, so a duplicate description will be omitted.
[0295] In Fig. 10, only the facility failure classification indicator (1640) is displayed, but a pest classification indicator may also be displayed depending on the issue type of the issue occurrence information.
[0296] Referring to FIG. 10, an issue item (1630) according to one embodiment may represent issue occurrence information classified into an issue status selected through the issue classification interface (1620). For example, the issue item (1630) may represent issue occurrence information classified into an issue that has been confirmed and registered and selected through the issue classification interface (1620). An issue item may refer to a form displayed so that a user can easily recognize issue occurrence information, and since specific details have been described above, a duplicate description will be omitted.
[0297] Referring to FIG. 10, an emergency indicator (1650) may be displayed on an issue item indicating issue occurrence information including an emergency. Since the emergency indicator has been described above, a detailed explanation will be omitted.
[0298] Referring to FIG. 10, a reminder indicator (1660) may be displayed on an issue item indicating issue occurrence information for which a reminder has been set. Specifically, an icon that identifies whether the issue occurrence information is for which a reminder has been set and the number of days remaining until the reminder date may be displayed as a reminder indicator (1660). In this case, the icon may be displayed in a light color, but if the reminder date is today's date, the icon may be displayed in a dark color.
[0299] Figure 11 is a diagram showing an issue status page according to one embodiment.
[0300] Referring to FIG. 11, an issue status page according to one embodiment may display a zone classification indicator (1910), an issue classification interface (1920), an issue item (1930) indicating issue occurrence information classified as a resolved issue, and a facility failure classification indicator (1940).
[0301] The contents related to the zone classification indicator (1910), issue classification interface (1920), and facility failure classification indicator (1940) according to one embodiment have been described above in FIG. 9, so a duplicate description will be omitted.
[0302] In Fig. 11, only the facility failure classification indicator (1940) is displayed, but a pest classification indicator may also be displayed depending on the issue type of the issue occurrence information.
[0303] Referring to FIG. 11, an issue item (1930) according to one embodiment may represent issue occurrence information classified as a resolved issue selected through the issue classification interface (1920). An issue item may refer to a form displayed so that a user can easily recognize issue occurrence information, and as specific details have been described above, a redundant description will be omitted.
[0304] Figure 12 is a diagram showing an issue status page according to one embodiment.
[0305] Referring to FIG. 12, an issue status page according to one embodiment may display an issue item (2110) indicating today's urgent issue, a facility failure classification indicator (2120), a pest classification indicator (2130), and a confirmation interface (2140).
[0306] The contents related to the facility failure classification indicator (2120) and the pest classification indicator (2130) according to one embodiment have been described above in FIG. 9, so a duplicate description will be omitted.
[0307] Referring to FIG. 12, an issue item (2110) according to one embodiment may represent issue occurrence information determined to be an urgent issue of the day. "Urgent issue of the day" refers to issue occurrence information that includes the word "urgent" and has a creation date of today. An issue item may refer to a format that allows users to easily recognize issue occurrence information. Since the specific details have been described above, a detailed explanation will be omitted.
[0308] According to one embodiment, the issue status page of FIG. 12 may be displayed based on the user's selection of the Today's Urgent Issues interface (1270) shown in FIG. 8. In this case, the user may select the confirmation interface (2140) to return to the page shown in FIG. 8.
[0309] Figure 13 is a diagram showing an issue status page according to one embodiment.
[0310] Referring to FIG. 13, an issue status page according to one embodiment may display a heat map (2210) for the entire farmland, a heat map (2220) for a specific area within the farmland, a period selection interface (2250), and a farmland classification interface (2260).
[0311] Since the content related to the farmland classification interface (2260) according to one embodiment has been described above in FIG. 8, a duplicate description will be omitted.
[0312] Referring to FIG. 13, a heat map (2210) for the entire agricultural land according to one embodiment may display a heat map for the entire area included in the agricultural land selected through the agricultural land classification interface (2260). For example, if Building A is selected through the agricultural land classification interface (2260), heat maps for Areas 1, 2, 3, and 4 included in Building A may be displayed as a heat map (2210) for the entire agricultural land.
[0313] Referring to FIG. 13, a heat map (2220) for a specific area according to one embodiment may display a heat map for a specific area included in farmland selected through a farmland classification interface (2260). For example, if Building A is selected through the farmland classification interface (2260), a heat map (2220) for Area 1 included in Building A, a heat map for Area 2 included in Building A, a heat map for Area 3 included in Building A, and a heat map for Area 4 included in Building A may be displayed, respectively. A heat map may refer to a map in which colors are displayed differently according to the number of issue occurrence information that occurred in a specific area at a location corresponding to a specific area, and since the contents related to the heat map have been described above, a duplicate description will be omitted.
[0314] Referring to FIG. 13, a heat map (2220) for a specific area may display a different color for a line at a location corresponding to a specific line on a map corresponding to the specific area depending on the number of issue occurrence information occurring in the corresponding line. For example, if the number of issue occurrence information occurring in the corresponding line is small, the line may be displayed in a light color (2230), and if the number of issue occurrence information occurring in the corresponding line is large, the line may be displayed in a dark color (2240). The method of displaying the color of a line depending on the number of issue occurrence information is not limited to the above-described example.
[0315] Referring to FIG. 13, a heat map (2220) for a specific area according to one embodiment may also display the total number of issue occurrence information that occurred in the area.
[0316] Referring to FIG. 13, a period selection interface (2250) according to one embodiment may be provided to select a period within which issue occurrence information to be displayed as a heat map belongs. When a period is selected through the period selection interface (2250), a heat map (2220) for a specific area may be displayed based on the number of issue occurrence information within the period selected through the period selection interface (2250).
[0317] As shown in Figure 13, the issue status page displays the number of issue occurrence information as a heat map, allowing users to intuitively and easily recognize which areas and locations have the most issues.
[0318] Figure 14 is a diagram showing an issue status page according to one embodiment.
[0319] Referring to FIG. 14, an issue status page according to one embodiment may display an issue item (2310) indicating issue occurrence information occurring in a specific area, an issue item thumbnail (2320) indicating one issue occurrence information, a today's date indicator (2330), an emergency indicator (2340), an area classification interface (2350), and an issue search interface (2360).
[0320] Since the contents related to the emergency indicator (2340) and the zone division interface (2350) according to one embodiment have been described above, a duplicate description will be omitted.
[0321] Referring to FIG. 14, an issue item (2310) according to one embodiment may indicate issue occurrence information that has occurred in a selected area through a area division interface (2350).
[0322] Referring to FIG. 14, an issue item (2310) according to one embodiment may be displayed in the form of an issue item thumbnail (2320). An issue item thumbnail (2320) according to one embodiment refers to a photo included in issue occurrence information. For example, an issue item thumbnail (2320) may refer to a representative photo included in issue occurrence information displayed in a small size.
[0323] As shown in Figure 14, the issue status page displays issue occurrence information in thumbnail form, allowing users to intuitively and easily recognize which issue each issue item relates to.
[0324] Referring to FIG. 14, an issue item thumbnail indicating issue occurrence information with a creation date of today's date may display a today's date indicator (2330).
[0325] Referring to FIG. 14, an issue search interface (2360) according to one embodiment may display an issue search window, allowing a user to search for information related to an issue occurrence for which they wish to search. In this case, the issue status page may display issue item thumbnails representing issue occurrence information including the information entered through the issue search interface (2360) in a categorized manner.
[0326] The issue status page according to the above-described embodiment may be generated and displayed on the administrator terminal based on issue occurrence information. This is not a limitation, and the issue status page according to one embodiment may be generated on the server based on issue occurrence information, provided to the administrator terminal, and displayed on the administrator terminal.
[0327] (9) Issue details page
[0328] An issue detail page according to one embodiment may display information about issue occurrence information.
[0329] Specifically, an issue detail page according to one embodiment may display an issue type indicator according to the type of issue included in the issue occurrence information, an occurrence location indicator according to the occurrence location of the issue, an image indicator according to a photo related to the issue, a description indicator according to a description related to the issue, an emergency indicator according to the urgency of the issue, a reminder indicator according to a reminder setting, and / or a message indicator according to an additional message.
[0330] Indicators displayed on an issue detail page according to one embodiment may vary depending on the classification of the issue occurrence information. For example, an issue detail page for an issue occurrence information classified as an unconfirmed issue may not display a reminder indicator and / or message indicator.
[0331] In one embodiment, the issue details page may display information about an issue item selected based on user input. In this case, the issue item may be the same issue item displayed on the issue status page. Since the issue items and issue status page have been described above, a detailed explanation will be omitted.
[0332] An issue registration interface may be further provided on the issue details page for issue occurrence information classified as an unconfirmed issue according to one embodiment.
[0333] Issue occurrence information displayed on the issue details page according to one embodiment can be reclassified as a registered issue through the issue registration interface. Specifically, upon obtaining an issue registration decision through the issue registration interface, the administrator terminal can reclassify the issue occurrence information as a registered issue. Alternatively, upon obtaining an issue registration decision through the issue registration interface, the administrator terminal can transmit the issue registration decision to the server, causing the server to reclassify the issue occurrence information as a registered issue.
[0334] An issue resolution interface may be further provided on the issue detail page for issue occurrence information classified as a registered issue according to one embodiment.
[0335] Issue information displayed on the issue details page according to one embodiment can be reclassified as resolved issues through the issue resolution interface. Specifically, upon obtaining an issue resolution decision through the issue resolution interface, the administrator terminal can reclassify the issue information as resolved issues. Alternatively, upon obtaining an issue resolution decision through the issue resolution interface, the administrator terminal can transmit the issue resolution decision to the server, causing the server to reclassify the issue information as resolved issues.
[0336] An issue detail page according to one embodiment may further provide an issue deletion interface.
[0337] Issue occurrence information displayed on the issue details page according to one embodiment can be deleted through the issue deletion interface. Specifically, the administrator terminal can delete the issue occurrence information upon obtaining an issue deletion decision through the issue deletion interface. Alternatively, upon obtaining an issue deletion decision through the issue deletion interface, the administrator terminal can transmit the issue deletion decision to the server, thereby causing the server to delete the issue occurrence information.
[0338] An issue detail page according to one embodiment may further provide a message input interface.
[0339] A message input interface according to one embodiment may be provided to input a message based on a user's input.
[0340] Issue occurrence information displayed on the issue details page according to one embodiment may store additional messages entered by the user through a message input interface. Specifically, when the administrator terminal obtains an additional message through the message input interface, the additional message may be stored in the issue occurrence information. Alternatively, when the administrator terminal obtains an additional message through the message input interface, the additional message may be transmitted to the server, causing the server to store the additional message in the issue occurrence information.
[0341] An issue detail page according to one embodiment may further provide an emergency selection interface.
[0342] An emergency selection interface according to one embodiment may be provided to display preset emergency activation tabs, one of which may be selected.
[0343] According to one embodiment, the issue occurrence information displayed on the issue detail page can be set to be urgent through an emergency selection interface. Specifically, when an emergency activation is input through the emergency selection interface, the administrator terminal can change the emergency status of the issue occurrence information to urgent. Alternatively, when an emergency activation is input through the emergency selection interface, the administrator terminal can transmit the emergency activation information to the server, causing the server to change the emergency status of the issue occurrence information to urgent. Meanwhile, when an emergency deactivation is input through the emergency selection interface, the administrator terminal can deactivate the emergency status of the issue occurrence information. Alternatively, when an emergency deactivation is input through the emergency selection interface, the administrator terminal can transmit the emergency deactivation information to the server, causing the server to deactivate the emergency status of the issue occurrence information.
[0344] According to one embodiment, the issue details page may further provide a reminder setting interface.
[0345] A reminder setting interface according to one embodiment may display preset reminder activation tabs so that one of them can be selected, and a date input window may be displayed so that date information can be entered according to a user's input.
[0346] Issue occurrence information displayed on an issue detail page according to one embodiment can have a reminder set via a reminder setting interface. Specifically, the administrator terminal can set a reminder for the issue occurrence information by entering reminder activation and date information through the reminder setting interface. Alternatively, the administrator terminal can transmit the reminder activation and date information to the server by entering reminder activation and date information through the reminder setting interface, thereby causing the server to set a reminder for the issue occurrence information.
[0347] Below, the issue details page is described with reference to FIGS. 15 to 19.
[0348] Figures 15 and 16 are diagrams showing issue detail pages according to one embodiment.
[0349] The issue detail pages according to FIGS. 15 and 16 may be displayed when one of the issue items shown in FIG. 9 is selected. Specifically, the issue detail pages according to FIGS. 15 and 16 may display information regarding the occurrence of issues classified as unconfirmed issues.
[0350] Referring to FIG. 15, an issue detail page according to one embodiment may display an occurrence location indicator (1410), an issue type indicator (1420), an information page interface (1430), an image indicator (1440), a description indicator (1450), an issue registration interface (1460), and a settings page interface (1470).
[0351] An occurrence location indicator (1410) according to one embodiment may display an occurrence location included in issue occurrence information displayed on an issue detail page. For example, the occurrence location indicator (1410) may display an issue occurrence area, an issue occurrence line, and a location within the line included in the issue occurrence information.
[0352] An issue type indicator (1420) according to one embodiment may display the type of issue included in the issue occurrence information displayed on the issue detail page. For example, the issue type indicator (1420) may display a pest indicator or a facility failure indicator depending on the type of issue included in the issue occurrence information.
[0353] An image indicator (1440) according to one embodiment may display a photo related to an issue included in issue occurrence information displayed on an issue detail page.
[0354] According to one embodiment, a description indicator (1450) may display a description related to an issue included in issue occurrence information displayed on an issue detail page. In this case, the description indicator (1450) may also display the name of the registrant of the issue occurrence information.
[0355] According to one embodiment, an information page interface (1430) and a settings page interface (1470) may be provided so that a user can select one of the information page interface (1430) and the settings page interface (1470).
[0356] When user input is obtained through the information page interface (1430) according to one embodiment, the issue detail page may display a page centered on information about issue occurrence information.
[0357] When user input is obtained through the settings page interface (1470) according to one embodiment, the issue detail page may display a page focused on changing settings for issue occurrence information.
[0358] An issue registration interface (1460) according to one embodiment may be provided for the user to select.
[0359] When user input is obtained through the issue registration interface (1460) according to one embodiment, issue occurrence information displayed on the issue details page may be reclassified as a registered issue. Since the reclassification of issue occurrence information has been described above, a detailed explanation will be omitted.
[0360] The issue detail page of FIG. 16 may be displayed when user input is obtained through the settings page interface (1470) shown in FIG. 15.
[0361] Referring to FIG. 16, an issue detail page according to one embodiment may display an occurrence location indicator (1510), an issue type indicator (1520), a settings page interface (1530), an emergency selection interface (1540), and an issue registration interface (1550).
[0362] The contents related to the occurrence location indicator (1510), issue type indicator (1520), setting page interface (1530), and issue registration interface (1550) according to one embodiment have been described above in FIG. 15, so a duplicate description will be omitted.
[0363] Referring to FIG. 16, an emergency selection interface (1540) according to one embodiment may display preset emergency activation tabs, allowing one of them to be selected. Since the details related to emergency setting have been described above, a detailed explanation will be omitted.
[0364] Figures 17 and 18 are diagrams showing issue detail pages according to one embodiment.
[0365] The issue detail pages according to FIGS. 17 and 18 may be displayed when one of the issue items shown in FIG. 10 is selected. Specifically, the issue detail pages according to FIGS. 17 and 18 may display information on issue occurrence information classified as registered issues.
[0366] Referring to FIG. 17, an issue detail page according to one embodiment may display an occurrence location indicator (1710), an issue type indicator (1720), an information page interface (1730), an image indicator (1740), a description indicator (1750), a message indicator (1760), a message input interface (1770), an issue resolution interface (1780), and a settings page interface (1790).
[0367] The contents related to the occurrence location indicator (1710), issue type indicator (1720), information page interface (1730), image indicator (1740), description indicator (1750), and setting page interface (1790) according to one embodiment have been described above in FIG. 15, so a duplicate description will be omitted.
[0368] According to one embodiment, a message indicator (1760) may display additional messages stored in issue occurrence information displayed on the issue detail page. The issue detail page of FIG. 17 relates to issue occurrence information classified as a registered issue. As such, the message indicator (1760) displays an additional message indicating that the issue occurrence information has been confirmed and classified as a registered issue. Since the details related to the additional message have been previously described, a detailed explanation will be omitted.
[0369] A message input interface (1770) according to one embodiment may be provided to allow messages to be entered based on user input. If an additional message is entered through the message input interface (1770) according to one embodiment, the administrator terminal and / or server may store the additional message in the issue occurrence information. Since the message input interface has been described above, a detailed description thereof will be omitted.
[0370] An issue resolution interface (1780) according to one embodiment may be provided for the user to select.
[0371] When user input is obtained through the issue resolution interface (1780) according to one embodiment, issue occurrence information displayed on the issue details page may be reclassified as a resolved issue. Since the reclassification of issue occurrence information has been described above, a detailed explanation will be omitted.
[0372] The issue detail page of FIG. 18 may be displayed when user input is obtained through the settings page interface (1790) shown in FIG. 17.
[0373] Referring to FIG. 18, an issue detail page according to one embodiment may display an occurrence location indicator (1810), an issue type indicator (1820), a settings page interface (1830), an emergency selection interface (1840), a reminder settings interface (1850, 1860), and an issue resolution interface (1870).
[0374] The contents related to the occurrence location indicator (1810), issue type indicator (1820), and setting page interface (1830) according to one embodiment have been described above in FIG. 15, so a duplicate description will be omitted.
[0375] The issue resolution interface (1870) according to one embodiment has been described above in FIG. 17, so a duplicate description will be omitted.
[0376] An emergency selection interface (1840) according to one embodiment may display preset emergency activation tabs, allowing one to be selected. Since the details related to emergency setting have been described above, a detailed explanation will be omitted.
[0377] A reminder setting interface (1850, 1860) according to one embodiment may include a reminder activation interface (1850) and a reminder date input interface (1860).
[0378] A reminder activation interface (1850) according to one embodiment may display preset reminder activation tabs, allowing one to be selected. A reminder date input interface (1860) according to one embodiment may allow date information to be entered based on user input. Since the details related to reminder settings have been described above, a detailed explanation will be omitted.
[0379] Figure 19 is a diagram showing an issue detail page according to one embodiment.
[0380] The issue detail page according to Fig. 19 may be displayed when one of the issue items shown in Fig. 11 is selected. Specifically, the issue detail page according to Fig. 19 may display information on issue occurrence information classified as a resolved issue.
[0381] Referring to FIG. 19, an issue detail page according to one embodiment may display an occurrence location indicator (2010), an issue type indicator (2020), an information page interface (2030), an image indicator (2040), a description indicator (2050), a message indicator (2060), and a page close interface (2070).
[0382] The contents related to the occurrence location indicator (2010), issue type indicator (2020), information page interface (2030), and image indicator (2040) according to one embodiment have been described above in FIG. 15, so a duplicate description will be omitted.
[0383] A message indicator (2060) according to one embodiment may display additional messages stored in the issue occurrence information displayed on the issue details page. Since the details related to the additional messages have been described above, a detailed explanation will be omitted.
[0384] A page close interface (2070) according to one embodiment may be provided for the user to select.
[0385] When user input is obtained through the page close interface (2070) according to one embodiment, the issue detail page can be closed and the issue status page can be displayed before the issue detail page is displayed.
[0386] The issue detail page according to the above-described embodiment may be generated and displayed on the administrator terminal based on issue occurrence information. This is not a limitation, and the issue detail page according to one embodiment may be generated on the server based on issue occurrence information, provided to the administrator terminal, and displayed on the administrator terminal.
[0387]
[0388] 5. Server
[0389] Below we describe the server.
[0390] A server according to the present disclosure may refer to a device that performs data communication with worker terminals and administrator terminals, and stores and / or manages data. Since the server has been described above in 2. Issue Management System, any duplicate information will be omitted or briefly explained below.
[0391] (1) Server components
[0392] Fig. 20 is a drawing showing the configuration of a server (300) according to one embodiment.
[0393] Referring to FIG. 20, a server (300) according to one embodiment may include a communication unit (310), a memory (320), and a processor (330). However, the present invention is not limited thereto, and the server (300) may further include other components or may be provided in a form in which some of the aforementioned components are omitted.
[0394] The communication unit (310) of the server (300) can transmit and / or receive data and / or information to and / or from the outside via wired and / or wireless communication. The server (300) can perform data communication with a worker terminal (100) and / or an administrator terminal (200) via the communication unit (310).
[0395] The memory (320) of the server (300) can store various processing programs, parameters for performing program processing, and / or processing result data. For example, the memory (320) can store instructions for the operation of the processor (330) described below, an issue storage method, and / or an issue management method. The memory (320) can be implemented as a nonvolatile semiconductor memory, a hard disk, a flash memory, a RAM, a ROM, an EEPROM, or other types of nonvolatile recording media.
[0396] The processor (330) of the server (300) may operate according to instructions and / or methods stored in the memory (320). In the following, unless otherwise stated, the operation of the server may be interpreted as being performed by the processor (320) of the server or under the control of the processor (320). The processor (320) may be implemented as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing unit (DSP), a state machine, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), and a combination thereof.
[0397] Hereinafter, unless otherwise specified, the operation of the server (300) can be understood as being performed by the processor (330).
[0398] (2) Saving issue occurrence information
[0399] The server according to the present disclosure can store issue occurrence information received from a worker terminal and / or an administrator terminal. In this case, the server can receive issue occurrence information from the worker terminal and / or the administrator terminal via a communication unit and store the received issue occurrence information via memory.
[0400] Specific details related to the issue occurrence information have been described above in 3. Worker Terminal, so duplicate explanations will be omitted.
[0401] (3) Classification of issue occurrence information
[0402] The server according to the present disclosure can classify and store received issue occurrence information according to preset conditions. Specifically, when registering issue occurrence information in an issue management system, the server can classify and register the issue occurrence information according to preset conditions. In this case, the server can classify issue occurrence information received through the communication unit according to preset conditions and store it in memory.
[0403] In one embodiment, a server can classify issue occurrence information received from worker terminals and store it as an unconfirmed issue. An unconfirmed issue may refer to a state before an issue occurrence is confirmed by an administrator and registered or deleted. In other words, an unconfirmed issue may refer to a temporarily registered issue.
[0404] According to one embodiment, a server can classify issue occurrence information received from an administrator terminal as a registered issue and store it. Issue occurrence information received from an administrator terminal may be generated by the administrator, and thus can be classified and stored as a registered issue.
[0405] (4) Issue occurrence information management
[0406] A server according to the present disclosure can manage stored issue occurrence information. In this case, the server can manage issue occurrence information stored in memory.
[0407] According to one embodiment, the server can transmit stored issue occurrence information to a worker terminal and / or an administrator terminal.
[0408] Specifically, the server can transmit issue occurrence information to the worker terminal and / or the administrator terminal in response to a trigger received from the worker terminal and / or the administrator terminal. Specific details regarding the trigger have been described above in Section 4. Administrator Terminal, so a detailed explanation will be omitted.
[0409] A server according to one embodiment can reclassify and store stored issue occurrence information.
[0410] Specifically, the server may reclassify issue occurrence information into registered issues based on an issue registration decision regarding issue occurrence information received from the administrator terminal. Furthermore, the server may reclassify issue occurrence information into resolved issues based on an issue resolution decision regarding issue occurrence information received from the administrator terminal. Furthermore, the server may delete issue occurrence information based on an issue deletion decision regarding issue occurrence information received from the administrator terminal. Since the reclassification of issue occurrence information has been described above in Section 4. Administrator Terminal, a detailed explanation will be omitted.
[0411] According to one embodiment, the server can change some information of the stored issue occurrence information.
[0412] Specifically, the server can change the information contained in the issue occurrence information based on the configuration information and / or changes to the issue occurrence information received from the administrator terminal. Since the details related to changing the issue occurrence information have been described above in 4. Administrator Terminal, a duplicate explanation will be omitted.
[0413] A server according to one embodiment may set a reminder for issue occurrence information.
[0414] Specifically, the server can set a reminder for issue occurrence information based on the reminder date information received from the administrator terminal. Details related to reminder settings have been previously described in 4. Administrator Terminal, so a detailed explanation will be omitted.
[0415] A server according to one embodiment may store additional messages with issue occurrence information.
[0416] Specifically, the server can store additional messages related to issue occurrence information received from the administrator terminal in the issue occurrence information. Furthermore, the server can store additional messages related to the reclassification of issue occurrence information in the issue occurrence information. The details related to the additional messages have been previously described in Section 4. Administrator Terminal, so a detailed explanation will be omitted.
[0417]
[0418] 6. Operation of the issue management system
[0419] Below, the operation of an issue management system according to one embodiment is described.
[0420] Figure 21 is a flowchart illustrating an issue management method according to one embodiment.
[0421] Referring to FIG. 21, the worker terminal (100) can generate issue occurrence information (3010) based on user input and transmit the issue occurrence information to the server (300) (3020). Specific details regarding issue occurrence information, generation of issue occurrence information, and transmission of issue occurrence information have been described above, so a duplicate description will be omitted.
[0422] The server (300) can classify issue occurrence information received from the worker terminal (100) as an unconfirmed issue and store it (3030). Specific details regarding classification as an unconfirmed issue and an unconfirmed issue have been described above, so a duplicate explanation will be omitted.
[0423] The administrator terminal (200) can request issue occurrence information (3040) from the server (300), and the server (300) can transmit issue occurrence information to the administrator terminal (200) (3050) according to the request of the administrator terminal (200). Since the specific details regarding the request and transmission of issue occurrence information have been described above, a duplicate description will be omitted.
[0424] The administrator terminal (200) can display an issue status page (3060) reflecting the received issue occurrence information. Since the specific details of the issue status page have been described above, a duplicate description will be omitted.
[0425] The administrator terminal (200) can obtain (3070) an issue registration decision for an unconfirmed issue through user input. Since the specific details of the issue registration decision have been described above, a duplicate description will be omitted.
[0426] The administrator terminal (200) can transmit (3080) the acquired issue registration decision to the server (300), and the server (300) can reclassify the issue occurrence information into a confirmed and registered issue and store it (3090). Since the specific details regarding the reclassification of issue occurrence information have been described above, a duplicate description will be omitted.
[0427] Figure 22 is a flowchart illustrating an issue management method according to one embodiment.
[0428] Referring to FIG. 22, the server (300) may store issue occurrence information (3110). The issue occurrence information may be information received from a worker terminal (100) and / or an administrator terminal (200). Since specific details regarding the issue occurrence information have been described above, a duplicate description will be omitted.
[0429] The administrator terminal (200) can request issue occurrence information (3120) from the server (300), and the server (300) can transmit issue occurrence information to the administrator terminal (200) (3130) according to the request of the administrator terminal (200). Since the specific details regarding the request and transmission of issue occurrence information have been described above, a duplicate description will be omitted.
[0430] The administrator terminal (200) can display an issue status page (3140) reflecting the received issue occurrence information. Since the specific details of the issue status page have been described above, a duplicate description will be omitted.
[0431] The administrator terminal (200) can obtain (3150) an issue resolution decision for an issue that has been confirmed and registered through user input. Since the specific details of the issue resolution decision have been described above, a detailed explanation will be omitted.
[0432] The administrator terminal (200) can transmit (3160) the acquired issue resolution decision to the server (300), and the server (300) can reclassify the issue occurrence information into resolved issues and store them (3170). Since the specific details regarding the reclassification of issue occurrence information have been described above, a duplicate description will be omitted.
[0433] Figure 23 is a flowchart illustrating an issue management method according to one embodiment.
[0434] Referring to FIG. 23, the administrator terminal (200) can generate issue occurrence information (3210) based on user input and transmit the issue occurrence information to the server (300) (3220). Specific details regarding issue occurrence information, generation of issue occurrence information, and transmission of issue occurrence information have been described above, so a duplicate description will be omitted.
[0435] The server (300) can classify and store (3230) the issue occurrence information received from the administrator terminal (200) as a confirmed and registered issue. Since the specific details of the confirmed and registered issue have been described above, a duplicate description will be omitted.
[0436] Figure 24 is a flowchart illustrating an issue management method according to one embodiment.
[0437] Referring to FIG. 24, the server (300) may store issue occurrence information (3310). The issue occurrence information may be information received from a worker terminal (100) and / or an administrator terminal (200). Since specific details regarding the issue occurrence information have been described above, a detailed explanation will be omitted.
[0438] The administrator terminal (200) can request issue occurrence information (3320) from the server (300), and the server (300) can transmit issue occurrence information to the administrator terminal (200) (3330) according to the request of the administrator terminal (200). Since the specific details regarding the request and transmission of issue occurrence information have been described above, a duplicate description will be omitted.
[0439] The administrator terminal (200) can display an issue status page (3340) reflecting the received issue occurrence information. Since the specific details of the issue status page have been described above, a duplicate description will be omitted.
[0440] The administrator terminal (200) can obtain date information for setting a reminder through user input (3350) and transmit it to the server (300) (3360), and the server (300) can set a reminder for issue occurrence information (3370) based on the obtained date information. Since specific details regarding reminder setting have been described above, a duplicate description will be omitted.
[0441] Figure 25 is a flowchart illustrating an issue management method according to one embodiment.
[0442] Referring to FIG. 25, the server (300) may store issue occurrence information (3410). The issue occurrence information may be information received from a worker terminal (100) and / or an administrator terminal (200). Since specific details regarding the issue occurrence information have been described above, a duplicate description will be omitted.
[0443] The administrator terminal (200) can request issue occurrence information from the server (300) (3420), and the server (300) can transmit issue occurrence information to the administrator terminal (200) (3430) according to the request of the administrator terminal (200). Since the specific details regarding the request and transmission of issue occurrence information have been described above, a duplicate description will be omitted.
[0444] The administrator terminal (200) can identify (3440) whether there is issue occurrence information with a reminder set that includes reminder date information corresponding to today's date among the issue occurrence information. If there is issue occurrence information with a reminder set that includes reminder date information corresponding to today's date among the issue occurrence information, the administrator terminal (200) can generate an alarm (3450). Since specific details regarding reminder identification and alarm generation have been described above, a duplicate description will be omitted.
[0445] Figure 26 is a flowchart illustrating an issue management method according to one embodiment.
[0446] Referring to FIG. 26, the server (300) may store issue occurrence information (3610). The issue occurrence information may be information received from the worker terminal (100) and / or the administrator terminal (200). Since specific details regarding the issue occurrence information have been described above, a duplicate description will be omitted.
[0447] The administrator terminal (200) can request issue occurrence information from the server (300) (3620), and the server (300) can transmit issue occurrence information to the administrator terminal (200) (3630) according to the request of the administrator terminal (200). Since the specific details regarding the request and transmission of issue occurrence information have been described above, a duplicate description will be omitted.
[0448] The administrator terminal (200) can display an issue status page (3640) reflecting the received issue occurrence information. Since the specific details of the issue status page have been described above, a duplicate description will be omitted.
[0449] The administrator terminal (200) can obtain (3650) an additional message through user input and transmit (3660) the same to the server (300), and the server (300) can store (3670) the obtained additional message in the issue occurrence information. Since the specific details regarding obtaining and storing the additional message have been described above, a duplicate description will be omitted.
[0450] The system and / or method according to the above-described embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium.
[0451] Computer-readable media may include program instructions, data files, data structures, etc., alone or in combination.
[0452] The program commands recorded on the computer-readable recording medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software.
[0453] Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as read-only memory (ROM), random access memory (RAM), and flash memory.
[0454] Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.
[0455] A hardware device may be configured to operate as one or more software modules to perform the operations of the embodiment, and vice versa.
[0456] The present invention described above is not limited to the above-described embodiments and the attached drawings, as those skilled in the art can make various substitutions, modifications, and changes without departing from the technical spirit of the present invention. Furthermore, the embodiments described in this document are not limited in their application, and all or part of each embodiment may be selectively combined to allow for various modifications. Furthermore, the steps constituting each embodiment may be utilized individually or in combination with the steps constituting other embodiments.
Claims
1. In an issue management system including an administrator terminal, a worker terminal, and a server, At least one worker terminal assigned to a worker who is guided to perform tasks within the greenhouse according to a set schedule; At least one administrator terminal assigned to an administrator who oversees the work status and work progress within the greenhouse; and A server that is communicatively connected to the worker terminal and the administrator terminal and stores and manages information about the greenhouse; The above worker terminal transmits the first issue occurrence information generated according to the user's first input to the server, The above first issue occurrence information includes at least the type of issue, the location where the issue occurred, a photo of the issue, and whether the issue is urgent. The above first input is obtained through an issue input interface provided to the worker terminal, The above server, At least store the first issue occurrence information received from the worker terminal, and classify the first issue occurrence information as an unconfirmed issue and store it until an issue registration decision for the first issue occurrence information is received from the administrator terminal. In response to a trigger received from the above administrator terminal, one or more stored issue occurrence information is provided to the above administrator terminal, The above administrator terminal displays an issue occurrence status page reflecting one or more of the provided issue occurrence information, The above issue occurrence status page displays one or more issue items indicating one or more issue occurrence information, and the one or more issue items are displayed by being classified according to the type, and an issue item indicating issue occurrence information classified as an unconfirmed issue is displayed by being classified as an unconfirmed issue despite the type. Issue items that display issue occurrence information including the above urgency are displayed with an emergency indicator indicating the above urgency. Issue management system.
2. In paragraph 1, The above administrator terminal displays an issue detail page for the first issue item when the first issue item is selected based on the user's second input, The above issue detail page displays the type, occurrence location, and photo corresponding to the first issue item selected above. Issue management system.
3. In paragraph 2, When the above first issue item is an issue item classified as an unconfirmed issue, an issue registration interface is further provided on the issue details page. When the above administrator terminal obtains an issue registration decision for the first issue item through the issue registration interface, it transmits the issue registration decision to the server, The above server reclassifies the issue occurrence information classified as the unconfirmed issue corresponding to the first issue item into a registered issue. Issue management system.
4. In paragraph 3, When the above first issue item is an issue item that indicates issue occurrence information classified as the above registered issue, an issue resolution interface is further provided on the issue detail page. The above administrator terminal, when an issue resolution decision for the first issue item is obtained through the issue resolution interface, transmits the issue resolution decision to the server, The above server reclassifies the issue occurrence information classified as the registered issue corresponding to the first issue item into a resolved issue. Issue management system.
5. In paragraph 4, Issue items that indicate issue occurrence information classified as resolved issues are displayed as resolved issues on the issue occurrence status page despite the above type. Issue management system.
6. In paragraph 1, The above administrator terminal transmits the second issue occurrence information generated according to the user's third input to the server, The above second issue occurrence information includes at least the type of issue and the occurrence location of the issue, The above third input is obtained through the issue input interface provided on the administrator terminal, The server stores the second issue occurrence information received from the administrator terminal, and classifies the second issue occurrence information as a registration issue and stores it even if an issue registration decision for the second issue occurrence information is not received. Issue management system.
7. In paragraph 1, The above issue input interface is, Including an interface for selecting the location of occurrence of the issue, an interface for selecting the type of the issue, an interface for entering a photo regarding the issue, an interface for selecting an emergency of the issue, and an interface for entering a description regarding the issue. Issue management system.
8. In paragraph 7, The above occurrence location selection interface is deactivated when there is location information corresponding to the QR code acquired through the worker terminal. Issue management system.
9. In paragraph 7, The above occurrence location selection interface provides a list of preset locations from which one can be selected. Issue management system.
10. In paragraph 7, The above occurrence location selection interface is, A zone selection interface that displays preset zone tabs so that one of them can be selected; A line selection interface that displays a list of preset lines existing within the area and allows one to be selected. Including at least one of the in-line position selection interfaces that provides for selecting one of the preset approximate position tabs within the line, Issue management system.
11. In paragraph 7, The above type selection interface is provided by displaying preset issue type tabs so that one of them can be selected. The above photo input interface is provided to input a photo acquired from the photographing module of the worker terminal, The above emergency selection interface is provided to display preset emergency setting tabs so that one of them can be selected. The above description input interface is provided so that a message can be input through the input section of the worker terminal. Issue management system.
12. In paragraph 1, The above types include at least pests and facility failures, The above issue occurrence status page displays issue items that indicate issue occurrence information classified as unconfirmed, issue items that indicate issue occurrence information regarding the pests, and issue items that indicate issue occurrence information regarding the facility failure. Issue management system.
13. In paragraph 1, The above issue occurrence status page displays the number of issue occurrence information classified as unconfirmed issues among the one or more issue occurrence information and the number of issue occurrence information by type. Issue management system.
14. In paragraph 1, The above occurrence locations are divided into zones within the greenhouse, The above issue occurrence status page displays one or more of the above issue items divided by the above area. Issue management system.
15. In paragraph 1, The above issue occurrence information further includes the creation date of the issue, The above issue occurrence status page displays a separate issue item that includes the above urgent issue occurrence information among the above one or more issue occurrence information and indicates the issue occurrence information with the above creation date of today. Issue management system.
16. In paragraph 1, The above administrator terminal displays an issue detail page for the second issue item when the second issue item is selected according to the user's fourth input, The above issue detail page provides a reminder setting interface, When the above administrator terminal obtains reminder date information for the second issue item through the reminder setting interface, it transmits the reminder date information to the server, The above server sets a reminder including the reminder date information in the issue occurrence information corresponding to the second issue item. Issue management system.
17. In paragraph 16, In the above issue occurrence status page, the issue items that display the issue occurrence information for which the above reminder has been set are displayed with a reminder indicator. Issue management system.
18. In paragraph 16, The above administrator terminal is, If there is an issue occurrence information with a reminder set that includes reminder date information corresponding to today's date among the one or more issue occurrence information, an alarm is provided. Issue management system.
19. In paragraph 1, The above administrator terminal displays an issue detail page for the third issue item when the third issue item is selected according to the user's fifth input. The above issue detail page provides a message input interface, When the above administrator terminal obtains an additional message for the third issue item through the message input interface, it transmits the additional message to the server, The above server includes the additional message in the issue occurrence information corresponding to the third issue item. Issue management system.
20. In paragraph 19, The above issue detail page displays the above additional message included in the issue occurrence information corresponding to the above third issue item. Issue management system.
Citation Information
Patent Citations
Farming management system, farming management device, farming management method, computer program, and recording medium
KR1020100005032A
System and method for controlling building energy
KR1020140104284A
Device which manages abnormal UItuations about a field of plant construction work
KR1020140111121A
KR20210131568A
KR20220071586A
