Information processing system, information processing method, and program

Abstract

To provide an information processing system, an information processing method, and a program for achieving traceability in an agricultural product supply chain. [Solution] An information processing system comprising: a code information memory unit that stores basic information associated with an automatic recognition code issued for each managed item related to the agricultural produce supply chain; a code reading processing unit that outputs a UI corresponding to the basic information of the read automatic recognition code in response to reading the automatic recognition code; a registration processing unit that accepts input of work information for processes related to the managed item via the UI and links the work information to the automatic recognition code and records it in a tracking database; and a pairing unit that reads the automatic recognition code that is a parent code and the automatic recognition code that is a child code, and links the work information linked to the child code to the parent code.

Description

[Technical field]

[0001] The present disclosure relates to an information processing system, an information processing method, and a program relating to information management in an agricultural product supply chain. [Background technology]

[0002] In recent years, with the background of increasing consumer interest in food safety, there is a demand in the agricultural field as well for the realization of traceability that makes it possible to trace the history of each process from the production of agricultural products to distribution and sales. As a technology related to agricultural product traceability, Patent Document 1 discloses a system that manages information on the history of pesticide spraying and determines whether or not the pesticide can be used. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-101804 A Summary of the Invention [Problem to be solved by the invention]

[0004] In a system such as that shown in Patent Document 1, it is possible to manage the history of pesticide spraying so that residual pesticides on agricultural products do not exceed standard values. However, the management of history information (trace information) implemented in the system of Patent Document 1 is limited to the management of one type of pesticide in one field. In the real agricultural product supply chain, multiple businesses and multiple bases are involved, and there is a demand for the realization of traceability that consolidates and shares information recorded by each business and each base.

[0005] One of the objectives of the exemplary embodiments of the present disclosure is to provide an information processing system, an information processing method, and a program for achieving traceability in an agricultural product supply chain. [Means for solving the problem]

[0006] An information processing system according to one aspect of the present disclosure includes: An information processing system for information management in an agricultural product supply chain, comprising: a code information storage unit that stores basic information associated with an automatic recognition code issued for each management target related to the agricultural product supply chain; a code reading processing unit that outputs a UI (User Interface) corresponding to the basic information of one of the read automatic recognition codes in response to reading the one of the automatic recognition codes; a registration processing unit that receives an input of work information of a process related to the managed object via the UI, and records the work information in a tracking database in association with the one automatic recognition code; The device is equipped with a pairing unit that reads an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generates pairing information indicating a correspondence between the parent code and the child code, and links work information linked to the child code to the parent code.

[0007] Because the information management system has the above-mentioned features, it can efficiently manage the recording, viewing, and sharing of information according to each process and the services of each business operator, even if multiple businesses and / or multiple locations are involved in the agricultural product supply chain from production to sales.

[0008] Other problems and other solutions disclosed in the present application will become apparent from the embodiments and drawings of the present disclosure. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an information processing system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating an example of an agricultural product supply chain. [Diagram 3] FIG. 3 is a block diagram illustrating an example of a hardware configuration of the management server 1 shown in FIG. [Figure 4] FIG. 4 is a block diagram illustrating an example of a hardware configuration of the user terminal 2 shown in FIG. [Diagram 5] FIG. 5 is a block diagram illustrating an example of the software configuration of the management server 1 and the user terminal 2. As shown in FIG. [Figure 6] FIG. 6 is a schematic diagram illustrating an example of the configuration of the tracking database. [Figure 7] FIG. 7 is a schematic diagram for explaining the process of reading the automatic recognition code. [Figure 8] FIG. 8 is a schematic diagram for explaining the registration process of work information (trace information). [Figure 9] FIG. 9 is a schematic diagram illustrating a registration screen for work information at each tracking point. [Figure 10] FIG. 10 is a schematic diagram for explaining a warning display in the registration process of work information. [Figure 11] FIG. 11 is a schematic diagram for explaining the pairing process of the automatic recognition code. [Figure 12] FIG. 12 is a schematic diagram for explaining the browsing process of the tracking data. [Figure 13] FIG. 13 is a diagram showing an example of a pest control log. [Figure 14] FIG. 14 is a schematic diagram for explaining the invalidation process and reuse process of the automatic recognition code. [Figure 15] FIG. 15 is an example of a flowchart showing the flow of a registration process of work information. [Figure 16] FIG. 16 is an example of a flowchart showing the flow of the pairing process of the automatic recognition code. [Figure 17] FIG. 17 is an example of a flowchart showing the flow of a process for browsing tracking data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an information processing system according to an embodiment of the present disclosure will be described with reference to the drawings. In each of the attached drawings, identical or similar elements are given identical or similar reference symbols and names, and duplicate descriptions of identical or similar elements may be omitted in the description of the embodiment. Note that the contents shown in each drawing are merely examples for explaining the present embodiment, and are merely schematic examples for easy explanation of the present embodiment. The contents of each drawing may be modified or changed within the scope of no technical problem.

[0011] <System Overview> The information processing system according to this embodiment is a system for managing records (work information) relating to each process in the agricultural product supply chain.

[0012] The agricultural product supply chain refers to a series of steps from the production to the sale of agricultural products. The information processing system of this embodiment can be applied to the supply chains of various agricultural products produced by agriculture, such as grains, vegetables, fruits, tea, and livestock products, and the types of agricultural products handled in the agricultural product supply chain are not particularly limited. The agricultural product supply chain may include, for example, a process related to the production of agricultural products, a process related to the shipping of agricultural products, a process related to the sorting of agricultural products (sorting is the process of sorting and / or grading agricultural products based on predetermined evaluation items such as size, weight, shape, and color), a process related to the processing of agricultural products, and a process related to the distribution of agricultural products or processed products thereof (transportation, storage, sale, etc.).

[0013] In the information processing system of this embodiment, each process included in the agricultural product supply chain is set as a tracking point for recording work information. In this embodiment, the function of the information processing system will be described using the process flow shown in FIG. 2 as an example. In FIG. 2, the process from drug storage to receipt (receiving; a process in which the seller confirms receipt of the agricultural product) is set as a tracking point. In the process flow shown in FIG. 2, the process from drug storage to shipment to the producer is the producer's service, the process from receipt at the sorting facility to shipment from the sorting facility is the sorting facility's service, and the process from seller's warehousing to receipt is the seller's service. The workers (users) who perform services in the agricultural product supply chain are not limited to the example in FIG. 2. For example, a processor who processes the agricultural products, a transporter who transports the agricultural products, and the like may be involved in the supply chain as workers, and the process corresponding to the services performed by these workers may be included in the process flow of the agricultural product supply chain. The process flow in FIG. 2 is merely an example, and the process flow of the agricultural product supply chain to which the information processing system of this embodiment is applied is not particularly limited. The tracking points for recording work information may be set appropriately according to the agricultural products being handled and the actual conditions of the supply chain.

[0014] In the information processing system of this embodiment, automatic recognition codes are used to manage the recording, viewing, sharing, etc. of work information in each process of the agricultural product supply chain. Automatic recognition codes are electronic codes that apply automatic recognition technology (technology that mechanically reads data such as IDs and various information without human intervention), and as automatic recognition codes, one-dimensional codes (e.g., barcodes) in which predetermined information is encoded, two-dimensional codes (e.g., QR codes (registered trademark)), or wireless tags (IC tags) such as RFID can be used.

[0015] The automatic identification code is issued for a specific management object for each individual process or each process group (process group; a group of several processes determined by dividing the agricultural product supply chain). In other words, the automatic identification code is issued for each management object related to the agricultural product supply chain. The "specific management object" means an object, person, or place related to a single process or a process group. For example, in the example of the agricultural product supply chain in FIG. 2, examples of the automatic identification code include a pesticide code issued for each type of pesticide used in a field as a management object for pesticides, a field code issued for each field as a management object for fields where agricultural products are produced, and a container code issued for each container (shipping box, container, gift box, etc.) that contains the agricultural products after harvesting as a management object. The form of the management object and the automatic identification code may be set appropriately according to the agricultural product supply chain to which the system is applied, and is not limited to the example in FIG. 2. For example, an automatic recognition code corresponding to a producer, an automatic recognition code corresponding to each specified area (plot, ridge, etc.) into which a field is divided, an automatic recognition code corresponding to a processing plant, or an automatic recognition code corresponding to a storage facility may be issued.

[0016] When recording work information in each process, the worker reads the automatic recognition code of the management target corresponding to the process with a work terminal such as a smartphone, and a UI (User Interface) corresponding to the read automatic recognition code is output on the work terminal. The work information input through the UI is recorded in a database linked to the automatic recognition code. As shown in FIG. 2, in an agricultural product supply chain, there are multiple bases and multiple businesses, and multiple types of automatic recognition codes are issued according to the processes that construct the supply chain. In the information processing system of this embodiment, multiple automatic recognition codes are paired to build a correspondence between the automatic recognition codes, and multiple pieces of information on work results (hereinafter referred to as tracking data) that are linked and recorded for each automatic recognition code are aggregated and managed. With this information management method, information accumulated in the supply chain can be aggregated and made available for viewing, and the efficiency of information sharing between businesses can be improved. The tracking data accumulated in the supply chain may be made available for viewing by consumers by reading the automatic recognition code.

[0017] In this embodiment, for the sake of convenience, workers who perform specific tasks in the agricultural product supply chain, such as producers, sorting site staff, and sellers, are referred to as "users," and terminals used by these workers are referred to as "user terminals." However, true users of the services provided by the information processing system are not limited to workers who perform specific tasks in the agricultural product supply chain, and consumers who purchase agricultural products or processed products thereof may also be users who receive tracking data. Details of the information processing system of this embodiment are described below.

[0018] <Components of an information processing system> As shown in FIG. 1, the information processing system of this embodiment has a management server 1 and one or more user terminals 2. The user terminals 2 may be a plurality of terminals such as a terminal used by a producer, a terminal used by a person in charge of a sorting facility, and a terminal used by a seller. The management server 1 and the user terminals 2 are communicatively connected via a network NW. In this embodiment, the network NW is mainly assumed to be the Internet, but the network NW is not limited to the Internet and may be constructed, for example, by a public telephone line network, a mobile phone line network, a wireless communication network, Ethernet (registered trademark), or the like. In the information processing system, a consumer terminal 3 used by a consumer may be communicatively connected to the management server 1 via the network NW.

[0019] The management server 1 is an information processing device managed by an operating company that provides services related to the information processing system. The management server 1 may be a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing. The user terminal 2 is an information processing terminal owned by a user such as a producer, and user operation information regarding recording, viewing, etc. of work information in each process is input via the user terminal 2. The user terminal 2 is a mobile terminal such as a smartphone or tablet, and may be a general-purpose computer such as a workstation or a personal computer. The consumer terminal 3 is also various computers such as smartphones and tablets used by consumers, similar to the user terminal 2.

[0020] <Hardware configuration of Management Server 1> 3, the management server 1 includes at least a processor 10, a memory 11, a storage 12, a transmission / reception unit 13, an input / output device 14, etc., which are electrically connected to each other via a bus 16. Note that the illustrated configuration is an example, and the management server 1 may have other configurations.

[0021] The processor 10 is a computing device that controls the operation of the entire management server 1, controls the transmission and reception of data between each element, and performs information processing necessary for application execution and authentication processing. For example, the processor 10 is a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit). Each functional unit of the processing unit 100 of the management server 1 is realized by the processor 10 executing a program stored in the storage 12 and deployed in the memory 11.

[0022] The memory 11 includes a main memory configured with a volatile storage device such as a DRAM (Dynamic Random Access Memory), and an auxiliary memory configured with a non-volatile storage device such as a flash memory, an HDD (Hard Disc Drive), etc. The memory 11 is used as a work area for the processor 10, and also stores a BIOS (Basic Input / Output System) that is executed when the management server 1 is started, various setting information, and the like.

[0023] The storage 12 stores various programs such as application programs. A database storing data used in each process may be constructed in the storage 12. For example, a storage unit 120 described later is realized as a part of the storage area of ​​the memory 11 and / or the storage 12.

[0024] The transmission / reception unit 13 is a communication interface for the management server 1 to communicate with various information processing terminals such as the user terminal 2 and / or the consumer terminal 3 via a communication network. The transmission / reception unit 13 may further include a short-range communication interface such as Bluetooth (registered trademark) and BLE (Bluetooth Low Energy) and / or a USB (Universal Serial Bus) terminal.

[0025] The input / output device 14 is an information input device such as a keyboard, a mouse, etc., and an output device such as a display, etc. The input / output device 14 may include a touch panel that has both functions of inputting and outputting information, and may include a printer, a speaker, etc. as output devices.

[0026] A bus 16 is commonly connected to all of the above elements, and transmits, for example, address signals, data signals and various control signals.

[0027] <Hardware configuration of user terminal 2> 4, the user terminal 2 includes, for example, a processor 20, a memory 21, a storage 22, a transmitting / receiving unit 23, an input / output device 24, etc., which are electrically connected to each other via a bus 26. The above components of the user terminal 2 are similar to the processor 10, memory 11, storage 12, transmitting / receiving unit 13, input / output device 14, and bus 16 of the management server 1, and therefore description thereof will be omitted.

[0028] In addition to the above components, the user terminal 2 includes a reader 25 for reading the automatic recognition code. The reader 25 may be, for example, a camera or an RFID reader, and is a device capable of reading information encoded in the automatic recognition code. The reader 25 may be built into the user terminal 2, or may be externally connected to the user terminal 2.

[0029] The hardware configuration of the user terminal 2 shown in Fig. 4 is an example, and the user terminal 2 may have a configuration other than the example of Fig. 4. In addition, the consumer terminal 3 may have the same hardware configuration as the user terminal 2, and the description of the hardware configuration of the consumer terminal 3 will be omitted.

[0030] <Management Server 1 Functions (Software Configuration)> FIG. 5 is a block diagram illustrating functions (software configuration) implemented in the management server 1 and the user terminal 2. The management server 1 may include, for example, a code issuing unit 101, a code setting unit 102, a code reading processing unit 103, a registration processing unit 104, a judgment processing unit 1041, a pairing unit 105, a journal generating unit 106, a browsing processing unit 107, a code invalidation processing unit 108, a code reuse processing unit 109, and an information disclosure control unit 110. The storage unit 120 of the management server 1 may include various databases such as a code information storage unit 121, a user information storage unit 122, and a tracking database (DB) 123. Each functional unit included in the processing unit 100 of the management server 1 illustrated in FIG. 5 is illustrated as a functional unit realized by the processor 10 of the management server 1, but some or all of the various functional units may be realized in the processor of the user terminal 2.

[0031] The code information storage unit 121 is a database that stores information about the automatic recognition codes issued by the management server 1, and stores basic information associated with the automatic recognition codes issued for each management subject related to the agricultural product supply chain. Examples of the information about the automatic recognition codes include identification information (code ID) of the automatic recognition code, an image of the automatic recognition code, information indicating the issuer of the code, and information indicating the date and time of issue. The basic information associated with the automatic recognition code may include, for example, basic information of the management subject to which the automatic recognition code is assigned, and process setting information, and may also include other setting information related to the automatic recognition code. This basic information is stored in the code information storage unit 121 in association with the identification information of the automatic recognition code.

[0032] The process setting information of the automatic recognition code includes setting information indicating a process in which the work information can be registered by the automatic recognition code, and in each automatic recognition code, different processes are set according to the attributes of the managed object. More specifically, the process setting information may include setting information that specifies the first process managed by the automatic recognition code, setting information that specifies the last process managed by the automatic recognition code, setting information that specifies the process order, and the like. In addition, the process setting information may include setting information that specifies the items of the work information recorded in each process (hereinafter referred to as input items), and different input items may be set for each process. In other words, the input items can be set for each process and are not particularly limited. For example, in each process, as input items that are uniformly specified for each process, a timestamp when the work information is registered (i.e., the date and time when the work of each process is performed), location information of the user terminal 2 at the time of registration, and the like may be specified, and other input items specific to the process may be specified. In addition, the input items for each process may include required items and optional items. The process setting information may include setting information that specifies the process for performing the code pairing process, setting information that specifies the registration conditions for determining whether or not to allow registration of work information at a specified process, and the like.

[0033] The basic information of the automatic recognition code may include other setting information related to the automatic recognition code, such as setting information that specifies whether or not to invalidate the automatic recognition code after registration of work information in a specified process, setting information that specifies the process at which the automatic recognition code is invalidated, setting information that specifies whether or not reuse of the automatic recognition code is permitted, and setting information that specifies the initial process which is the first tracking point at which new work information can be accepted when reused.

[0034] The code information storage unit 121 may have storage areas divided according to the attributes of the codes. For example, in the case of the agricultural product supply chain shown in Fig. 2, the code information storage unit 121 may have a pesticide code information storage unit 1211 that stores information about pesticide codes, a farm field code information storage unit 1212 that stores information about farm field codes, and a utensil code information storage unit 1213 that stores information about utensil codes.

[0035] The pesticide code information storage unit 1211 stores basic information associated with the pesticide code for each issued code. The basic information associated with the pesticide code may include, for example, field identification information that identifies the field to which the pesticide is to be sprayed, and use condition information that indicates the use conditions of the pesticide. The field identification information may include information such as field identification information, the field name, information indicating the variety of agricultural products produced in the field, the field area, the planting date and time, and the planned harvest date. The use condition information may include a condition that specifies the number of times the pesticide is sprayed (the maximum number of times it can be sprayed), a condition that specifies the dilution ratio (lower limit and / or upper limit) when the pesticide is used, a condition that specifies the amount of spraying per unit area in one spraying (lower limit and / or upper limit), a condition that specifies the number of days before harvest (the number of days that must be secured between the last spraying date and the harvest date, i.e., the number of days indicating the period during which the pesticide is restricted from being used before harvest), and the like.

[0036] In addition to the above, the basic information of the pesticide code may include information such as the name of the agent, the name of the manufacturer that produced the pesticide, the active ingredients, the crop varieties to which the pesticide can be applied, and the names of the pests for which the pesticide is effective. Detailed information on the field and detailed information on the pesticide may be managed in a dedicated database, in which case only identification information specifying the field (field ID) and identification information specifying the pesticide (agent ID) may be associated with the pesticide code as basic information. Note that multiple types of pesticides are usually used in one field, and a pesticide code is issued for each pesticide used in the field.

[0037] In addition to the above, the basic information associated with the pesticide code may include process setting information that specifies the process managed by the pesticide code (the process in which work information can be registered by the pesticide code). In the example of the process flow in FIG. 2, the pesticide code has processes of chemical storage, taking out, spray preparation, spray completion, and final spray completion set as processes (tracking points) for registering work information, with chemical storage being the first process in the pesticide code and final spray completion being the final process in the pesticide code. The process managed by the pesticide code is not necessarily limited to the example in FIG. 2. As described above, the process setting information of the pesticide code may include information that specifies the input items to be recorded in each process. In the spray preparation process, the actual dilution value multiplication factor may be specified as an input item specific to the process, and in the spray completion process, the spray amount may be specified as an input item specific to the process. The process setting information of the pesticide code may be specified for each pesticide according to the type of pesticide, and different processes may be set for each pesticide.

[0038] The field code information storage unit 1212 stores basic information associated with the field code for each issued code. The basic information associated with the field code may include, for example, basic information about the field, and process setting information that specifies a process in which work information can be registered with the field code. Examples of the basic information about the field include, but are not limited to, field identification information, the name of the producer who manages the field, the field name, the field area, the cultivated area, the date and time of cultivation, the agricultural product to be produced (cultivated variety), and the planned harvest date.

[0039] In the example of the process flow in FIG. 2, the field code has the processes of final spraying completion, harvesting, and producer shipment set as tracking points, with final spraying completion corresponding to the first process in the field code and producer shipment corresponding to the final process in the field code. Of the processes set in the field code, the final spraying process may be specified as a process for pairing the field code with the pesticide code. The processes specified in the field code are not limited to the example in FIG. 2, and may include other work processes performed in the production process, post-harvest storage processes, post-harvest primary processing processes, etc. The process setting information of the field code may include information specifying the input items to be recorded in each process, as described above.

[0040] The utensil code information storage unit 1213 stores basic information associated with the utensil code for each issued code. The basic information associated with the utensil code may include, for example, basic information on the utensil and process setting information that specifies a process in which work information can be registered using the utensil code. Examples of the basic information on the utensil include, but are not limited to, identification information on the utensil, the type of the utensil, the material, the dimensions, and the weight. Note that the utensil used in one project of the agricultural product supply chain is not limited to one type, and multiple types of utensils may be used. Examples of the utensil include shipping boxes in which agricultural products are stored after harvesting, containers in which agricultural products harvested from multiple fields are stored together, and gift boxes used when agricultural products are delivered to sellers or consumers. When multiple types of utensils are used in the agricultural product supply chain, a utensil code is issued for each utensil.

[0041] In the utensil code, at least one of the following processes may be set as a tracking point: producer shipment, receipt at a sorting facility, sorting, shipment from the sorting facility, receipt by a seller, receipt by a seller, and sale. In the example of FIG. 2, the final tracking point in the agricultural product supply chain is "receiving", and the receiving process may be set for the utensil code. In the example of FIG. 2, the producer shipment process may be defined as a process of pairing the utensil code with the field code. In addition, when multiple types of utensils are used in one project, the process set for the utensil code may be divided into smaller categories according to the attributes of the utensils than in the example of FIG. 2. The process defined for the utensil code is not limited to the example of FIG. 2, and may include a process of repacking agricultural products into other utensils, a process of storing the agricultural products contained in the utensils in a warehouse, etc.

[0042] As described above, the process setting information of the utensil code may include information that specifies the input items to be recorded at each process. In the producer shipping process, shipping clock data such as the dimensions, weight, and number of agricultural products stored in the utensil may be specified as input items specific to the process. If there is a process related to the storage of agricultural products, data related to storage results such as the location information of the storage facility, the temperature and humidity of the storage facility, and the storage period may be specified as input items specific to the process.

[0043] The user information storage unit 122 stores information about users who use services related to the information processing system. The information about users is not particularly limited, and for example, the user information storage unit 122 may store user authority information in association with the user's identification information (user ID). The user authority information may include, for example, authority information regarding the issuance of an automatic recognition code, authority information regarding the recording of work information, authority information regarding the viewing of the recorded work information (tracking data), and the like. Examples of the authority information regarding viewing include information indicating the presence or absence of viewing restrictions, and information indicating data items that can be viewed when viewing restrictions exist.

[0044] The tracking DB123 is a database that stores work information recorded in association with an automatic recognition code. In the tracking DB123, tracking data may be managed for each automatic recognition code. For example, FIG. 6 is a schematic diagram illustrating a data structure of the tracking DB123. The tracking DB123 may have a pesticide tracking DB1231 that stores tracking data associated with a pesticide code for each pesticide code, a field tracking DB1232 that stores tracking data associated with a field code for each field code, and an implement tracking DB1233 that stores tracking data associated with an implement code for each implement code.

[0045] As shown in FIG. 6, in the data folder for each automatic recognition code, past history data and work information accumulated in an ongoing project may be stored separately. In this embodiment, a series of process flows from agricultural products or processed products thereof until they are sold is considered as one project, and past history data refers to tracking data accumulated in projects that have been executed in the past. Although the folder storing the past history data can be viewed, it is in a state in which new work information cannot be written, and tracking data accumulated in an ongoing project is stored in a folder in which writing is enabled. As described later, the automatic recognition code may be disabled after the work information in a specific process is registered, and after this disabling process, the automatic recognition code may be reenabled for reuse in a new project. When the automatic recognition code is reused, a new folder in which writing of work information is enabled is added, and a data structure as shown in FIG. 6 is constructed.

[0046] The tracking DB 123 may have a pairing information storage unit 1230 that stores pairing information generated by the pairing unit 105 described later. The pairing information is information indicating a correspondence between an automatic recognition code as a parent (hereinafter referred to as a parent code) and an automatic recognition code as a child (hereinafter referred to as a child code), and in the tracking DB 123, the tracking data of the child code (work information recorded in association with the child code) is also associated with the parent code and managed based on this pairing information. Note that it is also possible to pair an automatic recognition code set as a parent code with another automatic recognition code as a child code, and in this case, not only the tracking data of the child code but also the tracking data of the grandchild code paired with the child code is associated with the automatic recognition code newly set as a parent code.

[0047] In Fig. 6, the correspondence between paired automatic recognition codes is indicated by arrows. Specifically, the code of the object α (parent code) is linked to the tracking data of the code of the field 1 (child code) and the tracking data of the codes of the pesticides A and B (grandchild codes) associated with the code of the field 1. By constructing the above-mentioned data structure through the pairing process of the automatic recognition codes, it is possible to identify not only the tracking data of the read code but also the tracking data of the codes (parent code, child code, and / or grandchild code) associated with the read code by simply reading any one of the paired automatic recognition codes.

[0048] The code issuing unit 101 executes a process of issuing an automatic recognition code corresponding to a predetermined management target in the agricultural product supply chain. For example, the code issuing unit 101 issues an automatic recognition code by specifying detailed code information including type information indicating the type of management target, code identification information (code ID), information indicating the person who issued the code, and a timestamp indicating the time of code issuance. The code issuing unit 101 may generate an automatic recognition code in a predetermined format determined according to the type of management target.

[0049] When issuing an automatic recognition code, the code issuing unit 101 may receive a designation of the type of automatic recognition code to be issued (whether it is an agricultural code, a field code, or an implement code) from the issuing person requesting the issuance of the code. Alternatively, the type of automatic recognition code that can be issued may be specified according to the person requesting the issuance of the code. Furthermore, when issuing an automatic recognition code, the code issuing unit 101 may receive a designation of a managed object to which the code to be issued is to be attached from the issuing person, and may receive, for example, an input operation of identification information of the managed object, various basic information of the managed object, and the like. The designation of the managed object and the input of information related to the managed object may be automatically input by reading a code originally attached to the managed object (for example, a barcode attached to a package of an agricultural chemical).

[0050] The automatic recognition code can be issued by a plurality of different issuing personnel. For example, the automatic recognition code may be issued by an administrator of the information processing system, or may be issued as necessary by each user involved in the agricultural product supply chain, such as a producer, a person involved in a sorting facility, or a seller. In particular, the pesticide code may be issued by a manufacturer that produces the pesticide, and may be affixed to the pesticide container in advance at the time of production.

[0051] The code setting unit 102 executes a process of setting basic information (basic information of the management object, process setting information, etc.) for the automatic recognition code. The setting of the automatic recognition code may be executed at any timing before, during, or after the issuance of the code. For example, basic information determined in advance according to the type of management object may be defined before the issuance of the code, and the basic information may be automatically associated with the code when the code is issued. In addition, when the code is issued, the basic information of the code may be defined by accepting a setting operation related to the code from an issuing person. Furthermore, even after the code is issued, the setting or updating process of the basic information may be executed in response to a request from a user who has the authority to access the management server 1. The person in charge of setting the automatic recognition code may be the system administrator or each user involved in the supply chain. The setting of the basic information related to one automatic recognition code is not necessarily executed by one qualified person, and multiple users who have the authority may be able to update the basic information and / or various setting information set in the automatic recognition code.

[0052] The code setting unit 102 outputs a setting screen for the automatic recognition code in response to a request from the setting person. Then, the code setting unit 102 accepts setting operations such as basic information of the management target to be associated with the automatic recognition code, designation of the process to be managed by the code (designation of process setting information), and designation of input items (data items of work information) to be registered in each process via the setting screen. After that, the code setting unit 102 generates basic information and process setting information for the automatic recognition code based on the information accepted from the setting person, and specifies this information in association with the automatic recognition code.

[0053] The code setting unit 102 may execute a process for defining other setting information related to the automatic recognition code. For example, it may accept a setting related to disabling the automatic recognition code. Here, disabling the automatic recognition code means disabling the recording (new registration) of new work information in the tracking database corresponding to the automatic recognition code. In other words, when the automatic recognition code is disabled, the tracking data can be viewed, but new work information cannot be written.

[0054] The code setting unit 102 accepts a selection of whether to invalidate the automatic recognition code at a predetermined process, a selection of a process to execute the invalidation, etc. from the person in charge of setting, and specifies setting information corresponding to the selection operation in association with the code. When accepting the selection of a process to execute the invalidation, the code setting unit 102 may present a process flow set in the project or a list of processes that can be invalidated, and accept the selection of a process to execute the invalidation from among the presented processes. The setting regarding the invalidation can be performed for each automatic recognition code, and different processes may be set as invalidation processes depending on the type of code. When the setting of the invalidation is specified, the automatic recognition code is automatically invalidated after the work information is registered in the specified process. Note that the invalidation of the automatic recognition code may be executed according to a manual operation by the user (an input operation requesting the invalidation). The code setting unit 102 may accept a selection by the person in charge of setting as to whether to execute the invalidation automatically.

[0055] The code setting unit 102 may also receive settings related to the reuse of automatic recognition codes. Here, the reuse of automatic recognition codes means setting a new folder in which the recording of new work information is enabled for the tracking DB of an automatic recognition code in a disabled state, and re-enabling the registration (writing) of work information using the automatic recognition code. In other words, when the reuse process is applied to an automatic recognition code in a disabled state, it becomes possible to register (write) work information related to a new project.

[0056] The code setting unit 102 accepts a selection from the person in charge of setting whether or not to permit reuse of the automatic recognition code, and specifies setting information according to the selection operation in association with the code. When permission of reuse is selected, the code setting unit 102 may accept designation of a process for executing reuse, designation of an initial process for starting registration of new work information after reuse, and the like. When accepting the selection of the process for executing reuse and the initialization process, the code setting unit 102 may present a process flow set in the project or a list of process candidates that can be set, and accept the person in charge of setting a selection from among the presented processes. Settings related to reuse can be performed for each automatic recognition code, and different processes may be set as initialization processes, etc., depending on the type of code.

[0057] In response to reading any one of the automatic recognition codes, the code reading processing unit 103 outputs a UI corresponding to the basic information of the one of the automatic recognition codes that has been read. The automatic recognition code reading process is executed before recording and viewing of work information (tracking data), and the UI output by the reading process is used for recording and viewing of the work information. FIG. 7 is a schematic diagram showing an example of the automatic recognition code reading process. The automatic recognition code reading process may be executed by using, for example, a dedicated application program, in which case the user starts the application program and inputs a user ID. The application program may be a program provided on the Internet, or may be a downloadable program.

[0058] As shown in (a)-(b) of Fig. 7, when an automatic recognition code attached to a predetermined management target is read using the user terminal 2, the code reading processing unit 103 receives the read information of the automatic recognition code transmitted from the user terminal 2. Then, the code reading processing unit 103 reads basic information of the read automatic recognition code (hereinafter, may be referred to as a read code) based on the read information, generates a UI corresponding to the read code, and transmits it to the user terminal 2 ((c) of Fig. 7). If work information has already been registered for the read code, the code reading processing unit 103 may refer to tracking data corresponding to the read code when outputting the UI, and reflect the work information recorded so far in association with the read code in the display area of ​​the UI.

[0059] The UI generated by the code reading processing unit 103 presents information according to the read code, and a different UI may be output according to the type of the automatic recognition code, the registration status of work information in the project, and the like. The form of the generated UI is not particularly limited. For example, the code reading processing unit 103 may present on the UI a display area for accepting various input operations by the user. Specifically, the display area for accepting input operations may be provided with an operation button for accepting a request to view work information accumulated in an ongoing project, an operation button for accepting a request to register work information, an operation button for accepting a request to pair an automatic recognition code, an operation button for accepting a request to cancel pairing, an operation button for requesting the presentation of information on other automatic recognition codes associated with the read code, an operation button for accepting a request to view history information of past projects, an operation button for accepting a request to invalidate or reuse an automatic recognition code, and the like.

[0060] The code reading processing unit 103 may also present, on the UI screen, a display area showing information about the read code, a display area showing the progress of the project (the registration status of work information), a display area showing basic information of the managed object, and the like. In the display area showing the progress of the project, as shown in FIG. 7(c), the current process for which work information has been registered may be displayed, or information showing the process which is the next tracking point may be displayed. In order to show the progress, the code reading processing unit 103 may present, on the UI, tracking points (processes) included in the project in the form of a flowchart. In this flowchart, the tracking points corresponding to the read code may be presented in a different form from tracking points managed by other codes, or only the processes managed by the read code may be presented. In addition, the display area showing the basic information of the managed object may present an operation button for accepting an update of the basic information, and addition, modification, etc. of the basic information may be performed via the UI output by reading the automatic recognition code.

[0061] The registration processing unit 104 accepts input of work information for a process related to the object to be managed by the read code via a UI output by reading the automatic recognition code, and executes a process of linking the work information to the read code and recording it in a tracking database.

[0062] Fig. 8 is a schematic diagram showing an example of a work information registration process. As shown in Fig. 8(a), when a user inputs operation information requesting recording of work information via the UI (tapping the "Add tracking data" button), the registration processing unit 104 refers to the process setting information associated with the read code, the registered tracking data, etc., identifies the next process (tracking point) for registering the work information and the input items set for that process, and presents an input form corresponding to the identified process on the UI (Fig. 8(b)).

[0063] The input form (work information registration screen) presents input items set for each process, and different input forms can be output depending on the process for which work information is to be registered. FIG. 8(b) shows an example of an input form for the "take-out" process set in the pesticide code. FIG. 9 shows other input forms corresponding to each process. If the next process for adding work information is branched, the registration processing unit 104 may present candidates for the next process as shown in FIG. 9(c) and allow the user to select the process for registering the work information. In this case, the registration processing unit 104 outputs an input form corresponding to the selected process based on the user's operation to select the next process.

[0064] The input format of the work information is not particularly limited. For example, the work information may be input in a selection format such as a text format, a radio button, a drop-down list, a check box, or a calendar. The type of input control for each input item may be arbitrarily specified by the person in charge of setting the input item. The work information may also be automatically input. For example, when the registration processing unit 104 receives operation information of a user requesting the recording of work information, the registration processing unit 104 may acquire current location information of the user terminal 2 and register the current location information as work information. In this case, the current location information of the user terminal 2 may be acquired by a known method such as a GPS (Global Positioning System). In addition, the time stamp may also be acquired automatically, and when the registration processing unit 104 receives an instruction to register work information from the user (tapping the "OK" button in FIG. 8(b)), the registration processing unit 104 may automatically acquire the date and time of receiving the instruction and register it as work information in the time stamp.

[0065] In addition, information acquired by an external device may be automatically input as work information into an input form. For example, in a process such as shipping or sorting, when work such as weighing and evaluation (grading) of agricultural products is performed using a predetermined machine such as a weighing scale or a sorting machine, the registration processing unit 104 may acquire data recorded by such a machine and automatically input the data into an input form of the UI. Also, in a process of storing agricultural products, storage environment data such as temperature and humidity may be recorded by a recording device such as a logger, and the registration processing unit 104 may acquire data recorded by such a recording device and automatically input the data into an input form of the UI. The method of acquiring the recorded data from the external device as described above is not particularly limited. For example, the recorded data of the external device may be acquired by API linkage, or the recorded data may be acquired by communication with the external device.

[0066] When the input of the work information into the input form is completed (by tapping the "OK" button in FIG. 8(c)), the registration processing unit 104 receives the work information transmitted from the user terminal 2 via the UI, and records the work information in the tracking DB 123 by linking it to the automatic recognition code read when the UI is output. If the read code is a pesticide code, the registration processing unit 104 records the work information related to the pesticide according to the input items in each process, such as the pesticide dilution ratio, the spray amount (unit: L / 10ac), the number of sprays, and a time stamp, in the pesticide tracking DB 1231 by linking it to the pesticide code. The registration processing unit 104 automatically counts the number of sprays based on the accumulated tracking data. If the read code is a field code, the registration processing unit 104 records the work information in the process set in the field code, such as work information related to the harvesting of the agricultural crops and the shipment of the agricultural crops, in the field tracking DB 1232 by linking it to the field code. If the read code is an utensil code, the registration processing unit 104 links the work information for the process set in the utensil code, such as information on the grade of the agricultural produce determined in the sorting work and work information related to the distribution of the agricultural produce, to the utensil code and records it in the utensil tracking DB 1233.

[0067] When the registration of work information in the process corresponding to the received work information is completed, the registration processing unit 104 activates the next tracking point. In other words, when the registration of work information in the current process is completed, the registration processing unit 104 executes a process to permit the registration of work information in the next process (a process to make it possible to input work information).

[0068] The registration processing unit 104 may include a determination processing unit 1041 that, when registering work information, determines whether or not the work information received from the user terminal 2 satisfies a predetermined registration condition. In this case, if the work information satisfies the registration condition, the determination processing unit 1041 links the work information to the reading code, records it in the tracking DB 123, and activates the next tracking point. On the other hand, if the work information does not satisfy the registration condition, the determination processing unit 1041 outputs warning information to notify that the input work information is incompatible or that the work information cannot be accepted.

[0069] For example, when the input items set for a given process include required items and optional input items, the determination processing unit 1041 may determine whether or not work information corresponding to the required items has been input. When a registration instruction is sent from the user terminal 2 without the required items being input, a warning indicating that the required items have not been input may be displayed on the user terminal 2. In addition, a registration condition may be set to limit the points at which work information can be registered. In this case, the determination processing unit 1041 may determine whether the current location information of the user terminal 2 is within the range of the registerable points, and if the current location is outside the range of the condition, may output a warning indicating that the registration of the work information cannot be accepted. In the process of performing the pairing process of the automatic recognition code, a condition may be set to allow the registration of the work information after pairing. In this case, when the determination processing unit 1041 receives a registration request for work information in a state in which the pairing process has not been performed, it may output a warning to notify the user to perform pairing first. The registration condition may be determined according to the attributes of the process, and is not particularly limited. When a predetermined registration condition is set for the process for which a registration request has been received, the code reading processing unit 103 may present the registration condition as remark information in the input form to be output.

[0070] If the read code is a pesticide code, the determination processing unit 1041 accepts input of work information related to the pesticide via a UI output by reading the pesticide code, and determines whether the input work information satisfies the use conditions of the pesticide based on the use condition information and field identification information associated with the pesticide code. If the work information related to the pesticide satisfies the use conditions, the determination processing unit 1041 links the input work information to the pesticide code and records it in the pesticide tracking DB 1231, and activates the next tracking point. On the other hand, if the work information related to the pesticide does not satisfy the use conditions, the determination processing unit 1041 outputs warning information indicating that the input information is non-compliant.

[0071] The warning information related to the pesticide code may include, for example, one or more of the following: a warning indicating that the dilution ratio entered as work information does not comply with the usage conditions; a warning indicating that the number of applications does not comply with the usage conditions; a warning indicating that the input date of the work information does not comply with the conditions regarding the number of days before harvest, which indicates the restricted period for pesticide use before harvest; and a warning indicating that the pesticide to be sprayed is not suitable for the target crop in the field.

[0072] Specifically, (a)-(b) in FIG. 10 are examples of warning information output in the "spray preparation" step. If the dilution ratio input by the user in the spray preparation step does not fall within the range of the use conditions specified for the target pesticide, the judgment processing unit 1041 outputs warning information notifying that the dilution ratio is different. Also, (c)-(d) in FIG. 10 are examples of warning information when the "number of applications" reaches the number of applications specified in the use conditions. When the judgment processing unit 1041 accepts registration of work information in the "spray completion" step, it may update the cumulative number of applications along with the recording of the work information, and determine whether the updated number of applications has reached the number of applications specified in the use conditions. Then, when the cumulative number of applications reaches the upper limit specified in the use conditions, it outputs warning information as shown in FIG. 10(d). When the judgment processing unit 1041 receives a request to register work information for performing new spraying after the number of sprayings has reached the upper limit (for example, when a request to transition to a process other than completion of final spraying, or a request to register work information) the judgment processing unit 1041 may output warning information indicating that the number of sprayings has already reached the upper limit and does not comply with the usage conditions.

[0073] The judgment regarding the number of days before harvest may be performed in a process before pesticide spraying (e.g., chemical storage, removal, preparation for spraying, etc.), or may be performed after the process of completing the final spraying. For example, if the basic information of the pesticide code, the input work information, or the recorded tracking data includes information on the planned harvest date, the judgment processing unit 1041 may compare the number of days from the current date to the planned harvest date with the number of days before harvest specified in the usage conditions to judge whether or not the work information in the process before pesticide spraying can be accepted. Then, if the number of days from the current date to the planned harvest date meets the usage conditions for the number of days before harvesting, the registration of the work information is accepted, and if the number of days from the current date to the planned harvest date does not meet the usage conditions for the number of days before harvesting, warning information is output to the effect that the condition for the number of days before harvesting is not met.

[0074] Furthermore, the determination processing unit 1041 may execute a determination regarding the number of days before harvest when performing pairing processing between the field code and the pesticide code. Specifically, the determination processing unit 1041 may refer to tracking data of each pesticide code associated with the field code and determine whether or not the date when pairing is performed has passed the pesticide use restriction period (number of days before harvest). When any of the pesticide codes associated with the field code does not satisfy the condition of the number of days before harvest, warning information regarding the number of days before harvest may be output together with information of the pesticide code that does not satisfy the condition. Furthermore, when receiving work information in the harvesting process, the determination processing unit 1041 may refer to tracking data of each pesticide code associated with the field code and determine whether or not the condition of the number of days before harvest for all the corresponding pesticides is satisfied. Alternatively, for each pesticide code associated with a field code, acceptance of work information in the "harvest" process may be disabled until the condition for the number of days before harvest is met, and acceptance of work information in the "harvest" process may be enabled once the condition for the number of days before harvest for all pesticides has been met.

[0075] In response to reading a plurality of automatic recognition codes, the pairing unit 105 generates pairing information indicating a correspondence between the read automatic recognition codes. Specifically, the pairing unit 105 generates pairing information indicating a correspondence between the child codes and the parent codes by reading an automatic recognition code as a parent code and an automatic recognition code as a child code, and links the work information linked to the child code to the parent code.

[0076] FIG. 11 is a schematic diagram showing an example of pairing processing. As shown in FIG. 11(a), the pairing unit 105 may accept a request for pairing processing via a pairing button presented on a screen of a UI output by reading any of the automatic recognition codes. In this case, the pairing unit 105 defines the automatic recognition code read to output the UI of FIG. 11(a) as a parent code. After requesting pairing processing, the user reads one or more automatic recognition codes to be associated with the parent code by the user terminal 2 (FIG. 11(b)), and the pairing unit 105 defines the read automatic recognition code as a child code based on the read information received from the user terminal 2. Then, the pairing unit 105 presents information on the read child code on the screen of the UI, and accepts operation information of the completion of reading from the user terminal 2 (FIG. 11(c), tapping the "Done" button). After that, the pairing unit 105 generates pairing information indicating the correspondence between the child code and the parent code, and links the work information linked to the child code to the parent code.

[0077] The generated pairing information includes identification information of each paired automatic recognition code, information indicating the parent-child relationship of the automatic recognition codes, etc., and when a child code is associated with a grandchild code, it may also include identification information of the grandchild code and information indicating the correspondence from the parent code to the grandchild code, etc. This pairing information is stored and managed in the pairing information storage unit 1230.

[0078] In the case of the project illustrated in FIG. 2, the pairing unit 105 reads the field code and the pesticide code corresponding to at least one pesticide used in the field, generates first pairing information with the field code as a parent code and the pesticide code as a child code, and links the work information linked to the pesticide code to the field code. When multiple pesticides are used in the field, the pairing unit 105 reads the pesticide codes of all the pesticides used in the field as child codes to generate the first pairing information. In addition, the pairing unit 105 reads the field code and the utensil code attached to the utensil that contains the agricultural products harvested in the field, generates second pairing information with the utensil code as a parent code and the field code as a child code, and links the work information linked to the field code to the utensil code. In this case, if the agricultural chemical code is associated with the field code, the agricultural chemical code is defined as a grandchild code. Then, the pairing unit 105 executes a process of linking not only the tracking data linked to the field code, but also the tracking data linked to the grandchild agricultural chemical code to the utensil code.

[0079] The timing of executing the pairing process is not particularly limited. The user may be allowed to request the execution of the pairing process at any step. Pairing may be executed before tracking data is registered in the child code (or grandchild code), or during the accumulation process of tracking data in the child code (or grandchild code). If new work information is registered in the child code (or grandchild code) after the pairing process, the work information is also linked to the parent code based on the pairing information. Alternatively, a predetermined step such as a final spraying completion step (step of generating first pairing information) or a producer shipping step (step of generating second pairing information) may be specified as a step for executing the pairing process. In this case, the execution of the pairing process may be used as a trigger to activate the next tracking point.

[0080] The pairing unit 105 may execute a pairing cancellation process to cancel the correspondence between the parent code and the child code. For example, when shipping boxes from a plurality of farm fields are mixed and managed in one container, the pairing unit 105 generates pairing information with the utensil code attached to the one container as the parent code and the utensil code attached to the shipping box of each farm field as the child code. After management in the container, the mixed state may be canceled in a predetermined process to shift to management in individual shipping boxes. In this case, the pairing unit 105 cancels the correspondence between the parent code and the child code. At this time, the pairing unit 105 may execute a process to transfer the tracking data accumulated in the parent code in the paired state to the child code after the pairing is canceled. The pairing cancellation process may be executable in any process according to a selection operation by the user, or a process for canceling the pairing may be specified in advance.

[0081] The log generation unit 106 executes a process of aggregating tracking data recorded in multiple automatic recognition codes to generate a log. For example, in an agricultural product supply chain, a pest control log that summarizes the spraying history of multiple pesticides used in a field may be required. In the information processing system of this embodiment, it is possible to generate a pest control log by aggregating the spraying history of multiple pesticides simply by reading the field code set as the parent code.

[0082] For example, when the field code is read by the user terminal 2, the log generating unit 106 identifies one or more pesticide codes associated with the field code and tracking data (work record) recorded using the pesticide codes based on pairing information identified by reading the field code. Then, the log generating unit 106 generates a pest control log showing the pesticide spray history in the field based on the tracking data of the identified pesticide code. Fig. 13 is an example of a pest control log generated by the log generating unit 106, and the pest control log includes spray history information for each pesticide composed of tracking data of the pesticide code, and may also reflect other tracking data such as basic information of the field code and harvest date linked to the field code and recorded.

[0083] The timing of generating the pest control journal is not particularly limited, and may be generated at any step according to a selection operation by the user, or the step of generating the pest control journal may be predefined. For example, the harvesting step may be defined as the step of generating the pest control journal, and in this case, the journal generating unit 106 may automatically generate the pest control journal when the registration of work information in the harvesting step is used as a trigger. In the above, the case where the pest control journal is generated by reading the field code is exemplified, but the pest control journal may be generated by reading the implement code associated with the field code. In addition, the timing of outputting (transmitting to the user terminal 2) the generated pest control journal is not particularly limited. The pest control journal may be transmitted to the user terminal 2 at any step according to a request from the user, or the step of providing the pest control journal to the user terminal 2 may be predefined.

[0084] The viewing processing unit 107 executes processing related to the user's viewing of the work information recorded in association with the automatic recognition code. For example, a button (for example, a "Trace (view)" button in FIG. 12(a)) for accepting a request to view the work information associated with the read code may be provided on the screen of the UI output by reading the automatic recognition code. When the viewing processing unit 107 accepts a request to view the work information from the user terminal 2 via the UI, it refers to the tracking data associated with the read code and displays a viewing screen on the UI showing the work information recorded so far with the read code.

[0085] When there is another automatic recognition code paired with the reading code, the viewing processing unit 107 may output not only the work information of the reading code but also the work information of the other automatic recognition code associated with the reading code on the viewing screen. For example, the viewing processing unit 107 may receive a viewing request for tracking data from a user via a UI output in response to reading a parent code, and display on the screen of the UI the work information associated with the parent code corresponding to the viewing request and / or the work information associated with the child code associated with the parent code. FIG. 12 is a schematic diagram showing an example of viewing processing in a state where pairing information exists. The reading processing unit 103 may receive a viewing request for tracking data of a child code and a selection of a child code to be viewed (FIG. 12(b)) via a UI output by reading a parent code (FIG. 12(a)), and display a list of work information associated with the selected child code on the screen of the UI (FIG. 12(c)). Note that while Figure 12 shows an example of outputting only the tracking data of the child code, the viewing processing unit 107 may also display on the UI screen together the work information linked to the parent code and the work information linked to the child code and / or grandchild code.

[0086] When a viewing restriction is set for a part of the tracking data in the authority information of the user, the viewing processing unit 107 may execute a process of extracting information corresponding to the authority information of the user from the tracking data. Specifically, the viewing processing unit 107 extracts information corresponding to the authority information from the work information linked to the parent code and / or the work information linked to the child code associated with the parent code based on the authority information of the user who read the parent code, and displays the information on the UI screen.

[0087] After the work information related to the predetermined process is registered, the code invalidation processing unit 108 executes an invalidation process to invalidate the recording of new work information in the tracking DB 123 corresponding to the automatic recognition code. The predetermined process to execute the invalidation is not particularly limited, and may be, for example, a process corresponding to a terminal tracking point set in a project of a product supply chain. The predetermined process to execute the invalidation may be a process set in advance as a process to invalidate the automatic recognition code. The process to execute the invalidation may be a different process for each code depending on the attribute or process setting information of the automatic recognition code. For example, the field code and the pesticide code may be invalidated after the work information is registered in the producer shipping process, and the utensil code may be invalidated in the receiving process which is the terminal tracking point. The invalidation process of the automatic recognition code may be executed manually based on an instruction from a user, or may be executed automatically triggered by the registration of work information in a predetermined process.

[0088] If pairing information is set in the automatic recognition code, the code invalidation processing unit 108 may execute a process of invalidating the child code and / or grandchild code associated with the parent code together with the parent code when invalidating the parent code. Note that it is possible to read an automatic recognition code in an invalid state, and when an automatic recognition code in an invalid state is read, it is possible to view the tracking data recorded in association with the automatic recognition code, even if it is not possible to register new work information.

[0089] FIG. 14 is a schematic diagram showing an example of a UI that is output when a disabled automatic recognition code is read. In the UI of FIG. 14, the "Add Tracking Data" button for registering new work information and the "Pairing" button for executing pairing of the automatic recognition code are disabled. On the other hand, the operation buttons for viewing the tracking data are enabled (for example, the "Trace (view)" button (a button for viewing the tracking data of the most recent project), the "Child Code (a button for checking the child codes and grandchild codes associated with a code)" button, and the "Past History (a button for viewing tracking data for past projects)).

[0090] The code reuse processing unit 109 accepts a request for reuse of an automatic recognition code in a state in which recording of new work information is disabled, sets a new folder in which recording of new work information is enabled in the tracking DB 123 corresponding to the automatic recognition code, and executes processing to enable the automatic recognition code. The request for reuse of an automatic recognition code may be accepted, for example, via a dedicated button (for example, the "Reuse" button in FIG. 14) presented on a UI that is output by reading the automatic recognition code to be reused.

[0091] When the automatic recognition code for which a request for reuse has been received is associated with another automatic recognition code (when they are paired), the code reuse processing unit 109 may execute a process of validating the automatic recognition code for which a request for reuse has been received (e.g., a parent code) and also validating the other automatic recognition codes (e.g., a child code and / or a grandchild code) associated with the automatic recognition code.

[0092] When validating an automatic recognition code, the code reuse processing unit 109 may set an initial step, which is the first tracking point at which new work information can be accepted during reuse. The initial step may be different depending on the management target of the automatic recognition code. For example, when reusing an agricultural chemical code, the code reuse processing unit 109 may set "chemical storage" as the initial step of the agricultural chemical code, when reusing a field code, may set "final spraying completed" as the initial step of the field code, and when reusing an utensil code, may set "producer shipment" as the initial step of the utensil code. Which step is to be the initial step is determined based on the step setting information of each automatic recognition code.

[0093] The code reuse processing unit 109 may execute a process of canceling the pairing set in the automatic recognition code during reuse processing. Alternatively, the code reuse processing unit 109 may take over the pairing information and reapply it to a new folder in a new tracking DB 123, so that the correspondence between the automatic recognition codes is maintained even after reuse. Even when an automatic recognition code is reused, the link between the automatic recognition code and past history (tracking data recorded in the past) may not be released, and past tracking data may be made viewable. For example, after reuse of an automatic recognition code, it may be possible to view tracking data in past projects recorded before reuse from a "past history" button shown in FIG. 14.

[0094] The information disclosure control unit 110 executes processing related to information disclosure to consumers. Specifically, the information disclosure control unit 110 presents a list of input items for work information stored in the tracking DB 123, accepts a selection of information to be disclosed to consumers from the list, and generates consumer disclosure information. While tracking data collected in the agricultural product supply chain includes information that should be shared between users who are members of the supply chain, it also includes information that is undesirable to be presented to consumers (e.g., pesticide spray history, pest control log, etc.). Therefore, in the information processing system of this embodiment, information scrutinized from the tracking data accumulated in the agricultural product supply chain is provided as disclosure information to consumers.

[0095] The timing of setting the information to be disclosed to consumers and the person in charge of setting it are not particularly limited. For example, the selection and setting of the information to be disclosed to consumers may be performed by the seller at the stage when the project has progressed to the final tracking point and the utensil code to which the final tracking point has been set is invalidated. Alternatively, the selection and setting of the information to be disclosed to consumers may be performed by a user such as a system administrator, a project manager, a producer, or a person involved in the field when the automatic identification code is set or at any stage during the progress of the project.

[0096] Also, information that can be disclosed to consumers may be set for each automatic recognition code. If the automatic recognition codes are in a paired state, the selection and setting of information that can be disclosed to consumers may be executed collectively for the automatic recognition codes that have a corresponding relationship established by the pairing information. The information disclosure control unit 110 recognizes the automatic recognition code designated by the setting person, or the designated automatic recognition code and another automatic recognition code that is associated with the code, and then identifies the input items of the work information for each process that are set in the automatic recognition code, and presents a list of these input items to the terminal of the setting person. Then, the information disclosure control unit 110 accepts the designation of information (input items) that can be disclosed to consumers or the designation of information (input items) that should not be disclosed via the list, and specifies information disclosure settings that indicate data items that can be disclosed to consumers.

[0097] After the registration of the work information at the end tracking point is completed, the information disclosure control unit 110 extracts tracking data corresponding to the data items specified in the information disclosure setting from the tracking data stored in the tracking DB 123 based on the information disclosure setting. Then, based on the extracted tracking data, consumer disclosure information to be provided for viewing by consumers is generated. The configuration of this consumer disclosure information is not particularly limited, and for example, the consumer disclosure information may include agricultural product PR information, agricultural product images, agricultural product producer details such as comments from the producer who produced the agricultural product, producer information such as the place of origin and the date and time of shipment from the producer, sorting information such as the grade of the agricultural product, storage history, and the date and time of shipment from the sorting facility, seller information, and sales information such as the date and time of arrival at the seller. In addition, the format of the consumer disclosure information is not particularly limited, and for example, the consumer disclosure information may be realized as a format embedded in a Web page (for example, a script (program) written in JavaScript or the like).

[0098] The information disclosure control unit 110 may link the generated consumer disclosure information to a predetermined automatic recognition code and record it in the tracking DB 123. The automatic recognition code to which the consumer disclosure information is linked may be, for example, a utensil code attached to a utensil used when providing agricultural products to consumers. The automatic recognition code to which the consumer disclosure information is linked is invalidated before being provided to the consumer. The consumer may be able to access a web page on which the consumer disclosure information is posted by reading the invalidated automatic recognition code with the consumer terminal 3.

[0099] <Functions of user terminal 2> 5, the user terminal 2 may include a display control unit 201 and an operation information receiving unit 202. The display control unit 201 receives information about the UI, information processing results, and the like transmitted from the management server 1, and then executes a process of reflecting the received data on the display unit of the user terminal 2. The operation information receiving unit 202 receives operation information input by the user to the UI displayed on the user terminal 2, and transmits the operation information to the management server 1. In addition, when the reader 25 reads the automatic recognition code in response to the user's operation of the user terminal 2, the operation information receiving unit 202 receives read information of the automatic recognition code and transmits it to the management server 1.

[0100] <An example of information processing method> Next, an example of information processing executed by the information processing system of this embodiment will be described with reference to the flowcharts illustrated in FIGS.

[0101] Fig. 15 is a flow chart illustrating an example of the flow of the task information registration process. When attempting to register task information, the user first launches a dedicated application program and inputs his / her own user ID. The code reading processing unit 103 accepts the input of the user ID and identifies the user who is the subject of the operation based on the user ID (step SQ101 in Fig. 15). Next, when the user operates the user terminal 2 to read an automatic recognition code associated with any of the managed objects (step SQ102), the code reading processing unit 103 generates a UI corresponding to the basic information of the read automatic recognition code and sends it to the user terminal 2 (step SQ103).

[0102] Next, the registration processing unit 104 accepts input of work information from the user via the UI output by the code reading processing unit 103 (step SQ104). At this time, an input form corresponding to the process for accepting the work information is displayed on the UI based on the process setting information of the automatic recognition code. The input form presents input items (mandatory items and optional items) set for each process, and the current location information of the user terminal 2 and automatically input items such as a timestamp may be automatically acquired as work information. Data acquired by an external device (a weighing machine, a fruit sorting machine, a thermometer, etc.) may also be automatically reflected in the input form through API linkage or communication.

[0103] In step SQ104, the registration processing unit 104 may determine whether the input work information satisfies a predetermined registration condition. For example, in the case of work information related to a pesticide code, the input work information may determine whether it satisfies the use conditions of the pesticide. Specifically, it may determine whether the dilution ratio is within the range specified in the use conditions, whether the number of applications has reached the upper limit specified in the use conditions, whether the interval between the input date of the work information and the planned harvest date satisfies the condition of the number of days before harvest, whether the pesticide is suitable for the crop in the target field, and so on. If the work information does not satisfy the registration conditions, the registration processing unit 104 may display warning information indicating that the input information is non-compliant on the UI and suspend the registration process until work information satisfying the conditions is input.

[0104] The registration processing unit 104 links the input work information to the automatic recognition code and records it in the tracking DB 123 (step SQ105). After that, the registration processing unit 104 determines whether or not there is a next tracking point set in the automatic recognition code (step SQ106), and if there is a next tracking point (step SQ106: Yes), it activates the next tracking point (step SQ107). By activating the next tracking point, it becomes possible to register work information in the next process (step SQ108). On the other hand, if there is no next tracking point (step SQ106: No), the process proceeds to a flow such as pairing processing or browsing processing. Note that, if work information in one process is to be registered in succession after work information in the next process is registered, the process may proceed to step SQ104 after step SQ107 and accept input of work information for the next process.

[0105] 16 is a flowchart showing an example of pairing processing. In the pairing processing, too, first, a user ID is input (step SQ111), and the user terminal 2 reads an automatic recognition code (step SQ112), and the code reading processing unit 103 outputs a UI corresponding to the read automatic recognition code. In the pairing processing, in step SQ112, the automatic recognition code to be used as a parent code is first read, and the code reading processing unit 103 outputs a UI corresponding to the parent code. Note that, when the pairing processing is executed consecutively after the work information registration processing or the work information browsing processing, if the UI corresponding to the parent code is already presented on the screen, steps SQ111 and SQ112 may be omitted.

[0106] Next, the pairing unit 105 accepts a pairing request from the user via the UI of the parent code, and requests the user terminal 2 to read the automatic recognition code to be the child code (step SQ114). For example, when the "pairing" button on the UI is tapped, the pairing unit 105 transmits instruction information to the user terminal 2 to activate the camera, and causes the camera of the user terminal 2 to read the child code (step SQ115). When the automatic recognition code is read by a method other than a camera, instruction information according to the reading method can be transmitted to the user terminal 2. When multiple child codes are associated with the parent code ("Yes" in step SQ116), the child codes are successively read (step SQ115 is repeated).

[0107] In the pairing process by reading the child code, for example, pairing may be performed with the field code as the parent code and the pesticide code as the child code, or with the utensil code as the parent code and the field code as the child code. Automatic recognition codes having the same managed attributes may also be paired. For example, a utensil code may be paired with a utensil code attached to another utensil, in which case any one utensil code may be associated with multiple other utensil codes as child codes.

[0108] After reading all the child codes associated with the parent code is completed (step SQ116: No), the pairing unit 105 generates pairing information indicating the correspondence between the parent code and the child code based on the read information received from the user terminal 2 (step SQ117). The pairing information may include identification information of the parent code, identification information of the child code, and information indicating the parent-child relationship of the paired automatic recognition codes. When another automatic recognition code (grandchild code) is associated with the child code, the pairing information may include identification information of the grandchild code and information indicating the correspondence between the automatic recognition codes including the grandchild code. In addition to generating the pairing information, the pairing unit 105 executes a process of linking the tracking data recorded in association with the child code to the parent code. When a grandchild code associated with the child code exists, the pairing unit 105 may link the tracking data of the grandchild code to the parent code in addition to the tracking data of the child code.

[0109] 17 is a flow chart showing an example of a browsing process of work information (tracking data). In the browsing process, first, a user ID is input (step SQ121) and the automatic recognition code is read by the user terminal 2 (step SQ122), and the code reading processing unit 103 outputs a UI corresponding to the read automatic recognition code (read code). When the browsing process is executed consecutively after the work information registration process or pairing process, steps SQ121 and SQ122 may be omitted if a UI corresponding to the automatic recognition code for which tracking data is to be browsed is already presented on the screen.

[0110] The viewing processing unit 107 receives a request to view tracking data via a UI corresponding to the read code (step SQ124). In response to the viewing request, the viewing processing unit 107 judges whether or not there is another automatic recognition code associated with the read code (step SQ125). If another automatic recognition code is not paired with the read code (step SQ125: No), the process proceeds to step SQ126, where the viewing processing unit 107 reads out tracking data associated with the read code and recorded from the tracking DB 123. On the other hand, if another automatic recognition code is paired with the read code (step SQ125: Yes), the process proceeds to step SQ127, where the viewing processing unit 107 reads out tracking data of the other automatic recognition code associated with the read code as well as tracking data associated with the read code and recorded. In addition, when the read code is a parent code and the parent code also has a child code and a grandchild code associated with the child code, the viewing processing unit 107 may read out all the tracking data of the parent code, the child code, and the grandchild code.

[0111] After reading the tracking data, the viewing processor 107 checks the authority information of the user who made the viewing request, and judges whether the authority information includes information related to viewing restrictions and whether the user has viewing authority (step SQ128). If the user has viewing authority for the read tracking data (i.e., no viewing restrictions are set for the read tracking data ("No" in step SQ128)), the process proceeds to step SQ129, where the viewing processor 107 displays the tracking data corresponding to the viewing request (the read tracking data) on the UI screen. On the other hand, if a viewing restriction is set for the read tracking data in the user's authority information ("Yes" in step SQ128), the process proceeds to step SQ130, where the viewing processor 107 extracts data corresponding to the user's authority information from the tracking data read in step SQ126 or step SQ127. The viewing processor 107 then displays the extracted data on the UI screen (step SQ131).

[0112] Note that the information processing flows shown in Figures 15 to 17 are merely examples, and the information processing method of this embodiment is not limited to the examples in Figures 15 to 17. For example, the order of some of the steps shown in Figures 15 to 17 may be changed. In Figure 17, the user authority is confirmed after the tracking data is read, but the tracking data may be read after the user authority is confirmed.

[0113] The information processing system of this embodiment issues an automatic recognition code for each management target in the agricultural product supply chain, and records basic information and work information corresponding to each automatic recognition code in a tracking database. Then, by pairing multiple automatic recognition codes and establishing a correspondence relationship between the automatic recognition codes, the work information linked to each automatic recognition code can be consolidated and managed.

[0114] The above system allows for the recording of appropriate information for each process in the agricultural product supply chain and the services of each business operator, and for efficient management of that information.For example, by recording information such as pesticide use history, field production history, and shipping / distribution history in association with pesticide codes, field codes, and equipment codes, respectively, and associating this information through pairing between automatic recognition codes, information for the entire supply chain can be managed in a unified manner.

[0115] In addition, by checking the registration conditions set in the automatic recognition code when recording work information, it is possible to ensure that information is recorded appropriately. In particular, with regard to the use of pesticides, proper use of pesticides can be ensured by preventing the registration of work information that does not meet the conditions for use, such as dilution ratio and number of applications. Furthermore, by outputting a warning when work information does not meet the registration conditions, it is possible to encourage workers to perform appropriate work.

[0116] In addition, information can be shared efficiently among multiple businesses. In particular, by pairing the automatic recognition codes, the work information linked to the child and grandchild codes can be viewed simply by reading the parent code. Also, by limiting the range of information that can be viewed according to the user's authority, appropriate information sharing can be achieved.

[0117] The above-described embodiment is merely an example for facilitating understanding of the present disclosure, and is not intended to limit the present disclosure. The present disclosure can be modified and improved without departing from the spirit thereof, and the present disclosure includes equivalents. For example, the types of automatic recognition codes are not limited to the pesticide code, field code, and utensil code shown in FIG. 2. An automatic recognition code may be issued for any management object, such as a worker, a work place, or an instrument used in the agricultural product supply chain, and pairing may be performed between the automatic recognition codes. In addition, multiple automatic recognition codes may be issued for one management object, and different processes and different input items may be set for each of them.

[0118] Furthermore, the format of the automatic recognition code is not limited to barcodes, two-dimensional codes such as QR codes (registered trademark), RFID, etc., and an appropriate format may be selected according to the attributes of the managed object. For example, if the work place is the managed object, a location information tag linked to GPS may be used, and if the worker is the managed object, an ID tag linked to biometric authentication information may be used.

[0119] Furthermore, although the present embodiment describes an example of application to an agricultural product supply chain, the information processing system of the present disclosure can also be applied to supply chains in other industrial fields involving multiple businesses and multiple bases. For example, the system can be applied to traceability management of parts or products in the general manufacturing industry, in addition to food-related industries such as food processing, livestock farming, and fisheries.

[0120] The information processing system described in this specification may be realized as a single device, or may be realized by a plurality of devices (e.g., cloud servers) partially or entirely connected via a network. For example, the functions of the control unit (processor 10) of the management server 1 and the storage 12 may be realized by different servers connected to each other via a network.

[0121] In addition, the series of processes by the information processing system described in this specification may be realized using any of software, hardware, and a combination of software and hardware. It is also possible to create a computer program for realizing each function of the management server 1 according to this embodiment and install it in a PC or the like. It is also possible to provide a computer-readable recording medium in which such a computer program is stored. The recording medium is, for example, a magnetic disk, an optical disk, a magneto-optical disk, a flash memory, etc. In addition, the above computer program may be distributed, for example, via a network, without using a recording medium.

[0122] In addition, the effects described in this specification are merely descriptive or exemplary and are not limiting. In other words, the technology according to the present disclosure may achieve other effects that are apparent to a person skilled in the art from the description of this specification, in addition to or in place of the above effects.

[0123] The information processing system, the information processing method, and the program disclosed herein may have the following configuration. [Item 1] An information processing system for information management in an agricultural product supply chain, comprising: a code information storage unit that stores basic information associated with an automatic recognition code issued for each management target related to the agricultural product supply chain; a code reading processing unit that outputs a UI (User Interface) corresponding to the basic information of one of the read automatic recognition codes in response to reading the one of the automatic recognition codes; a registration processing unit that receives an input of work information of a process related to the managed object via the UI, and records the work information in a tracking database in association with the one automatic recognition code; an information processing system comprising: a pairing unit that reads an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generates pairing information indicating a correspondence between the parent code and the child code, and links work information linked to the child code to the parent code. [Item 2] 2. An information processing system as described in item 1, wherein the basic information associated with the automatic recognition code includes basic information of the managed object and process setting information indicating a process in which work information can be registered using the automatic recognition code. [Item 3] 3. The information processing system according to claim 1 or 2, wherein the automatic identification codes used in the agricultural produce supply chain include a pesticide code issued for a pesticide as the managed object, a field code issued for a field as the managed object, and a utensil code issued for a utensil in which the agricultural produce is stored as the managed object. [Item 4] The information processing system described in item 1 or 2, wherein the code reading processing unit refers to the work information recorded in the tracking database and displays on the UI screen the current process for which the work information has been registered and the process that is the next tracking point. [Item 5] The information processing system described in item 1 or 2 further includes a viewing processing unit that receives a viewing request for tracking data from a user via the UI output in response to reading of the parent code, and displays, on a screen of the UI, the work information linked to the parent code corresponding to the viewing request and / or the work information linked to the child code associated with the parent code. [Item 6] The information processing system described in item 5, wherein the viewing processing unit extracts information corresponding to the authority information from the work information linked to the parent code and / or the work information linked to the child code corresponding to the parent code based on the authority information of the user who read the parent code, and displays it on the UI screen. [Item 7] a code invalidation processing unit that executes an invalidation process to invalidate a record of new work information in the tracking database corresponding to the automatic recognition code after the work information related to a predetermined process is registered, The information processing system according to item 1 or 2, wherein the specified process is a process corresponding to a terminal tracking point set in a project of the agricultural produce supply chain, and / or a process that is preset as a process for invalidating the automatic recognition code. [Item 8] 8. The information processing system according to item 7, wherein the code invalidation processing unit, when invalidating the parent code, executes a process of invalidating the child code associated with the parent code together with the parent code. [Item 9] 3. The information processing system according to item 1 or 2, further comprising a code reuse processing unit that receives a request for reuse of the automatic recognition code in a state in which recording of new work information is disabled, sets a new folder in the tracking database corresponding to the automatic recognition code in which recording of new work information is enabled, and executes a process of enabling the automatic recognition code. [Item 10] the code reuse processing unit sets an initial process which is a first tracking point at which new work information can be accepted during reuse, and validates the automatic recognition code; 10. The information processing system according to item 9, wherein the initial step is a step that differs depending on the management target of the automatic recognition code. [Item 11] The information processing system described in item 1 or 2 further comprises an information disclosure control unit that presents a list of input items for work information stored in the tracking database, accepts a selection of information to be disclosed to the consumer from the list, and generates consumer disclosure information. [Item 12] The automatic recognition code includes a pesticide code issued for a pesticide as the management target, the code information storage unit has an agrochemical code related information storage unit that stores, as the basic information associated with the agrochemical code, use condition information indicating use conditions of the agrochemical and field identification information specifying a field to which the agrochemical is to be sprayed; 3. The information processing system according to item 1 or 2, wherein the registration processing unit executes a process of linking the work information related to the pesticide to the pesticide code and recording it in the tracking database. [Item 13] The information processing system according to item 12, wherein the pesticide code has the processes of storage, removal, preparation for spraying, completion of spraying, and final completion of spraying set as tracking points for registering the work information. [Item 14] Item 13. The information processing system of item 12, wherein the pairing unit reads a field code issued for a field to be managed and the pesticide code corresponding to at least one type of pesticide used in the field, generates first pairing information with the field code as the parent code and the pesticide code as the child code, and links the work information linked to the pesticide code to the field code. [Item 15] Item 15. The information processing system according to item 14, wherein the pairing unit reads a utensil code issued for a utensil in which agricultural products are stored as the managed object and the field code corresponding to at least one field in which the agricultural products are harvested, generates second pairing information with the utensil code as the parent code and the field code as the child code, and links the work information linked to the field code to the utensil code. [Item 16] Item 15. The information processing system according to item 14, further comprising a log generation unit that identifies one or more of the pesticide codes associated with the field code and the work information recorded using the pesticide codes based on reading the field code, and generates a pest control log showing a pesticide spraying history in the field. [Item 17] Item 13. The information processing system according to item 12, further comprising a judgment processing unit that accepts input of work information related to the pesticide via the UI output by reading the pesticide code, and judges whether the input work information satisfies the use conditions based on the use condition information and the farm field identification information. [Item 18] Item 18. The information processing system according to item 17, wherein, when the work information related to the pesticide satisfies the usage conditions, the judgment processing unit links the work information to the pesticide code, records the work information in a tracking database, and activates the next tracking point. [Item 19] Item 18. The information processing system according to item 17, wherein the judgment processing unit outputs warning information indicating that the input information is non-compliant when the work information related to the pesticide does not satisfy the use conditions. [Item 20] 20. The information processing system of item 19, wherein the warning information includes any one or more of a warning indicating that the dilution ratio entered as the work information does not conform to the usage conditions, a warning indicating that the number of applications does not conform to the usage conditions, a warning indicating that the input date of the work information does not conform to the condition regarding the number of days before harvest, which indicates the pre-harvest pesticide use restriction period, and a warning indicating that the pesticide to be sprayed is not suitable for the target crop of the field. [Item 21] the automatic recognition code includes a field code issued for the field to be managed, the code information storage unit includes a field code information storage unit configured to store basic information about the field and process setting information indicating a process for which work information can be registered using the field code; 3. The information processing system according to item 1 or 2, wherein the registration processing unit executes a process of linking work information for the process set in the field code to the field code and recording the work information in the tracking database. [Item 22] Item 22. The information processing system according to item 21, wherein in the process setting information of the farm field code, harvest and producer shipment are set as tracking points for registering the work information. [Item 23] The automatic recognition code includes a utensil code issued to a utensil that contains agricultural produce as the management target, the code information storage unit includes an object code information storage unit that stores basic information including basic information of the object and process setting information indicating a process for which work information can be registered using the object code; The information processing system according to item 1 or 2, wherein the registration processing unit executes a process of linking work information in the process set in the object code to the object code and recording it in the tracking database. [Item 24] Item 24. An information processing system as described in Item 23, wherein the process setting information of the utensil code includes at least one of the following tracking points for registering the work information: receipt at sorting facility, sorting, shipping from sorting facility, receipt by seller, and sale. [Item 25] An information processing method for performing a process for information management in an agricultural product supply chain by a computer, comprising: storing basic information associated with an automatic identification code issued for each management target related to the agricultural product supply chain; In response to reading any one of the automatic recognition codes, outputting a UI (User Interface) corresponding to the basic information of the one of the read automatic recognition codes; accepting an input of work information of a process related to the managed object via the UI, and recording the work information in a tracking database in association with the one automatic recognition code; An information processing method executed by the computer, comprising: reading an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generating pairing information indicating the correspondence between the parent code and the child code, and linking work information linked to the child code to the parent code. [Item 26] A program for causing a computer to execute an information processing method relating to information management in an agricultural product supply chain, The information processing method includes: storing basic information associated with an automatic identification code issued for each management target related to the agricultural product supply chain; In response to reading any one of the automatic recognition codes, outputting a UI (User Interface) corresponding to the basic information of the one of the read automatic recognition codes; accepting an input of work information of a process related to the managed object via the UI, and recording the work information in a tracking database in association with the one automatic recognition code; A program comprising: reading an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generating pairing information indicating a correspondence between the parent code and the child code, and linking work information linked to the child code to the parent code. [Explanation of symbols]

[0124] 1 Management Server 2. User terminal 3. Consumer Devices 121 Code information storage unit 103 Code reading processing unit 104 Registration processing section 105 Pairing Section

Claims

1. An information processing system for information management in an agricultural product supply chain, comprising: a code information storage unit that stores basic information associated with an automatic recognition code issued for each management target related to the agricultural product supply chain; a code reading processing unit that outputs a UI (User Interface) corresponding to the basic information of one of the read automatic recognition codes in response to reading the one of the automatic recognition codes; a registration processing unit that receives an input of work information of a process related to the managed object via the UI, associates the work information with the one automatic recognition code as tracking data indicating work results, and records the work information in a tracking database that manages tracking data for each automatic recognition code; an information processing system comprising: a pairing unit that reads an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generates pairing information indicating a correspondence between the parent code and the child code, and links tracking data linked to the child code to the parent code.

2. 2. The information processing system according to claim 1, wherein the basic information associated with the automatic recognition code includes basic information of the managed object and process setting information indicating a process in which work information can be registered using the automatic recognition code.

3. The information processing system according to claim 1 or 2, wherein the automatic recognition codes used in the agricultural produce supply chain include a pesticide code issued for a pesticide as the managed object, a field code issued for a field as the managed object, and a utensil code issued for a utensil in which the agricultural produce is stored as the managed object.

4. 3. The information processing system according to claim 1, wherein the code reading processing unit refers to the work information recorded in the tracking database, and displays on the UI screen the current process for which the work information has been registered and the process that is the next tracking point.

5. The information processing system of claim 1 or 2, further comprising a viewing processing unit that receives a viewing request for the tracking data from a user via the UI output in response to reading of the parent code, and displays on the screen of the UI the work information linked to the parent code corresponding to the viewing request and / or the work information linked to the child code associated with the parent code.

6. The information processing system of claim 5, wherein the viewing processing unit extracts information corresponding to the authority information from the work information linked to the parent code and / or the work information linked to the child code corresponding to the parent code based on the authority information of the user who read the parent code, and displays the information on the UI screen.

7. a code invalidation processing unit that executes an invalidation process to invalidate a record of new work information in the tracking database corresponding to the automatic recognition code after the work information related to a predetermined process is registered, The information processing system according to claim 1 or 2, wherein the specified process is a process corresponding to a terminal tracking point set in a project of the agricultural product supply chain, and / or a process preset as a process for invalidating the automatic recognition code.

8. The information processing system according to claim 7 , wherein the code invalidation processing unit, when invalidating the parent code, executes a process of invalidating the child code associated with the parent code together with the parent code.

9. 3. The information processing system according to claim 1, further comprising a code reuse processing unit that receives a request for reuse of the automatic recognition code in a state in which recording of new work information is disabled, sets a new folder in the tracking database corresponding to the automatic recognition code in which recording of new work information is enabled, and executes a process of enabling the automatic recognition code.

10. the code reuse processing unit sets an initial process which is a first tracking point at which new work information can be accepted during reuse, and validates the automatic recognition code; 10. The information processing system according to claim 9, wherein the initial step is a step that differs depending on the management target of the automatic recognition code.

11. The information processing system of claim 1 or 2, further comprising an information disclosure control unit that presents a list of input items for work information stored in the tracking database, accepts a selection of information to be disclosed to the consumer from the list, and generates consumer disclosure information.

12. The automatic recognition code includes a pesticide code issued for a pesticide as the management target, the code information storage unit has an agrochemical code related information storage unit that stores, as the basic information associated with the agrochemical code, use condition information indicating use conditions of the agrochemical and field identification information specifying a field to which the agrochemical is to be sprayed; The information processing system according to claim 1 or 2, wherein the registration processing unit executes a process of linking the work information related to the pesticide to the pesticide code as the tracking data and recording the work information in the tracking database of the pesticide code.

13. 13. The information processing system according to claim 12, wherein the agricultural chemical code includes steps of storage, removal, preparation for spraying, completion of spraying, and final completion of spraying as tracking points for registering the work information.

14. The information processing system according to claim 12, wherein the pairing unit reads a field code issued for a field to be managed and the pesticide code corresponding to at least one type of pesticide used in the field, generates first pairing information with the field code as the parent code and the pesticide code as the child code, and links the work information linked to the pesticide code to the field code.

15. The information processing system of claim 14, wherein the pairing unit reads a utensil code issued to designate a utensil in which agricultural produce is stored as the managed object, and the field code corresponding to at least one field in which the agricultural produce is harvested, to generate second pairing information with the utensil code as the parent code and the field code as the child code, and to link the work information linked to the field code to the utensil code.

16. The information processing system according to claim 14, further comprising a log generation unit that, based on reading the field code, identifies one or more of the pesticide codes associated with the field code and the work information recorded using the pesticide codes, and generates a pest control log showing a pesticide spraying history in the field.

17. The information processing system of claim 12, further comprising a judgment processing unit that accepts input of work information related to the pesticide via the UI output by reading the pesticide code, and determines whether the input work information satisfies the use conditions based on the use conditions information and the field identification information.

18. The information processing system according to claim 17, wherein when the work information related to the pesticide satisfies the usage conditions, the judgment processing unit links the work information to the pesticide code, records the work information in a tracking database, and activates the next tracking point.

19. The information processing system according to claim 17 , wherein the determination processing unit outputs warning information indicating that input information is non-compliant when the work information related to the pesticide does not satisfy the use conditions.

20. The information processing system described in claim 19, wherein the warning information includes any one or more of a warning indicating that the dilution ratio input as the work information does not conform to the usage conditions, a warning indicating that the number of applications does not conform to the usage conditions, a warning indicating that the input date of the work information does not conform to a condition regarding the number of days before harvest which indicates a restricted period for pesticide use before harvest, and a warning indicating that the pesticide to be sprayed is not suitable for the target crop of the field.

21. the automatic recognition code includes a field code issued for the field to be managed, the code information storage unit includes a field code information storage unit configured to store basic information about the field and process setting information indicating a process for which work information can be registered using the field code; 3. The information processing system according to claim 1, wherein the registration processing unit executes a process of linking work information in the process set in the field code to the field code as the tracking data and recording the work information in the tracking database of the field code.

22. The information processing system according to claim 21 , wherein in the process setting information of the farm field code, harvesting and producer shipment are set as tracking points for registering the work information.

23. The automatic recognition code includes a utensil code issued to a utensil that contains agricultural produce as the management target, the code information storage unit includes an object code information storage unit that stores basic information including basic information of the object and process setting information indicating a process for which work information can be registered using the object code; The information processing system according to claim 1 or 2, wherein the registration processing unit executes a process of linking work information in the process set in the object code to the object code as the tracking data and recording it in the tracking database of the object code.

24. The information processing system of claim 23, wherein the process setting information of the utensil code includes at least one of the following tracking points for registering the work information: receipt at sorting facility, sorting, shipping from sorting facility, receipt by seller, and sale.

25. An information processing method for performing a process for information management in an agricultural product supply chain by a computer, comprising: storing basic information associated with an automatic identification code issued for each management target related to the agricultural product supply chain; outputting a UI (User Interface) corresponding to the basic information of the read one of the automatic recognition codes in response to reading the one of the automatic recognition codes; accepting an input of work information of a process related to the managed object via the UI, linking the work information to the one automatic recognition code as tracking data indicating work results, and recording the work information in a tracking database that manages tracking data for each automatic recognition code; An information processing method executed by the computer, comprising: reading an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generating pairing information indicating the correspondence between the parent code and the child code, and linking tracking data linked to the child code to the parent code.

26. A program for causing a computer to execute an information processing method relating to information management in an agricultural product supply chain, The information processing method includes: storing basic information associated with an automatic identification code issued for each management target related to the agricultural product supply chain; outputting a UI (User Interface) corresponding to the basic information of the read one of the automatic recognition codes in response to reading the one of the automatic recognition codes; accepting an input of work information of a process related to the managed object via the UI, linking the work information to the one automatic recognition code as tracking data indicating work results, and recording the work information in a tracking database that manages tracking data for each automatic recognition code; A program comprising: reading an automatic recognition code serving as a parent code and an automatic recognition code serving as a child code, generating pairing information indicating a correspondence between the parent code and the child code, and linking tracking data linked to the child code to the parent code.

Images