Information processing method, non-transitory computer-readable recording medium, RFID (radio frequency identifier) reader, and information processing system

Abstract

To provide an information processing method or the like which can store information about an RF tag each time when a code of the RF tag is read by an RFID reader.SOLUTION: The information processing method according to one aspect includes: each time when an RFID reader 1 reads a code of an RF tag 20, storing the read code of the RF tag 20, a date / time of reading, and a work attribute in association with each other; and transmitting the stored code of the RF tag 20, the stored date / time, and the stored work attribute to a server computer 2, wherein the server computer 2 executes processing of storing the code of the RF tag 20, the date / time, and the work attribute in association with each other.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing method, a non-transitory computer-readable recording medium, an RFID reader, and an information processing system. [Background technology]

[0002] In recent years, there has been active development of technology for managing objects (products or product packaging, etc.) by reading information storage media (e.g., RFID) attached to the objects. For example, Patent Document 1 discloses a product management system that, in product management using information storage media, detects damage to the information storage media and determines whether the product is insufficient or excessive. [Prior art documents] [Patent documents]

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

[0004] However, the invention of Patent Document 1 has a problem in that it is not possible to store information about an RF (Radio Frequency) tag every time the code of the RF tag is read by an RFID reader.

[0005] One aspect of the present invention is to provide an information processing method etc. that can store information about an RF tag every time a code of the RF tag is read by an RFID reader. [Means for solving the problem]

[0006] An information processing method according to one aspect is characterized in that, each time an RF tag code is read by an RFID reader, the read RF tag code is associated with the date and time when the read was performed and work attributes are stored, and the stored RF tag code, date and time, and work attributes are transmitted to a server computer, and the server computer executes a process of storing the RF tag code, date and time, and work attributes in association with each other. Effect of the Invention

[0007] In one aspect, each time an RFID reader reads the code on an RF tag, it is possible to store information about that RF tag. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an overview of an RF tag matching system. [Diagram 2] 1 is a block diagram showing an example of the configuration of an RFID reader. [Diagram 3] FIG. 11 is an explanatory diagram showing an example of a record layout of a read information DB. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of a data configuration of a reference file. [Diagram 5] FIG. 2 is a block diagram showing an example of the configuration of a server. [Figure 6] FIG. 2 is an explanatory diagram illustrating an example of a record layout of a management DB. [Figure 7] 11 is a flowchart showing a processing procedure for transmitting a code, a read date and time, and work attributes. [Figure 8] FIG. 13 is an explanatory diagram showing an example of a selection acceptance screen for an item in a reference file. [Figure 9A] FIG. 11 is an explanatory diagram showing an example of a determination result of over- or under-reading of an RF tag. [Figure 9B] FIG. 11 is an explanatory diagram showing an example of a determination result of over- or under-reading of an RF tag. [Figure 9C] FIG. 11 is an explanatory diagram showing an example of a determination result of over- or under-reading of an RF tag. [Figure 10]11 is a flowchart showing a processing procedure for determining whether an RF tag has been read excessively or insufficiently. [Figure 11] 10 is a flowchart showing the procedure of a subroutine for determining whether an RF tag has been read excessively or insufficiently. [Figure 12] FIG. 11 is an explanatory diagram illustrating a code conversion process. [Figure 13] 11 is a flowchart showing a processing procedure for performing code conversion processing. [Figure 14] FIG. 13 is an explanatory diagram showing an example of a record layout of a read information DB in the third embodiment. [Figure 15] FIG. 11 is an explanatory diagram illustrating a process of storing a first two-dimensional code and a second two-dimensional code in association with each other. [Figure 16] 10 is a flowchart showing a processing procedure for storing a first two-dimensional code and a second two-dimensional code in association with each other. [Figure 17] FIG. 13 is an explanatory diagram showing an overview of an RF tag matching system according to a fourth embodiment. [Figure 18] FIG. 13 is a block diagram showing an example of the configuration of a server in the fourth embodiment. [Figure 19] FIG. 2 is an explanatory diagram showing an example of a record layout of an object information DB. [Figure 20] 10 is a flowchart showing a processing procedure when information on an object is transmitted to a server. [Figure 21] 13 is a flowchart showing a processing procedure for creating a report file. [Figure 22] FIG. 11 is an explanatory diagram illustrating an example of a report file. [Diagram 23] FIG. 13 is an explanatory diagram showing an example of a display screen of a fifth graph. [Figure 24] FIG. 13 is an explanatory diagram showing an example of a display screen of the sixth graph. [Diagram 25] FIG. 13 is an explanatory diagram showing an example of a display screen of a seventh graph. [Figure 26] 13 is a flowchart showing a processing procedure for outputting a graph based on damage information of an object. [Figure 27] FIG. 13 is an explanatory diagram illustrating an example of a record layout of a management DB in the fifth embodiment. [Figure 28] 10 is a flowchart showing a processing procedure for storing position information of an object. [Figure 29] FIG. 13 is an explanatory diagram showing an example of a map screen showing the position of an object; [Diagram 30] 10 is a flowchart showing a processing procedure for outputting the position of an object on a map. [Diagram 31] FIG. 23 is a block diagram showing an example of the configuration of a server in the sixth embodiment. [Diagram 32] FIG. 13 is an explanatory diagram showing an example of a record layout of a shelf DB. [Diagram 33] 10 is a flowchart showing a processing procedure for identifying a shelf in which an object can be stored. [Diagram 34] FIG. 13 is an explanatory diagram showing an example of a display screen showing the storage status of shelves. [Diagram 35] 13 is a flowchart showing a processing procedure for outputting a shelf map and a first graph. [Diagram 36] FIG. 23 is a block diagram showing an example of the configuration of a server in the seventh embodiment. [Figure 37] FIG. 13 is an explanatory diagram showing an example of the record layout of an inventory count DB and an inventory management DB. [Figure 38] FIG. 13 is an explanatory diagram showing an example of a display screen of a second graph. [Figure 39] 13 is a flowchart showing a processing procedure for outputting a second graph. [Diagram 40] FIG. 13 is an explanatory diagram showing an example of a display screen of a third graph. [Diagram 41] 13 is a flowchart showing a processing procedure for outputting a third graph. [Diagram 42] FIG. 13 is an explanatory diagram showing an example of a display screen of a fourth graph. [Diagram 43] 13 is a flowchart showing a processing procedure for outputting a fourth graph. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the present invention will be described in detail with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) The first embodiment relates to a mode in which, every time a code of an RF tag is read, the read code of the RF tag is stored in association with a date and time and an operation attribute.

[0011] 1 is an explanatory diagram showing an overview of an RF tag matching system. The system of this embodiment includes an RFID reader 1 and an information processing device 2, and each device transmits and receives information via a network N such as the Internet.

[0012] The RFID reader 1 generates electromagnetic waves from an antenna to communicate with an RF tag 20 in a non-contact manner and reads (scans) information stored in the RF tag 20. The RFID reader 1 can also read multiple RF tags simultaneously.

[0013] It should be noted that an RFID reader / writer may be used in place of the RFID reader 1. The RFID reader / writer is capable of not only reading information stored in the RF tag 20 but also writing information to the writable area of ​​the RF tag 20.

[0014] The RFID reader 1 may be, for example, an information processing device such as a smartphone, a mobile phone, a tablet, or a personal computer terminal having a reader function for reading the code or two-dimensional code of the RF tag 20. Alternatively, the RFID reader 1 may be an imaging device such as a CCD (Charge Coupled Device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera having a communication function.

[0015] The RF tag 20 has an IC (Integrated Circuit) chip that stores information, and is attached to the object 10. The object 10 includes a manufactured product, a product, or packaging for a product or the like. The RF tag 20 is used together with a corresponding RFID reader 1, and is capable of transmitting or receiving data between the RFID reader 1 in a non-contact manner. The RF tag 20 in this embodiment is created by encoding (writing data to the IC chip) a dedicated code (for example, "RFID1").

[0016] The information processing device 2 is an information processing device that processes, stores, and transmits / receives various information. The information processing device 2 is, for example, a server computer (server device), a cloud server device, a personal computer, or a general-purpose tablet PC (personal computer). In this embodiment, the information processing device 2 is a server computer, and hereinafter will be referred to as server 2 for simplicity.

[0017] The RFID reader 1 according to this embodiment reads the code of the RF tag 20 printed on the surface of the RF tag 20 affixed to the target object 10. The RFID reader 1 stores the read code of the RF tag 20 in association with the date and time when the tag was read and the work attribute. The RFID reader 1 transmits the stored code, date and time, and work attribute of each RF tag 20 to the server 2. The server 2 stores the code of each RF tag 20 in association with the date and time, and the work attribute.

[0018] 2 is a block diagram showing an example of the configuration of the RFID reader 1. The RFID reader 1 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a code reading unit 16, a large-capacity storage unit 17, and an imaging unit 18. Each component is connected by a bus B.

[0019] The control unit 11 includes an arithmetic processing device such as a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit), and reads out and executes a control program 1P (program product) stored in the storage unit 12, thereby performing various information processing related to the RFID reader 1, 2, the control unit 11 is described as being a single processor, but may be a multi-processor.

[0020] The storage unit 12 includes memory elements such as a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data required for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing processing related to communication, and transmits and receives information to and from the server 2, etc. via the network N.

[0021] The input unit 14 may be a keyboard, a mouse, or a touch panel integrated with the display unit 15. The display unit 15 is a liquid crystal display or an organic EL (Electroluminescence) display, etc., and displays various information according to instructions from the control unit 11. The code reading unit 16 is a read-only module for reading the code or two-dimensional code of the RF tag 20.

[0022] The mass storage unit 17 includes a recording medium such as a hard disk drive (HDD) or a solid state drive (SSD). The mass storage unit 17 includes a read information database (DB) 171 and a reference file 172.

[0023] The read information DB 171 stores the code of the RF tag 20 read by the RFID reader 1, as well as the date and time of reading, work attributes, etc. The reference file 172 stores a plurality of RF tags 20 to be read. The reference file will be described later.

[0024] The photographing unit 18 is, for example, a photographing device such as a CCD camera or a CMOS camera. The photographing unit 18 may not be built in the RFID reader 1, but may be externally connected to the RFID reader 1 and configured to be capable of photographing.

[0025] 3 is an explanatory diagram showing an example of a record layout of the read information DB 171. The read information DB 171 includes a UID column, an RFID column, an arrival column, an inventory column, and a shipment column.

[0026] The work attributes of the object 10 include reception, inventory count, and shipment. Inventory count is a task of checking the amount of stock remaining in a warehouse. Note that, in this embodiment, an example of work attributes including reception, inventory, and shipment has been described, but this is not limiting. For example, the work attributes may include inspection, etc.

[0027] The UID column stores a unique ID of any object 10 in order to identify each object 10. The UID is set so that there is a one-to-one relationship between the UID and the EPC (Electronic Product Code). The UID may be the same code as the EPC.

[0028] The UID of the object 10 may be automatically assigned as a consecutive number when the RF tag 20 is issued using software for printing the RF tag 20. Alternatively, the UID of the object 10 may be obtained by using a UID data file to which UIDs have been assigned in advance.

[0029] The RFID column stores the code of the RF tag 20 read by the RFID reader 1. The arrival column includes an arrival status column and a reading date and time column. The arrival status column stores the arrival status of the object 10. The arrival status includes statuses such as "arrival completed" and "incomplete". The reading date and time column stores date and time information when the code of the RF tag 20 was read by the RFID reader 1 when the object 10 arrived.

[0030] The inventory column includes an inventory status column and a read date and time column. The inventory status column stores the inventory status of the target object 10. The inventory status includes, for example, statuses such as "inventory completed" and "incomplete." The read date and time column stores date and time information when the code of the RF tag 20 was read by the RFID reader 1 during the inventory of the target object 10.

[0031] The shipping column includes a shipping status column and a reading date and time column. The shipping status column stores the shipping status of the object 10. The shipping status includes, for example, statuses such as "shipped completed" and "not completed." The reading date and time column stores date and time information when the code of the RF tag 20 is read by the RFID reader 1 when the object 10 is shipped.

[0032] 4 is an explanatory diagram showing an example of the data configuration of the reference file 172. The reference file 172 storing multiple RF tags 20 to be read is stored in advance in the mass storage unit 17 of the RFID reader 1. That is, information on multiple RF tags 20 to be read by the RFID reader 1 is stored in the reference file 172 and used.

[0033] In addition, when a second RF tag 20 different from the RF tag 20 included in the reference file 172 already imported into the RFID reader 1 is to be read, it is necessary to import into the RFID reader 1 a reference file 172 including the second RF tag 20 to be read.

[0034] The reference file 172 stores the number (No), product management code, location, pick list, EPC, etc. EPC is a general term for identification codes to be written to electronic tags standardized by GS1 (an international organization for the management of distribution codes and distribution standards). The number is the number to be read.

[0035] The product management code is, for example, a code that is uniquely determined for each object 10 based on the manufacturing date or manufacturing lot of the object 10, and is a code that is assigned to the object 10 at the manufacturing factory that manufactures the object 10. The location may be the longitude and latitude of the object 10, the name of the location, the name of a warehouse, or the like.

[0036] A picklist is a list to which the reading (picking) target belongs. Picklists can be set by the vendor under any conditions. As an example, a receiving picklist, an inventory picklist, and a shipping picklist may be set according to the work attributes including receiving, inventory, and shipping.

[0037] As shown in the figure, for a picklist named "PICK1", all RF tags 20 belonging to "PICK1" are to be read. Specifically, the RF tags 20 affixed to objects 10 whose product management codes are "PART_A_1" and "PART_B_1" are the RF tags 20 belonging to "PICK1" that should be read.

[0038] It should be noted that the reference file is not limited to the above items, and other items (such as the order number or name of the object 10) may be stored in accordance with actual needs.

[0039] 5 is a block diagram showing an example of the configuration of the server 2. The server 2 includes a control unit 21, a storage unit 22, a communication unit 23, a reading unit 24, a large-capacity storage unit 25, and a display unit 26. Each component is connected by a bus B.

[0040] The control unit 21 includes a processor such as a CPU, an MPU, a graphics processing unit (GPU), a field programmable gate array (FPGA), a digital signal processor (DSP), or a quantum processor. By reading and executing 2P (program product), various information processing, control processing, etc. related to the server 2 are performed.

[0041] The control program 2P can be deployed to be executed on a single computer, or on multiple computers located at one site, or distributed across multiple sites and interconnected by a communications network. Although the control unit 21 is described in FIG. 5 as being a single processor, it may be a multiprocessor.

[0042] The storage unit 22 includes memory elements such as RAM or ROM, and stores the control program 2P or data required for the control unit 21 to execute processing. The storage unit 22 also temporarily stores data required for the control unit 21 to execute arithmetic processing. The communication unit 23 is a communication module for performing processing related to communication, and transmits and receives information to and from the RFID reader 1, etc. via the network N.

[0043] The reading unit 24 reads the portable storage medium 2a including a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM. The control unit 21 may read the control program 2P from the portable storage medium 2a via the reading unit 24 and store it in the mass storage unit 25. The control unit 21 may also download the control program 2P from another computer via the network N or the like and store it in the mass storage unit 25. Furthermore, the control unit 21 may read the control program 2P from the semiconductor memory 2b.

[0044] The mass storage unit 25 includes a recording medium such as an HDD or SSD. The mass storage unit 25 includes a management DB 251. The management DB 251 stores management information of the object 10. The display unit 26 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 21.

[0045] In this embodiment, the storage unit 22 and the large-capacity storage unit 25 may be configured as an integrated storage device. The large-capacity storage unit 25 may be configured with a plurality of storage devices. Furthermore, the large-capacity storage unit 25 may be an external storage device connected to the server 2.

[0046] The server 2 may execute various information processing and control processing, etc., on a single computer, or may execute the processing in a distributed manner on multiple computers. The server 2 may be realized by multiple virtual machines provided in one server, or may be realized by using a cloud server.

[0047] 6 is an explanatory diagram showing an example of a record layout of the management DB 251. The management DB 251 includes a UID column, an RFID column, an arrival column, an inventory column, and a shipment column. Note that each column of the management DB 251 is similar to each column of the read information DB 171, and therefore a description thereof will be omitted.

[0048] The above-mentioned storage formats of each DB are merely examples, and other storage formats may be used as long as the relationships between the data are maintained.

[0049] Next, a process will be described in which, every time the code of the RF tag 20 is read, the code read from the RF tag 20 is stored in association with the read date and time and the work attribute.

[0050] 7 is a flowchart showing a processing procedure for transmitting the code, the read date and time, and the work attribute. The control unit 11 of the RFID reader 1 reads the code of the RF tag 20 printed on the surface of the RF tag 20 attached to each object 10 through the code reading unit 16. (Step S101). The control unit 11 receives an input of the task attribute for the target object 10 via the input unit 14 (Step S102). Note that the task attribute can be specified based on a pick list, which will be described later.

[0051] The control unit 11 associates the code of the read RF tag 20 with the read date and time when the reading was performed and the work attribute, and stores them in the read information DB 171 of the mass storage unit 17 (step S103). Specifically, the control unit 11 associates the UID of the object 10 and the code of the read RF tag 20, and stores the status of the work attribute and the read date and time in the read information DB 171. For example, when the work attribute is arrival, the control unit 11 associates the arrival status of "arrival completed" and the read date and time in the read information DB 171 with the UID of the object 10 and the code of the RF tag 20.

[0052] The control unit 11 transmits the stored UID of the object 10, the code of the RF tag 20, the read date and time, and the work attributes to the server 2 via the communication unit 13 (step S104). The control unit 21 of the server 2 receives the UID of the object 10, the code of the RF tag 20, the read date and time, and the work attributes transmitted from the RFID reader 1 via the communication unit 23 (step S201).

[0053] The control unit 21 associates the received code of the RF tag 20 with the read date and time and the work attribute, and stores them in the management DB 251 of the mass storage unit 25 (step S202). The control unit 21 ends the process. Specifically, the control unit 21 stores the work attribute status and the read date and time in the management DB 251, associated with the received UID of the target object 10 and the code of the RF tag 20.

[0054] Next, a process for determining whether the RF tag 20 has been read excessively or insufficiently using the reference file 172 will be described. First, a process for accepting the selection of an item in the reference file 172 will be described.

[0055] 8 is an explanatory diagram showing an example of a selection acceptance screen for items in the reference file 172. The screen includes a list display field 11a, a product management code selection field 11b, a location selection field 11c, a pick list selection field 11d, and an EPC selection field 11e.

[0056] The list display field 11a is a display field that displays a list of multiple RF tags 20 included in the reference file 172. The product management code selection field 11b is a selection field that accepts the selection of a product management code. The location selection field 11c is a selection field that accepts the selection of a location. The pick list selection field 11d is a selection field that accepts the selection of a pick list. The EPC selection field 11e is a selection field that accepts the selection of an EPC.

[0057] The RFID reader 1 stores in advance in the mass storage unit 17 a reference file 172 that stores multiple RF tags 20 to be read. The RFID reader 1 refers to the reference file 172 stored in the mass storage unit 17, and reads out the multiple RF tags 20 and the items of each RF tag 20 in the reference file 172. The RFID reader 1 displays the multiple RF tags 20 that have been read out and the items of each RF tag 20 in the list display field 11a.

[0058] As shown in the figure, items including the number (No), product management code, location, pick list, and EPC are displayed in the list display field 11a for each RF tag 20 to be read. Note that the items are not limited to those mentioned above, and other items (order number, name, etc.) may be displayed according to actual needs.

[0059] The RFID reader 1 accepts the selection of the type of item in the reference file 172 by the vendor (user). The type of item is a detailed classification of the item. For example, Location item types include "LOC_X" and "LOC_Y", and picklist item types include "PICK1" and "PICK2", where "LOC_X" and "LOC_Y" each indicate a different location or warehouse name, etc. "PICK1" and "PICK2" each indicate, for example, an incoming picklist and an inventory picklist.

[0060] For example, when the RFID reader 1 receives a selection operation in the location selection field 11c, it receives the selection of the type of location item (e.g., "LOC_X" or "LOC_Y") by the vendor. The RFID reader 1 identifies the RF tag 20 to be read that corresponds to the selected location item (e.g., "LOC_X"). The RFID reader 1 displays a list of the identified RF tags 20 to be read in the list display field 11a.

[0061] Alternatively, when the RFID reader 1 receives a selection operation in the picklist selection field 11d, it receives the selection of the type of picklist item (e.g., "PICK1" or "PICK2") by the vendor. The RFID reader 1 identifies the RF tag 20 to be read that corresponds to the selected picklist item (e.g., "PICK1"). The RFID reader 1 displays a list of the identified RF tags 20 to be read in the list display field 11a.

[0062] When there are multiple reference files 172, the RFID reader 1 accepts the vendor's selection of a reference file 172 from the multiple reference files 172. The RFID reader 1 refers to the selected reference file 172, and reads out the multiple RF tags 20 and the items of each RF tag 20 in the reference file 172.

[0063] Next, a process for determining whether the RF tag 20 has been read excessively or insufficiently based on the reference file 172 will be described.

[0064] 9A, 9B, and 9C are explanatory diagrams showing an example of a result of judgment on over-reading or under-reading of the RF tag 20. Fig. 9A is an explanatory diagram showing an example of a screen showing successful reading of the RF tag 20. Fig. 9B is an explanatory diagram showing an example of a screen showing unsuccessful reading of the RF tag 20. Fig. 9C is an explanatory diagram showing an example of an over-reading screen of the RF tag 20.

[0065] The screen includes an RFID button 12a. The RFID button 12a is a button for reading the code of the RF tag 20. When the RFID reader 1 receives a touch (click) operation of the RFID button 12a, it reads the code of the RF tag 20 printed on the surface of the RF tag 20 attached to each object 10. The code of the RF tag 20 includes an EPC.

[0066] The RFID reader 1 judges whether the RF tag 20 has been read too much or too little by comparing the read RF tag 20 with the tag of the RF tag 20 to be read that corresponds to the item (e.g., PICK1) selected from the reference file 172. The RFID reader 1 displays the judgment result on the screen.

[0067] Specifically, the RFID reader 1 determines that the reading is successful when the EPC included in the code of the read RF tag 20 is stored in the reference file 172. After reading all the RF tags 20 to be read, the RFID reader 1 determines whether the number of the read RF tags 20 matches the number of the RF tags 20 to be read that corresponds to the item selected from the reference file 172 (e.g., PICK1).

[0068] If the two numbers match, the RFID reader 1 displays a message indicating that the reading was successful and including the number of RF tags 20 that were read. As shown in FIG. 9A, the number of RF tags 20 that are read is "54". The screen will display the number of groups 20 and a message including "Scan Complete!".

[0069] If the EPC included in the code of the read RF tag 20 is not stored in the reference file 172, the RFID reader 1 determines that the reading has failed. In this case, the RFID reader 1 outputs information indicating that the RFID tag 20 is not a target for reading. As shown in FIG. 9B, the message "Other Items Detected!" is displayed on the screen. The RFID reader 1 may also output an alert on the screen indicating that the items are different from those in the reference file 172.

[0070] When the number of read RF tags 20 exceeds the number of RF tags 20 to be read, the RFID reader 1 displays a message including a message indicating that the number of read RF tags 20 has been exceeded. As shown in Fig. 9C, the message "Scan Quantity Exceeded!" is displayed on the screen.

[0071] When the number of read RF tags 20 is less than the number of RF tags 20 to be read, the RFID reader 1 displays a message including a message indicating that the number of read RF tags 20 is insufficient. For example, a message (not shown) such as "Scan Quantity Insufficient!" may be displayed. The RFID reader 1 counts the number of unread RF tags 20 from the reference file 172. The RFID reader 1 may display the counted number of unread RF tags 20 on the screen together with the message.

[0072] 10 is a flowchart showing the processing procedure for determining whether the RF tags 20 have been read too much or too little. The control unit 11 of the RFID reader 1 acquires a reference file 172 that stores multiple RF tags 20 to be read (step S111). For example, the control unit 11 may download the reference file 172 from the RF tag matching system of this embodiment via the communication unit 13. The control unit 11 stores the acquired reference file 172 in the mass storage unit 17 (step S112).

[0073] It should be noted that once the above-mentioned process (steps S111 to S112) has been performed, the process can be omitted from the next time.

[0074] The control unit 11 refers to the reference file 172 stored in the mass storage unit 17, and reads out the multiple RF tags 20 in the reference file 172 and the items of each RF tag 20 (number, product management code, position, pick list, EPC, etc.) (step S113).

[0075] The control unit 11 displays a list of the read RF tags 20 and the items of each RF tag 20 via the display unit 15 (step S114). The control unit 11 accepts the vendor's selection of an item in the reference file 172 and the type of the item via the input unit 14 (step S115). The control unit 11 displays a list of RF tags 20 to be read that correspond to the selected item and the type of the item via the display unit 15 (step S116).

[0076] The control unit 11 executes a subroutine for determining whether the RF tag 20 has been read too much or too little (step S117). The subroutine for determining whether the RF tag 20 has been read too much or too little will be described later. The control unit 11 deletes the read RF tag 20 from the reference file 172, thereby updating the reference file 172 (step S118). The control unit 11 displays the determination result on the display unit 15 (step S119), and ends the process.

[0077] Note that the timing of updating the reference file 172 is not limited to the above. For example, it may be performed at predetermined intervals (for example, once a day) by batch processing.

[0078] Note that it is not essential to select an item in the reference file 172, and all of the RF tags 20 included in the reference file 172 may be read. In this case, the control unit 11 omits the processing of steps S115 to S116 and the processing of step S118 (update processing of the reference file 172). After that, the control unit 11 executes the processing of step S104 in FIG. 7.

[0079] 11 is a flowchart showing the procedure of a subroutine for determining whether the RF tag 20 has been read too much or too little. The control unit 11 of the RFID reader 1 reads the code of the RF tag 20 attached to the target object 10 via the code reading unit 16 (step S01). The control unit 11 determines whether the EPC included in the read code of the RF tag 20 is stored in the reference file 172 (step S02).

[0080] If the EPC included in the code of the RF tag 20 is not stored in the reference file 172 (NO in step S02), the control unit 11 determines that the reading has failed (step S03). The control unit 11 displays a message indicating that the tag was not read on the display unit 15 (step S04). If the EPC included in the code of the RF tag 20 is stored in the reference file 172 (YES in step S02), the control unit 11 determines that the reading has been successful (step S05).

[0081] The control unit 11 determines whether or not reading of the codes of all the RF tags 20 to be read has been completed (step S06). If reading of the codes of all the RF tags 20 to be read has not been completed (NO in step S06), the control unit 11 returns to the process of step S01.

[0082] When reading of the codes of all RF tags 20 to be read has been completed (YES in step S06), the control unit 11 determines whether the number of RF tags 20 read matches the number of RF tags 20 to be read corresponding to the item selected from the reference file 172 (step S07).

[0083] If the two numbers match (YES in step S07), the control unit 11 displays a message indicating that reading was successful on the display unit 15 (step S08). The control unit 11 ends the subroutine for the process of determining whether reading was insufficient or excessive, and returns. If the two numbers do not match (NO in step S07), the control unit 11 determines whether the number of read RF tags 20 exceeds the number of RF tags 20 to be read (step S09).

[0084] If the number of read RF tags 20 exceeds the number of RF tags 20 to be read (YES in step S09), the control unit 11 displays a message including a message indicating that the number of read RF tags 20 has exceeded (step S10) on the display unit 15. The control unit 11 ends the subroutine for the process of determining whether the reading is excessive or insufficient, and returns.

[0085] If the number of read RF tags 20 is less than the number of RF tags 20 to be read (NO in step S09), the control unit 11 causes the display unit 15 to display a message indicating that the number of read RF tags 20 is insufficient (step S11). The control unit 11 ends the subroutine for the process of determining whether the reading is insufficient or not, and returns.

[0086] According to this embodiment, every time the RFID reader 1 reads the code of the RF tag 20, it is possible to store the read code of the RF tag 20 in association with the read date and time and the work attribute.

[0087] According to this embodiment, by referring to the reference file 172, it is possible to judge whether the RF tag 20 has been read excessively or insufficiently.

[0088] According to this embodiment, by using the reference file 172, it becomes possible to determine whether the RF tag 20 has been read excessively or insufficiently by the RFID reader 1 alone, without depending on a specific network environment.

[0089] According to this embodiment, when the RF tag 20 is not stored in the reference file 172, it is possible to output information indicating that the RF tag 20 is not a target for reading.

[0090] (Embodiment 2) The second embodiment relates to a form in which a first code of a two-dimensional code attached to an object 10 is converted into a second code, and the converted second code is set as the code of an RF tag 20. Note that a description of the contents overlapping with the first embodiment will be omitted.

[0091] The two-dimensional code may be, for example, a QR code (registered trademark) that has information in both horizontal and vertical directions, as opposed to a one-dimensional code that has information only in the horizontal direction. The one-dimensional code may be, for example, a barcode that expresses numbers or characters by the thickness of lines in a striped pattern. Note that, although an example of a two-dimensional code has been described in this embodiment, the present invention is not limited to this, and may also be applied to one-dimensional codes.

[0092] The RF tag 20 is encoded on the spot based on the two-dimensional code affixed to the object 10, and the encoded RF tag 20 is issued. The issued RF tag 20 is affixed to the object 10. However, if the size of the two-dimensional code to be encoded is large, it may not be possible to encode it because it will not fit into the code memory capacity of the RF tag 20 to be encoded. In this embodiment, the above-mentioned problem can be solved by performing a code conversion process on the two-dimensional code to be encoded.

[0093] Fig. 12 is an explanatory diagram illustrating the code conversion process. As shown in the figure, a two-dimensional code 19 is affixed to an object 10. Fig. 12 also includes a printer 3. The printer 3 is a printer that prints an RF tag 20, etc.

[0094] The RFID reader 1 reads the two-dimensional code 19 to obtain a first code of the two-dimensional code 19. The RFID reader 1 converts the obtained first code into a second code which is shorter than the first code.

[0095] Specifically, the RFID reader 1 converts the acquired first code into a second code that is shorter than the first code, for example, by using a hash function of MD (Message Digest) 5. The MD5 hash function is one of the hash functions (summary functions) that generate a 128-bit value based on an encoded source (original text) of any length.

[0096] By using the MD5 hash function, the original data is converted to 128 bits regardless of the size of the original data, so any RFID reader 1 with a memory capacity of 128 bits or more can be used. Note that the code conversion process is not limited to the above-mentioned hash function such as MD5, and a code conversion process algorithm other than the hash function that can convert to a second code that is shorter than the first code may be used.

[0097] The RFID reader 1 sets the converted second code as the code of the RF tag 20. The FID reader 1 issues an RF tag 20 having the set code to be affixed to the object 10 .

[0098] Specifically, the RFID reader 1 uses, for example, software for printing the RF tag 20 to set the converted second code as the code of the RF tag 20. The RFID reader 1 transmits printing information (print data, number of prints, etc.) of the RF tag 20 having the set code to the printing device 3 through the software for printing the RF tag 20.

[0099] The printer 3 receives the printing information of the RF tag 20 transmitted from the RFID reader 1. The printer 3 prints the RF tag 20 based on the received printing information of the RF tag 20. The vendor attaches the printed RF tag 20 to the object 10.

[0100] 13 is a flowchart showing the processing procedure when performing the code conversion process. The control unit 11 of the RFID reader 1 reads the two-dimensional code 19 attached to the target object 10 via the code reading unit 16 (step S121). The control unit 11 acquires a first code of the two-dimensional code 19 from the read two-dimensional code 19 (step S122). The control unit 11 converts the acquired first code into a second code that is shorter than the first code, for example, by using an MD5 hash function (step S123).

[0101] The control unit 11, for example, uses RF tag 20 printing software to set the converted second code as the code of the RF tag 20 (step S124). The control unit 11 generates printing information (print data, number of prints, etc.) of the RF tag 20 having the set code through the RF tag 20 printing software (step S125). The control unit 11 transmits the generated printing information of the RF tag 20 to the printer 3 via the communication unit 13 (step S126). The control unit 11 ends the process.

[0102] According to this embodiment, the second code converted from the first code of the two-dimensional code attached to the object 10 can be set as the code of the RF tag 20.

[0103] According to this embodiment, the code conversion process for the two-dimensional code allows the two-dimensional code used on the system side to be used as is, eliminating the need to modify the system, thereby making it possible to reduce operational costs.

[0104] (Embodiment 3) The third embodiment relates to a form in which a two-dimensional code affixed to an object 10 and a two-dimensional code corresponding to the code of an RF tag 20 affixed to the object 10 are stored in association with each other. Note that a description of the contents that overlap with the first and second embodiments will be omitted.

[0105] Fig. 14 is an explanatory diagram showing an example of a record layout of the read information DB 171 in the embodiment 3. Note that the same reference numerals are used to denote the same contents as in Fig. 3, and the description thereof will be omitted. The read information DB 171 includes a first two-dimensional code string and a second two-dimensional code string.

[0106] The first two-dimensional code string stores the code of a first two-dimensional code affixed to the object 10. The second two-dimensional code string stores the code of a second two-dimensional code printed on the surface of the RF tag 20 affixed to the object 10, the code corresponding to the code of the RF tag 20.

[0107] FIG. 15 is an explanatory diagram for explaining a process of storing a first two-dimensional code and a second two-dimensional code in association with each other. The screen includes an RF tag 20, a first two-dimensional code 31, and a second two-dimensional code 32. The first two-dimensional code 31 is a code attached to an object 10. The second two-dimensional code 32 is a two-dimensional code corresponding to the code of the RF tag 20. That is, the code of the RF tag 20 and the code of the second two-dimensional code 32 match.

[0108] The RFID reader 1 reads the first two-dimensional code 31 attached to the object 10. The RFID reader 1 acquires the code of the first two-dimensional code 31 from the first two-dimensional code 31 that it has read.

[0109] The RFID reader 1 reads the second two-dimensional code 32 corresponding to the code of the RF tag 20. The RFID reader 1 acquires the code of the second two-dimensional code 32 from the second two-dimensional code 32 that it has read.

[0110] The RFID reader 1 associates the read code of the first two-dimensional code 31 and the read code of the second two-dimensional code 32 with each other and stores them in the read information DB 171. Specifically, the RFID reader 1 associates the read code of the first two-dimensional code 31, the read code of the second two-dimensional code 32, and the code of the RF tag 20 that matches the code of the second two-dimensional code 32 with each other and stores them in the read information DB 171.

[0111] 16 is a flow chart showing a processing procedure for storing a first two-dimensional code and a second two-dimensional code in association with each other. The control unit 11 of the RFID reader 1 reads the first two-dimensional code attached to the target object 10 by the code reading unit 16 (step S131). The control unit 11 obtains the code of the first two-dimensional code from the read first two-dimensional code (step S132).

[0112] The control unit 11 reads the second two-dimensional code corresponding to the code of the RF tag 20 by the code reading unit 16 (step S133). The control unit 11 acquires the code of the second two-dimensional code from the read second two-dimensional code (step S134).

[0113] The control unit 11 associates the code of the first two-dimensional code with the code of the second two-dimensional code and stores them in the read information DB 171 of the mass storage unit 17 (step S135). The control unit 11 ends the process. Note that the data in which the code of the first two-dimensional code is associated with the code of the second two-dimensional code may be stored on the server 2 side.

[0114] Since the code of the RF tag 20 and the code of the second two-dimensional code 32 match, by performing the above-mentioned processing, the code of the RF tag 20, the code of the first two-dimensional code 31, and the code of the second two-dimensional code 32 are stored in correspondence with each other in the reading information DB 171.

[0115] According to this embodiment, it is possible to store a two-dimensional code attached to an object 10 and a two-dimensional code corresponding to the code of the RF tag 20 attached to the object 10 in association with each other.

[0116] According to this embodiment, when the RF tag 20 associated with a two-dimensional code is attached to the object 10, visual matching with the two-dimensional code is not required, which makes it possible to reduce the workload.

[0117] According to this embodiment, since radio waves are not required, it is possible to prevent errors in linking the original code (first two-dimensional code 31) with the two-dimensional code (second two-dimensional code 32) corresponding to the code of the RF tag 20.

[0118] (Embodiment 4) The fourth embodiment relates to an embodiment in which information on an object 10 is obtained by reading a two-dimensional code corresponding to the code of an RF tag 20 attached to the object 10, and a report file is created based on the obtained information on the object 10. Note that a description of the contents that overlap with the first to third embodiments will be omitted.

[0119] Fig. 17 is an explanatory diagram showing an overview of an RF tag matching system in embodiment 4. Note that the same reference numerals are used for the same contents as in Fig. 1, and the description thereof will be omitted.

[0120] As shown in the figure, an RF tag 20 having a two-dimensional code printed thereon corresponding to the code of the RF tag 20 is affixed to an object 10. An EPC number 201 and a two-dimensional code 202 including the EPC number 201 are printed on the surface of the RF tag 20. Note that the information printed on the surface of the RF tag 20 is not limited to the items described above, and may be any characters, numbers, or the like.

[0121] Fig. 18 is a block diagram showing an example of the configuration of the server 2 in the fourth embodiment. Note that the same reference numerals are used for the same contents as in Fig. 5, and the description thereof will be omitted. The large-capacity storage unit 25 includes an object information DB 252. The object information DB 252 stores information on the object 10. Note that the information on the object 10 will be described later.

[0122] 19 is an explanatory diagram showing an example of a record layout of the object information DB 252. The object information DB 252 includes a UID column, an object image column, a name column, a model number column, a two-dimensional code column, an EPC column, a size column, a damage size column, a damage level column, a damage cause column, a damage image column, a work type column, a contractor column, a warehouse column, and an occurrence date and time column.

[0123] The UID column stores the UID of the object 10 for identifying the object 10. The object image column stores image data of the object 10, such as a packaging image. The name column stores the name of the object 10. The model number column stores the model number of the object 10. The two-dimensional code column stores the two-dimensional code 202 printed on the surface of the object 10. The EPC column stores the EPC contained in the two-dimensional code 202.

[0124] The size column stores size data of the object 10. The damage size column stores size data of the damage of the object 10. The damage level column stores the damage level of the object 10. The damage levels will be described later. The damage cause column stores damage causes such as breakage, crushing, dirt, or dents. The damage image column stores damage image data obtained by photographing the damaged portion of the object 10.

[0125] The work type column stores the type of work including the time of arrival and the time of transport by a lifter. The contractor column stores information identifying the contractor who performed the work on the object 10, such as the ID or name of the contractor. The warehouse column stores information identifying (specifying) the warehouse in which the object 10 is stored, such as the ID or name of the warehouse. The occurrence date and time column stores information on the date and time when damage to the object 10 occurred.

[0126] The RFID reader 1 reads the two-dimensional code 202 corresponding to the code of the RF tag 20, thereby acquiring the code of the two-dimensional code 202. The code of the two-dimensional code includes the EPC of the object 10.

[0127] The RFID reader 1 acquires the UID of the object 10. For example, if the UID of the object 10 is configured as a part of the EPC, the RFID reader 1 acquires the UID of the object 10 from the EPC included in the acquired two-dimensional code 202. The UID of the object 10 can be obtained by using a UID data file to which the UID is assigned. For example, when the RFID reader 1 reads the RF tag 20 attached to the object 10 for the first time, the RFID reader 1 may obtain the UID from the data file.

[0128] The RFID reader 1 acquires information about the object 10. The information about the object 10 includes image data, name, model number, size data, damage information about damage, an image of the object 10, and the like.

[0129] Specifically, the RFID reader 1 accepts input of the name, model number, type of work (when receiving or transporting, etc.) of the object 10, the name of the contractor who performed the work on the object 10, and the name of the warehouse storing the object 10. The name and model number of the object 10 may be described in the code of the two-dimensional code 202 in association with the EPC of the object 10. The RFID reader 1 acquires image data of the object 10 via the imaging unit 18.

[0130] The RFID reader 1 measures the size (length, width, and height) of the target object 10. For example, if the RFID reader 1 is equipped with a LiDAR (Light Detection And Ranging) sensor, the RFID reader 1 measures the size of the target object 10 using the LiDAR sensor. Note that the measurement of the size of the target object 10 is not limited to the LiDAR sensor. For example, a contractor may manually measure the size of the target object 10.

[0131] The RFID reader 1 acquires damage information regarding damage to the target object 10. The damage information includes, for example, a damage size, a damage level, a damage cause (for example, breakage, crushing, dirt, or dent), or damage image data.

[0132] The damage level may be set in advance to a plurality of levels according to the damage size, etc. In this embodiment, the damage levels are set to damage level L (small), damage level M (medium), and damage level H (large). For example, when the damage size is less than "L: 5 cm x W: 5 cm", the damage level is set to damage level L. Or, when the damage size is "L: 5 cm x W: 5 cm" or more and less than "L: 10 cm x W: 10 cm", the damage level is set to damage level M. Or, when the damage size is "L: 10 cm x W: 10 cm" or more, the damage level is set to damage level H. The damage level may be set arbitrarily, and for example, 10 levels from level 0 to level 9 may be set.

[0133] For example, the RFID reader 1 uses a LiDAR sensor to measure the damage size of the target object 10. The RFID reader 1 accepts input of the damage level, the damage factor, and the like by the contractor according to the measured damage size.

[0134] The damage information may be acquired using a learning model trained by machine learning, deep learning, etc. For example, when a damage image showing damage to the object 10 is input, the RFID reader 1 may acquire the damage level and the damage factor by using a learning model trained to output the damage level and the damage factor of the object 10.

[0135] The RFID reader 1 acquires damage image data including the damaged area of ​​the target object 10 via the photographing unit 18.

[0136] The RFID reader 1 transmits the two-dimensional code 202 of the object 10, the code (EPC) of the two-dimensional code 202, and information on the object 10 to the server 2 in association with the acquired UID of the object 10. The information on the object 10 includes image data, name, model number, size data, and damage information on the object 10 (damage size, damage level, and damage degree). This includes images, etc.

[0137] The server 2 receives the UID of the object 10, the two-dimensional code 202 of the object 10, the code of the two-dimensional code 202, and the information of the object 10 transmitted from the RFID reader 1. The server 2 stores the two-dimensional code 202 of the object 10, the code of the two-dimensional code 202, and the information of the object 10 in the object information DB 252 in association with the received UID of the object 10.

[0138] 20 is a flowchart showing a processing procedure when information on the object 10 is transmitted to the server 2. The control unit 11 of the RFID reader 1 reads the two-dimensional code 202 corresponding to the code of the RF tag 20 attached to the object 10 via the code reading unit 16 (step S141). The control unit 11 acquires the EPC of the object 10 (the code of the two-dimensional code 202) from the read two-dimensional code 202 (step S142).

[0139] The control unit 11 accepts input of the name and model number of the object 10 through the input unit 14 (step S143). Note that the input is not limited to the name and model number of the object 10, and other items (e.g., product type) may also be accepted. The control unit 11 acquires image data of the object 10 through the photographing unit 18 (step S144).

[0140] The control unit 11 measures the size of the target object 10 using, for example, a LiDAR sensor mounted on the RFID reader 1 (step S145). The control unit 11 acquires size data of the measured target object 10 (step S146).

[0141] The control unit 11 acquires damage information regarding damage to the target object 10 (step S147). The damage information includes a damage size, a damage level, a damage factor, and damage image data. The damage information may be acquired, for example, by a LiDAR sensor or a learning model trained based on machine learning or the like.

[0142] The control unit 11 transmits the acquired UID, two-dimensional code 202, EPC, and information on the object 10 to the server 2 via the communication unit 13 (step S148). The information on the object 10 includes image data, name, model number, size data, and damage information on the damage of the object 10 (damage size, damage level, damage cause, damage image, etc.).

[0143] The control unit 21 of the server 2 receives the UID, two-dimensional code 202, EPC, and information on the object 10 transmitted from the RFID reader 1 through the communication unit 23 (step S241). The control unit 21 stores the two-dimensional code 202, EPC, and information on the object 10 in the object information DB 252 of the mass storage unit 25 in association with the received UID of the object 10 (step S242). The control unit 21 ends the process.

[0144] Next, a process for creating a report file based on information about the target object 10 will be described.

[0145] 21 is a flowchart showing the processing procedure for creating a report file. The control unit 11 of the RFID reader 1 transmits the UID of the target object 10 to the server 2 via the communication unit 13 (step S151). The control unit 21 of the server 2 receives the UID of the target object 10 transmitted from the RFID reader 1 via the communication unit 23 (step S251).

[0146] Based on the received UID of the object 10, the control unit 21 generates a report file including the two-dimensional code 202 corresponding to the code of the RF tag 20 attached to the object 10, the code 201 (EPC number 201) of the two-dimensional code 202, and information on the object 10. Creation information is obtained from the object information DB 252 of the mass storage unit 25 (step S252).

[0147] The information on the object 10 includes image data, name, model number, size data, damage size, damage level, damage cause, or damage image data of the object 10. The control unit 21 creates a report file based on the acquired information for creating the report file (step S253). The control unit 21 displays (outputs) the created report file on the display unit 26 (step S254). The control unit 21 ends the process. Note that the report file creation and display process may be executed on the RFID reader 1 side.

[0148] 22 is an explanatory diagram showing an example of a report file. The report file includes an EPC display field 13a, a basic information display field 13b, a size display field 13c, a damage information display field 13d, and an image display field 13e.

[0149] The EPC display column 13a is a display column that displays the two-dimensional code 202 corresponding to the code of the RF tag 20 and the EPC number 201 included in the two-dimensional code 202. The basic information display column 13b is a display column that displays basic information of the object 10, such as the name and model number.

[0150] The size display field 13c is a display field that displays size data of the object 10. The damage information display field 13d is a display field that displays damage information of the object 10. The image display field 13e is a display field that displays image data of the object 10.

[0151] Based on the UID of the object 10, the server 2 acquires, from the object information DB 252, information for creating a report file including the two-dimensional code 202 and EPC number 201 corresponding to the code of the RF tag 20 affixed to the object 10, and information on the object 10. The information on the object 10 includes image data, name, model number, size data, damage size, damage level, damage cause, and damage image data of the object 10.

[0152] The server 2 creates a report file based on the acquired two-dimensional code 202 and EPC, and the information on the target object 10. The server 2 displays the created report file on a screen.

[0153] As shown in the figure, in the report file, an EPC number 201 and a two-dimensional code 202 are displayed in an EPC display field 13a, and a name and model number are displayed in a basic information display field 13b. In addition, size data of the object 10 is displayed in a size display field 13c, and damage image data, damage size, damage level, and cause of the object 10 are displayed in a damage information display field 13d. In addition, image data of the object 10 is displayed in an image display field 13e.

[0154] The format of the report file and the items in the report file are not limited to those described above. The format and items of the report file may be set appropriately depending on the type of the target object 10, etc.

[0155] Next, a process for outputting a graph based on the damage information of the object 10 will be described.

[0156] The server 2 acquires damage information on the damage to the object 10 to which the RF tag 20 is attached from the object information DB 252. The damage information includes the type of work and the contractor when the damage occurred, the warehouse where the object 10 is stored, the date and time when the damage occurred, and the like.

[0157] Server 2 performs a calculation for each work and each unit period (e.g., month) based on the acquired damage information. The server 2 creates a fifth graph showing the number of objects 10 on which damage has occurred in each unit period, by business operator, based on the acquired damage information. The server 2 creates a sixth graph showing the number of objects 10 on which damage has occurred in each unit period, by business operator, based on the acquired damage information.

[0158] The server 2 creates a seventh graph showing the number of objects 10 that have suffered damage per unit period by warehouse based on the acquired damage information. The server 2 displays (outputs) at least one of the created fifth graph, sixth graph, and seventh graph on the screen.

[0159] 23 is an explanatory diagram showing an example of a display screen for the fifth graph. This screen includes a fifth graph display field 18a. The fifth graph display field 18a is a display field for displaying the fifth graph.

[0160] The server 2 acquires damage information including the type of work when the damage occurred to the object 10 and the date and time of the damage from the object information DB 252. The server 2 counts up the number of objects 10 for which damage occurred per unit period (e.g., month) for each work based on the acquired type of work and date and time of the damage. The server 2 creates a fifth graph based on the counted results. The server 2 displays the created fifth graph in the fifth graph display field 18a.

[0161] As shown, the fifth graph is shown in the form of a stacked vertical bar graph. The horizontal axis of the fifth graph indicates a unit period (e.g., January to December), and the vertical axis indicates the number of objects 10 on which damage has occurred. The vertical axis of the fifth graph is broken down into the number of objects 10 on which damage has occurred, corresponding to "at the time of arrival," "at the time of transportation," and "other," respectively. "At the time of arrival" is illustratively indicated by hatching diagonally upward to the right. "At the time of transportation" is illustratively indicated by hatching diagonally downward to the right. "Other" is illustratively indicated without hatching.

[0162] As shown in the figure, the fifth graph displays the number of objects 10 for which damage occurred, corresponding to "at the time of arrival," "during transportation," and "other," by month from January to December.

[0163] 24 is an explanatory diagram showing an example of a display screen for the sixth graph. This screen includes a sixth graph display field 18b. The sixth graph display field 18b is a display field for displaying the sixth graph.

[0164] The server 2 acquires damage information including the contractor when the damage occurred to the object 10 and the date and time of the image from the object information DB 252. The server 2 counts up the number of objects 10 where damage occurred per unit period (e.g., month) for each contractor based on the acquired contractor and date and time of the image. The server 2 creates a sixth graph based on the counted result. The server 2 displays the created sixth graph in the sixth graph display field 18b.

[0165] As shown, the sixth graph is shown in the form of a stacked vertical bar graph. The horizontal axis of the sixth graph indicates a unit period (e.g., January to December), and the vertical axis indicates the number of objects 10 on which damage has occurred. The vertical axis of the sixth graph is broken down into the number of objects 10 on which damage has occurred corresponding to each trader (e.g., trader A, trader B, and trader C). "Trader A" is illustratively shown with diagonal hatching going up to the right. "Trader B" is illustratively shown with diagonal hatching going down to the right. "Trader C" is illustratively shown without hatching.

[0166] As shown in the figure, the sixth graph displays the number of objects 10 on which damage occurred corresponding to each of "Company A," "Company B," and "Company C" by month from January to December.

[0167] 25 is an explanatory diagram showing an example of a display screen for the seventh graph. This screen includes a seventh graph display field 18c. The seventh graph display field 18c is a display field for displaying the seventh graph.

[0168] The server 2 acquires damage information including the warehouse in which the damaged object 10 is stored and the date and time of the image from the object information DB 252. The server 2 counts up the number of damaged objects 10 for each unit period (e.g., month) for each warehouse based on the acquired warehouse and date and time of image occurrence. The server 2 creates a seventh graph based on the counted results. The server 2 displays the created seventh graph in the seventh graph display field 18c.

[0169] As shown, the seventh graph is shown in the form of a stacked vertical bar graph. The horizontal axis of the seventh graph indicates a unit period (e.g., January to December), and the vertical axis indicates the number of objects 10 on which damage has occurred. The breakdown of the vertical axis of the seventh graph is the number of objects 10 on which damage has occurred corresponding to each warehouse (e.g., AA Warehouse, BB Warehouse, and CC Warehouse). The "AA Warehouse" is exemplarily shown with diagonal hatching that slopes upward to the right. The "BB Warehouse" is exemplarily shown with diagonal hatching that slopes downward to the right. The "CC Warehouse" is exemplarily shown without hatching.

[0170] As shown in the figure, the seventh graph displays the number of damaged objects 10 corresponding to each of the "AA Warehouse", "BB Warehouse" and "CC Warehouse" by month from January to December.

[0171] Although the fifth, sixth and seventh graphs described above are in the form of stacked vertical bar graphs, they are not limited to this and may be in other graph forms (for example, stacked horizontal bar graphs or pie charts).

[0172] 26 is a flowchart showing a processing procedure for outputting a graph based on damage information of the object 10. The control unit 21 of the server 2 acquires damage information including the type of work and the contractor when the damage occurred, the warehouse storing the object 10, and the date and time when the damage occurred, from the object information DB 252 of the mass storage unit 25 (step S41).

[0173] The control unit 21 counts the number of objects 10 on which damage has occurred for each task and month based on the acquired task type and occurrence date and time (step S42). The control unit 21 creates a fifth graph based on the counted results (step S43).

[0174] The control unit 21 counts the number of objects 10 on which damage has occurred for each month and for each business operator based on the acquired business operator and the date and time of occurrence (step S44). The control unit 21 creates a sixth graph based on the counted results (step S45).

[0175] Based on the acquired warehouses and occurrence dates and times, the control unit 21 tally up the number of objects 10 for which damage has occurred for each warehouse and month (step S46). The control unit 11 creates a seventh graph based on the tally up results (step S47).

[0176] The unit period is not limited to a month, but may be a day, a week, half a year, or a specific time period (eg, 8:00 to 12:00).

[0177] The control unit 21 displays (outputs) the created fifth, sixth and seventh graphs on the display unit 26 (step S48). The control unit 11 ends the process.

[0178] 26 illustrates an example in which the fifth, sixth, and seventh graphs are simultaneously displayed on the screen, but the present invention is not limited to this. For example, the control unit 21 may display at least one of the fifth, sixth, and seventh graphs that have been created on the screen.

[0179] The server 2 transmits the created fifth, sixth and seventh graphs to other terminals. The creation and display processing of the fifth, sixth and seventh graphs may be executed on the RFID reader 1 side.

[0180] According to this embodiment, it is possible to output (transmit) to the server 2 a two-dimensional code corresponding to the code of the RF tag 20 attached to the object 10 and information about the object 10.

[0181] According to this embodiment, it is possible to output (transmit) size data of the object 10 or damage information relating to damage to the object 10 to the server 2 as information of the object 10.

[0182] According to this embodiment, it is possible to create a report file based on the information of the target object 10.

[0183] According to the present embodiment, at least one of the fifth graph, sixth graph, and seventh graph based on the damage information of the object 10 can be output.

[0184] (Embodiment 5) The fifth embodiment relates to a form in which the position of each object 10 is output on a map based on the position information of each object 10. Note that a description of the contents that overlap with the first to fourth embodiments will be omitted.

[0185] Fig. 27 is an explanatory diagram showing an example of a record layout of the management DB 251 in the fifth embodiment. Note that description of contents overlapping with Fig. 6 will be omitted. The management DB 251 includes an arrival column, an inventory column, and a shipping column. Each of the arrival column, the inventory column, and the shipping column includes a position information column.

[0186] The position information column in the arrival column stores position information of the object 10 when the object 10 arrives. The position information may be, for example, longitude and latitude, a location name, or a warehouse name. The position information column in the inventory column stores position information of the object 10 when the object 10 is inventoryed. The position information column in the shipping column stores position information of the object 10 when the object 10 is shipped.

[0187] First, a process of storing the position information of the object 10 to which the RF tag 20 is attached in association with the reading by the RFID reader 1 will be described.

[0188] Fig. 28 is a flow chart showing a processing procedure for storing the position information of the target object 10. Note that the same reference numerals are used for the contents that overlap with Fig. 7, and the description thereof will be omitted.

[0189] After executing the process of step S103, the control unit 11 of the RFID reader 1 acquires the position information of the target object 10 (step S105). For example, if the RFID reader 1 is equipped with a GPS (Global Positioning System, Global Positioning Satellite) module, the control unit 11 may acquire the position of the target object 10 through the GPS module. Note that the position information (e.g., the name of the location or the name of the warehouse) may be manually input by the business operator. Also, the business operator may select a position from a plurality of positions registered in advance.

[0190] The control unit 11 transmits the stored UID of the object 10, the code of the RF tag 20, the read date and time, the work attributes, and the position information to the server 2 via the communication unit 13 (step S106). The control unit 21 of the server 2 receives the UID of the object 10, the code of the RF tag 20, the read date and time, the work attributes, and the position information transmitted from the RFID reader 1 via the communication unit 23 (step S203).

[0191] The control unit 21 stores the work attribute status, the read date and time, and the position information in the management DB 251 in association with the received UID of the target object 10 and the code of the RF tag 20 (step S204). The control unit 21 ends the process.

[0192] 29 is an explanatory diagram showing an example of a map screen showing the position of the target object 10. The screen includes a map display field 14a, a position list 14b, a position marker 14c, and a position display label 14d.

[0193] The map display field 14a is a display field that displays a map for displaying the position of each object 10. The location list 14b is a display field that displays a list of detailed location information of each object 10. The location marker 14c is a mark or symbol that indicates the location of the object 10 on the map. The location display label 14d is a label that displays information such as the UID and location of the object 10.

[0194] The server 2 acquires, from the management DB 251, the read date and time and position information corresponding to the reading of each object 10, based on the UID of each object 10. Specifically, the server 2 acquires, from the management DB 251, the read date and time and position information corresponding to multiple readings (e.g., three times) of each object 10, based on the UID of each object 10.

[0195] Although FIG. 29 illustrates an example in which the reading is performed multiple times, the present invention is not limited to this example, and only the reading date and time and position information corresponding to the most recent reading of the target object 10 may be obtained.

[0196] The server 2 acquires a map from, for example, a map providing server or the like through the communication unit 23. The server 2 displays the acquired map in the map display field 14a. The server 2 displays a marker indicating the position of each object 10 in the corresponding position marker 14c on the map displayed in the map display field 14a, based on the position information corresponding to the most recent reading of each object 10.

[0197] Furthermore, the server 2 displays the UID of each object 10 and the read date and time corresponding to the most recent read of each object 10 on the map displayed in the map display field 14a in the corresponding position display label 14d.

[0198] The server 2 displays in the position list 14b the UID of each object 10, the read date and time corresponding to the most recent (current) read of each object 10, and location information corresponding to multiple reads (e.g., the most recent, previous, and the time before last) of each object 10. Note that a map screen showing the location of the object 10 may be displayed on the RFID reader 1 side.

[0199] 30 is a flowchart showing a processing procedure for outputting the position of the object 10 on a map. The control unit 21 of the server 2 acquires the position information corresponding to the reading of each object 10 from the management DB 251 of the mass storage unit 25 based on the UID of each object 10 (step S261).

[0200] The control unit 21 acquires a map from, for example, a map providing server or the like through the communication unit 23 (step S262). The control unit 21 displays (outputs) the acquired position information of each object 10 on the acquired map through the display unit 26 (step S263). For example, the control unit 21 may display the position of each object 10 on the map with a position marker. The control unit 21 ends the process.

[0201] According to this embodiment, the position of each object 10 can be visualized by outputting the position of each object 10 on a map.

[0202] (Embodiment 6) The sixth embodiment relates to a mode for identifying a shelf in which the object 10 can be stored. Note that a description of the contents that overlap with the first to fifth embodiments will be omitted.

[0203] Fig. 31 is a block diagram showing a configuration example of the server 2 in the sixth embodiment. Note that the same reference numerals are used for the contents overlapping with Fig. 18, and the description thereof will be omitted. The large-capacity storage unit 25 includes a shelf DB 253. The shelf DB 253 stores information on the shelf on which the object 10 is stored.

[0204] 32 is an explanatory diagram showing an example of a record layout of the shelf DB 253. The shelf DB 253 includes a shelf number column, a space number column, a storage size column, a storage status column, a UID column, and a shelf map column. The shelf number column stores a shelf number for identifying each shelf. The space number column stores space numbers provided to distinguish spaces (areas) within a shelf.

[0205] The storage size column stores the size (length, width, and height) that can be stored in the space. The storage status column stores the storage status of the space (e.g., stored or available for storage). The UID column stores the UID of the object 10 stored in the space. The shelf map column stores shelf map data.

[0206] 33 is a flowchart showing the process steps for identifying a shelf on which the object 10 can be stored. The control unit 11 of the RFID reader 1 measures the size of the object 10 to be stored, for example, using a LiDAR sensor mounted on the RFID reader 1 (step S171). The control unit 11 acquires size data of the measured object 10 (step S172). The control unit 11 transmits the acquired size data to the server 2 via the communication unit 13 (step S173).

[0207] The control unit 21 of the server 2 receives the size data transmitted from the RFID reader 1 through the communication unit 23 (step S271). When the size data of the object 10 is stored in the object information DB 252, the control unit 21 may acquire the size data from the object information DB 252.

[0208] The control unit 21 of the server 2 acquires shelf storage information from the shelf DB 253 of the mass storage unit 25 (step S272). The storage information includes shelf position information, storable size data, storage status of the space in the shelf (stored or storable), UID of the object 10 stored in the space in the shelf, or a shelf map, etc. The shelf position information includes the shelf number of each shelf and the space number in each shelf, etc.

[0209] Based on the acquired shelf storage information and the received size data of the object 10, the control unit 21 identifies the shelf number of the shelf in which the object 10 can be stored and the space number within the shelf (step S273).

[0210] Specifically, the control unit 21 extracts the shelf number of the shelf including the space capable of storage and the space number capable of storage within the shelf from the storage information based on the acquired storage status (stored or available for storage) of the space within each shelf. The control unit 21 compares the size data of the object 10 with the storage size of the extracted space capable of storage. If the size of the object 10 is less than the storage size of the space capable of storage, the control unit 21 identifies the space as a space capable of storage within the shelf.

[0211] The control unit 21 transmits the shelf number of the specified shelf and the space number within the shelf through the communication unit 23. The server 2 transmits the information to the RFID reader 1 (step S274). The control unit 11 of the RFID reader 1 receives the shelf number of the shelf and the space number within the shelf transmitted from the server 2 via the communication unit 13 (step S174). The control unit 11 displays (outputs) the received shelf number of the shelf and the space number within the shelf on the display unit 15 (step S175). The control unit 11 ends the process.

[0212] The process of identifying the shelf on which the target object 10 can be stored may be performed on the RFID reader 1 side.

[0213] Next, a process for displaying the storage status of each shelf based on the shelf storage information will be described.

[0214] 34 is an explanatory diagram showing an example of a display screen of the storage status of shelves. The screen includes a shelf map display field 15a, a first graph display field 15b, and a details display field 15c.

[0215] The shelf map display field 15a is a display field that displays the shelf numbers on which the objects 10 are stored and a shelf map including the storage status of each shelf. The first graph display field 15b is a display field that displays a first graph showing the ratio of stored space to available space within a shelf where objects can be stored. The detail display field 15c is a display field that displays detailed information such as the stored space numbers and available space numbers.

[0216] The server 2 acquires shelf storage information including the shelf number of each shelf, the space number within the shelf, storage size data, the storage status of the space within the shelf (stored or storage available), and the shelf map, etc. from the shelf DB 253. The server 2 displays the acquired shelf map and shelf number in the shelf map display field 15a.

[0217] The server 2 determines whether each shelf is available for storage based on the storage status of the space in each shelf. If there is no available storage space in a shelf, the server 2 determines that the shelf is already stored. If there is available storage space in a shelf, the server 2 determines that the shelf is available for storage.

[0218] As shown in the figure, the shelves where items are stored (shelf numbers: A, B, C, and D) are exemplarily indicated with diagonal hatching that slopes downward to the right. Also, in the shelf where items can be stored (shelf number: E), the stored spaces are exemplarily indicated with diagonal hatching that slopes downward to the right, and the storable spaces are exemplarily indicated without hatching.

[0219] In addition, the server 2 displays the space numbers of the storage space and the storage space in the storage shelf in the detail display field 15c. As shown in the figure, the storage space numbers are E1 and E2, and the storage space number is E3.

[0220] The server 2 creates a first graph based on the storage status of the available space in the shelf. The server 2 displays the created first graph in the first graph display field 15b.

[0221] The first graph is a graph showing the ratio of the stored space to the available storage space in the shelf. As shown in the figure, the first graph is shown in the form of a pie chart. The ratio of the stored space (full) is 70%, and the ratio of the available storage space (empty) is 30%. Note that the first graph is not limited to a pie chart, and may be various graphs such as a bar graph or a line graph.

[0222] FIG. 35 is a flow chart showing the processing procedure for outputting the shelf map and the first graph. Note that the same reference numerals are used for the contents that overlap with those in FIG. 33, and the description thereof will be omitted. After executing the process of step S274, the control unit 21 of the server 2 displays storage information including each shelf number, storage status (stored or available for storage), and space number within the shelf where storage is possible on the shelf map (step S275).

[0223] The control unit 21 creates a first graph showing the ratio of the space already stored in the shelf to the space available for storage (step S276). The control unit 21 displays (outputs) the created first graph on the display unit 26 (step S277). The control unit 21 ends the process.

[0224] The server 2 may transmit the created first graph to another terminal. The creation and display process of the first graph may be executed on the RFID reader 1 side.

[0225] According to this embodiment, it is possible to specify a shelf on which the object 10 can be stored, based on the shelf position information and the size data of the object 10.

[0226] According to this embodiment, it is possible to output a map and a first graph showing the storage status of the shelves.

[0227] (Embodiment 7) The seventh embodiment relates to a form in which a graph relating to an inventory of the object 10 is output. Note that a description of the contents that overlap with the first to sixth embodiments will be omitted. An inventory is to check the number of the object 10 in stock.

[0228] Fig. 36 is a block diagram showing a configuration example of the server 2 in the seventh embodiment. The same reference numerals are used for the contents that overlap with Fig. 31, and the description thereof will be omitted. The large-capacity storage unit 25 includes an inventory count DB 254 and an inventory management DB 255. The inventory count DB 254 stores the number of objects 10 for each inventory count of the objects 10. The inventory management DB 255 stores information such as the number of objects 10 in stock.

[0229] FIG. 37 is an explanatory diagram showing an example of the record layout of the inventory count DB 254 and the inventory management DB 255.

[0230] The inventory count DB 254 includes a year / month column, an inventory count column, and a number of objects column. The year / month column stores the year and month when the inventory was conducted. The inventory count column stores the number of times an inventory of the objects 10 was conducted (e.g., 0, 1, 2, 3, or 4 times). The object number column stores the number of objects 10 corresponding to each inventory count.

[0231] The number of inventory counts and the number of objects 10 for each inventory count are tallied from the management DB 251. Specifically, the server 2 acquires from the management DB 251 the read date and time of the code of the RF tag 20 affixed to each object 10 during inventory, when the inventory status of the object 10 is "inventory completed" during a predetermined period (for example, January 2023). The server 2 tallies up the number of inventory counts for each UID of the object 10 during the predetermined period, based on the acquired read date and time during inventory of the object 10. The server 2 tallies up the number of objects 10 corresponding to the tallied number of inventory counts during the predetermined period, from the management DB 251.

[0232] The inventory management DB 255 includes a year / month column, an inventory quantity column, and an actual inventory quantity column. The year / month column stores the target year / month for managing the inventory quantity of the object 10. The inventory quantity column stores the number of the object 10 that should be in stock for each year / month. The actual inventory quantity column stores the actual inventory quantity of the object 10 for each year / month.

[0233] The stock quantity is tallied from the management DB 251. Specifically, the server 2 acquires from the management DB 251 the read date and time of the code of the RF tag 20 affixed to each object 10 at the time of arrival, when the inventory status of the object 10 is "arrival completed" for the month (January 2022) preceding the target year and month (for example, February 2022). The server 2 tallies the number of arrivals of the object 10 in the month preceding the target year and month as the stock quantity for the target year and month, based on the acquired read date and time of the object 10 at the time of arrival.

[0234] The actual stock quantity is obtained from the number of arrivals and the number of shipments. Specifically, the server 2 obtains from the management DB 251 the read date and time of the code of the RF tag 20 affixed to each object 10 at the time of shipment, when the inventory status of the object 10 is "shipped completed" for the month before the target month. The server 2 counts up the number of shipments of the object 10 in the month before the target month, based on the obtained read date and time of the object 10 at the time of shipment. The server 2 calculates the difference between the total number of arrivals and the number of shipments of the object 10 for the month before the target month. The server 2 obtains the calculated difference as the actual stock quantity for the target month.

[0235] A second graph can be created showing the percentage of times that an inventory was taken of the objects 10 having the RF tags 20 attached thereto during a predetermined period of time. The predetermined period of time may be, for example, the last month or a specified month.

[0236] 38 is an explanatory diagram showing an example of a display screen for the second graph. This screen includes a second graph display field 16a. The second graph display field 16a is a display field for displaying the second graph.

[0237] The server 2 acquires the number of objects 10 corresponding to each inventory count during a predetermined period (e.g., last month) from the inventory count DB 254. For example, the number of objects 10 in four inventory counts is 3420, the number of objects 10 in three inventory counts is 1368, the number of objects 10 in two inventory counts is 1368, and the number of objects 10 in one inventory count is 684.

[0238] The server 2 creates a second graph showing each ratio of the number of inventory counts in a predetermined period based on the inventory count information including the number of objects 10 corresponding to each inventory count in the predetermined period.

[0239] Specifically, the server 2 calculates each ratio of the number of inventory counts based on the number of objects 10 corresponding to each number of inventory counts. The server 2 creates a second graph showing each ratio based on each calculated ratio of the number of inventory counts. The server 2 displays the created second graph in the second graph display field 16a.

[0240] As shown in the figure, the second graph is shown in the form of a pie chart. The percentage of four counts is 50%, the percentage of three counts is 20%, the percentage of two counts is 20%, and the percentage of one count is 10%. Note that the second graph is not limited to a pie chart, and may be various graphs such as a bar graph or a line graph.

[0241] 39 is a flowchart showing the processing procedure when outputting the second graph. The control unit 21 of the server 2 acquires the number of objects 10 corresponding to each number of inventory counts during a predetermined period (e.g., last month) from the inventory count DB 254 of the mass storage unit 25 (step S281). The inventory count information includes the predetermined period and the number of objects 10 corresponding to each number of inventory counts during the predetermined period.

[0242] The control unit 21 calculates each ratio of the number of inventory counts based on the number of objects 10 corresponding to each number of inventory counts included in the inventory count information (step S282). Based on each ratio of the number of inventory counts, a second graph showing each ratio is created (step S283). The control unit 21 displays the created second graph on the display unit 26 (step S284). The control unit 21 ends the process.

[0243] The server 2 may transmit the created second graph to another terminal. The creation and display process of the second graph may be executed on the RFID reader 1 side.

[0244] In addition, a third graph can be created including a graph showing, over time, the number of objects 10 with RF tags 20 attached thereto during a predetermined period, and a graph showing, over time, an inventory rate for indicating the error between the number that should be in stock and the actual number in stock of the objects 10. The predetermined period may be, for example, January to May 2022.

[0245] 40 is an explanatory diagram showing an example of a display screen of the third graph. The screen includes a third graph display field 16b. The third graph display field 16b is a display field for displaying the third graph. The third graph includes a graph 16b_1 and a graph 16b_2.

[0246] The graph 16b_1 is a graph showing the number of objects 10 with RF tags 20 attached thereto in a predetermined period in a time series. The graph 16b_2 is a graph showing the inventory rate in a time series, which indicates the error between the number of objects 10 that should be in stock and the actual number of objects 10 in stock.

[0247] The server 2 acquires from the management DB 251 the number of objects 10 that should be in stock and the actual number of objects 10 in stock for each predetermined unit (for example, month) during a predetermined period (for example, January to May 2022).

[0248] The server 2 creates a graph 16b_1 showing the stock quantity of the target object 10 in a time series for each predetermined unit (e.g., month) based on the actual stock quantity of the target object 10 for a predetermined period. The server 2 displays the created graph 16b_1 in the third graph display field 16b.

[0249] As shown in the figure, graph 16b_1 is shown in the form of a vertical bar graph. The horizontal axis of graph 16b_1 indicates a period (for example, January to May 2022). The vertical axis of graph 16b_1 indicates the inventory quantity of object 10. Graph 16b_1 displays the inventory quantity of object 10 by month from January to May 2022.

[0250] The server 2 calculates the inventory rate (the difference between the number of objects that should be in stock and the actual number of objects in stock) for the object 10 for each predetermined unit (e.g., month) based on the number of objects that should be in stock and the actual number of objects in stock for the acquired period. The server 2 creates a graph 16b_2 based on the calculated inventory rate. The server 2 displays the created graph 16b_2 in the third graph display field 16b.

[0251] As shown in the figure, graph 16b_2 is shown in the form of a broken line. Graph 16b_2 is a line showing the change in the inventory rate to represent the error between the number of objects 10 that should be in stock and the actual number of objects in stock from January to May 2022.

[0252] Although FIG. 40 shows a vertical bar graph and a line graph, the present invention is not limited to this and other graph formats may be used.

[0253] 41 is a flowchart showing a processing procedure for outputting the third graph. The control unit 21 of the server 2 acquires the number of objects 10 that should be in stock and the actual number of objects 10 in stock for each predetermined unit (e.g., month) according to a predetermined period (e.g., January to May 2022) from the management DB 251 of the mass storage unit 25 (step S291).

[0254] The control unit 21 creates an inventory quantity graph (graph 16b_1) that shows the inventory quantity of the target item 10 over time for a specified period, based on the actual inventory quantity of the target item 10, for each specified unit (e.g., month) (step S292).

[0255] The control unit 21 calculates the inventory rate of the object 10 for each predetermined unit (e.g., month) based on the number of the object 10 that should be in stock for the predetermined period and the actual number of the object 10 in stock (step S293). The control unit 21 creates an inventory rate graph (graph 16b_2) based on the calculated inventory rate (step S294).

[0256] The control unit 21 creates a third graph including the created inventory quantity graph and inventory rate graph (step S295). The control unit 21 displays (outputs) the created third graph on the display unit 26 (step S296). The control unit 21 ends the process.

[0257] The server 2 may transmit the created third graph to another terminal. The creation and display process of the third graph may be executed on the RFID reader 1 side.

[0258] According to this embodiment, it is possible to output a second graph showing the percentage of times that an inventory of the objects 10 has been carried out.

[0259] According to this embodiment, it is possible to output a third graph including a graph showing the stock quantity of the target object 10 over time and a graph showing the inventory rate of the target object 10 over time.

[0260] (Embodiment 8) The eighth embodiment relates to a form in which a graph relating to the inventory retention period of the object 10 is output. Note that a description of the contents that overlap with the first to seventh embodiments will be omitted.

[0261] For the object 10 that has been shipped out, the inventory hold period of the object can be calculated. The inventory hold period is calculated based on the difference in date and time between the object's entry date and time and its departure date and time. A fourth graph can be created based on the calculated proportion of each inventory hold period.

[0262] 42 is an explanatory diagram showing an example of a display screen of the fourth graph. This screen includes a fourth graph display field 17a. The fourth graph display field 17a is a display field that displays the fourth graph. The server 2 acquires from the management DB 251 the read date and time (warehousing date and time) of the code of the RF tag 20 affixed to each object 10 at the time of arrival, and the read date and time (shipment date and time) of the code of the RF tag 20 affixed to each object 10 at the time of shipment.

[0263] The server 2 calculates the inventory retention period of each of the acquired objects 10 based on the difference between the storage date and time and the shipment date and time of the object 10. For example, the server 2 calculates inventory retention periods including "within one month," "one month to three months," and "three months or more."

[0264] The server 2 creates a fourth graph showing the calculated proportion of each inventory hold period. Specifically, the server 2 counts the number of objects 10 corresponding to each inventory hold period. For example, the number of objects 10 in "one month or less" is 5120, the number of objects 10 in "one month to three months" is 2080, and the number of objects 10 in "three months or more" is 640.

[0265] The server 2 calculates the ratio of each inventory hold period based on the total number of objects 10 corresponding to each inventory hold period. The server 2 creates a fourth graph showing the calculated ratio of each inventory hold period. The server 2 displays the created fourth graph in the fourth graph display field 17a.

[0266] As shown in the figure, the fourth graph is shown in the form of a pie chart. The percentage of "within one month" is 65%, the percentage of "one month to three months" is 27%, and the percentage of "three months or more" is 8%. Note that the fourth graph is not limited to a pie chart, and may be various graphs such as a bar graph or a line graph.

[0267] 43 is a flowchart showing the processing procedure when outputting the fourth graph. The control unit 21 of the server 2 acquires, from the management DB 251 of the mass storage unit 25, the read date and time of the code of the RF tag 20 affixed to each object 10 at the time of arrival as the storage date and time (step S21). The control unit 21 acquires, from the management DB 251 of the mass storage unit 25, the read date and time of the code of the RF tag 20 affixed to each object 10 at the time of shipment as the shipping date and time (step S22).

[0268] The control unit 21 calculates the inventory retention period of the target object 10 based on the difference between the acquired storage date and time and the storage date and time (step S23). The control unit 21 tallies the number of targets 10 corresponding to each calculated inventory retention period (step S24).

[0269] The control unit 21 calculates the ratio of each inventory hold period based on the total number of objects 10 corresponding to each inventory hold period (step S25). The control unit 21 creates a fourth graph showing the calculated ratio of each inventory hold period (step S26). The control unit 21 displays (outputs) the created fourth graph on the display unit 26 (step S27). The control unit 21 ends the process.

[0270] The server 2 may transmit the created fourth graph to another terminal. The creation and display process of the fourth graph may be executed on the RFID reader 1 side.

[0271] According to this embodiment, it is possible to output a fourth graph showing the proportion of each inventory retention period of the objects 10.

[0272] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims.

[0273] The matters described in each embodiment can be combined with each other. In addition, the independent claims and dependent claims described in the claims can be combined with each other in any combination regardless of the reference format. Furthermore, the claims use a format in which a claim references two or more other claims (multiple claim format), but this is not limited to this format. [Explanation of symbols]

[0274] 1 RFID reader 11 Control section 12 Storage section 13. Communications Department 14 Input section 15 Display 16 Code reader 17 Mass storage 171 Reading information DB 172 Reference Files 18. Photography Department 1P control program 2. Information processing device (server computer; server) 20 RF Tag 21 Control section 22 Memory section 23 Communications Department 24 Reading unit 25 Mass storage 251 Management DB 252 Object Information DB 253 Shelf DB 254 Inventory count DB 255 Inventory Management DB 26 Display section 2a Portable storage media 2b Semiconductor memory 2P control program 3 Printing device

Claims

1. Each time the RFID reader reads the code of the RF tag, the read RF tag code is stored in association with the date and time when the RFID reader reads the code and the work attribute. Transmitting the stored code of each RF tag, the date and time, and the work attributes to a server computer; The server computer, The code of each RF tag is stored in association with the date and time and the work attributes. Information processing methods.

2. A reference file that stores a plurality of RF tags to be read is stored in the RFID reader; When a plurality of the RF tags are read, the reference file is referenced to determine whether the plurality of the RF tags are read excessively or insufficiently. The information processing method according to claim 1 .

3. Referencing the reference file and accepting a selection of an item in the reference file; Display a list of RF tags to be read that correspond to the received items The information processing method according to claim 2 .

4. When the RF tag is read, if the RF tag is not stored in the reference file, information indicating that the RF tag is not a target for reading is output. The information processing method according to claim 2 .

5. Acquire a first code of the two-dimensional code attached to the object; The acquired first code is converted into a second code which is shorter than the first code. The converted second code is set as the code of the RF tag. The information processing method according to claim 1 .

6. A first code is obtained by reading a two-dimensional code attached to an object with the RFID reader; Using a hash function, convert the obtained first code into a second code that is shorter than the first code; The converted second code is set as the code of the RF tag; An RF tag having the set code is issued to be attached to the object. The information processing method according to claim 1 .

7. A first two-dimensional code attached to an object is read by the RFID reader to obtain a code of the first two-dimensional code; a second two-dimensional code corresponding to the code of the RF tag printed on the surface of the RF tag attached to the object is read by the RFID reader, thereby acquiring the code of the second two-dimensional code; The acquired first two-dimensional code and the acquired second two-dimensional code are stored in association with each other. The information processing method according to claim 1 .

8. Acquire a two-dimensional code of an object to which an RF tag is attached, the two-dimensional code being printed on the RF tag and corresponding to the code of the RF tag; Acquire information about the object; Transmitting the acquired object information and code to the server computer. The information processing method according to claim 1 .

9. Measuring the size of the object; The measured size data of the object is transmitted to the server computer as information of the object. The information processing method according to claim 8.

10. Obtaining damage information regarding damage to the object; The acquired damage information and an image of the object are transmitted to the server computer as information of the object. The information processing method according to claim 8.

11. creating a report file including information on the object, including size data, damage information, and an image of the object, a two-dimensional code of the object, and a code of the two-dimensional code; Output the created report file The information processing method according to claim 8.

12. storing location information of the object to which the RF tag is attached in association with the reading by the RFID reader; Based on the location information of each object, output the location of each object on a map. The information processing method according to claim 1 .

13. Identifying a shelf capable of storing the object to be stored based on position information of a shelf where each object to which the RF tag is attached has been stored and size data of the object to be stored; Output the identified storage shelf The information processing method according to claim 1 .

14. creating a first graph showing a ratio of stored space to available space in the shelf based on the storage status of the identified available space in the shelf; Output the map showing the storage status of each shelf and the first graph created. The information processing method according to claim 13.

15. creating a second graph showing the percentage of times that an inventory of the objects to which the RF tags are attached was conducted during a predetermined period of time; Output the second graph you created The information processing method according to claim 1 .

16. creating a third graph including a graph showing the number of objects to which the RF tags are attached in a time series during a predetermined period, and a graph showing an inventory rate in a time series for indicating an error between the number of objects that should be in stock and the actual number of objects in stock; Output the third graph you created The information processing method according to claim 1 .

17. Calculating the inventory retention period of an object having an RF tag attached thereto that has been released from the warehouse based on the difference between the entry date and time of the object and the exit date and time of the object; Create a fourth graph showing the calculated percentage of each inventory hold period, Output the fourth graph you created The information processing method according to claim 1 .

18. Acquire damage information regarding damage to the object to which the RF tag is attached; creating a fifth graph showing the number of the objects that have been damaged per unit time period for each operation including the time of arrival and the time of transportation by a lifter based on the damage information; creating a sixth graph showing the number of the objects that have been damaged per unit period for each business based on the damage information; creating a seventh graph showing the number of the objects that have been damaged per unit period for each warehouse storing the objects based on the damage information; At least one of the fifth graph, the sixth graph, and the seventh graph is output. The information processing method according to claim 1 .

19. Each time the code of the RF tag is read, the read code of the RF tag is stored in association with the date and time when the code was read and the work attribute. The stored code of each RF tag, the date and time, and the work attributes are transmitted to a server computer. A non-transitory computer-readable recording medium that records a program for causing a computer to execute a process.

20. An RFID reader including a control unit, The control unit is Each time the code of the RF tag is read, the read code of the RF tag is stored in association with the date and time when the code was read and the work attribute. The stored code of each RF tag, the date and time, and the work attributes are transmitted to a server computer. RFID reader.

21. An information processing system including an RFID reader having a first control unit and a server computer that stores information read by the RFID reader, The first control unit is Each time the RFID reader reads a code of an RF tag, the read RF tag code is stored in association with the date and time when the RFID reader reads the code and the work attribute. Transmitting the stored code of each RF tag, the date and time, and the work attributes to a server computer; The server computer includes a second control unit, The second control unit is receiving the code, date and time, and work attributes of each RF tag transmitted by the first control unit; The received code of each RF tag is stored in association with the date and time and the work attributes. An information processing system comprising:

Images