ITEM MANAGEMENT SYSTEM, METHOD, AND INFORMATION PROCESSING APPARATUS

An item management system includes a reading apparatus capable of reading, from a wireless device, identification information stored in the wireless device; a management unit configured to manage, in a database, a list of one or more items that are subject to a work by a user and a status of each item regarding the work; and a first wireless device attached to a first item included in the list and storing first identification information associated with the first item. The management unit updates the status of the first item when it is determined that the reading apparatus has read the first identification information from the first wireless device in a state where a first user has logged into the item management system and a first user operation representing a start of the work regarding the list has been detected.

BACKGROUND OF THE INVENTION

Field of the Invention

The present disclosure relates to an item management system, a method, and an information processing apparatus.

Background Art

Radio frequency identification (RFID) is a technology that allows information embedded in a small device which is also referred to as a tag to be read by an external reader through short-range wireless communication. For example, an RFID tag in which unique identification information is embedded is attached to an item so that a location of the item can be efficiently known in item stock and distribution management and that visualization of information on managed items becomes easier. Among others, a passive type RFID tag, which transmits information utilizing energy of electromagnetic wave emitted from a reader, does not require a battery, leading to low manufacturing cost and semipermanent operation. Hence, it has become widely-used not only in the stock and distribution management but also in various applications.

Patent Literature 1 discloses an example of a system which makes use of RFID tags for item stock management purpose. The system of Patent Literature 1 can easily determine, at timings of arrival, shipping and inventory counting, stock statuses by a server gathering and processing information that has been read by a reader (also referred to as a scanner) from RFID tags attached to items, for example.

CITATION LIST

Patent Literature

When considering to make use of the RFID technology in situations such as inventory or distribution management where reliability is required in updating information, there is sometimes an issue of trade-off between simplicity of tag reading by a tag reader and the reliability in updating information based on reading results. For example, assume that a plurality of users are carrying tag readers and are working in a place where items to be shipped to a transaction partner or items having arrived from a partner are inspected. In a case where each tag reader is always operating, results of tag reading from RFID tags are accumulated over time without user's intentional operation on the tag readers. Such reading results include mixture of ones that should lead to information update and the others that should not, and it is not easy for the system to distinguish between them. Such an inconvenience will not occur if the tag readers are activated only when the information should be updated. However, in that case, there would be other problems that operations to repeatedly turn on and off a tag reader are cumbersome, and that a tag reader is erroneously kept in off-state at a timing when it should be active.

In light of the foregoing, the present invention aims at enhancing reliability of updating item management statuses based on results of tag reading.

SUMMARY OF THE INVENTION

According to an aspect, there is provided an item management system including: a reading apparatus capable of reading, from a wireless device, identification information stored in the wireless device; a management unit configured to manage, in a database, a list of one or more items that are subject to a work by a user and a status of each item regarding the work; and a first wireless device attached to a first item included in the list and storing first identification information associated with the first item, wherein the management unit is configured to update the status of the first item when it is determined that the reading apparatus has read the first identification information from the first wireless device in a state where a first user has logged into the item management system and a first user operation representing a start of the work regarding the list has been detected. A corresponding method and an information processing apparatus are also provided.

DESCRIPTION OF THE EMBODIMENTS

1. SYSTEM OVERVIEW

FIG.1is a schematic view illustrating an example of a configuration of an item management system1according to an embodiment. Herein, the item management system1is a system for managing statuses of works such as confirmation before shipment of items and inspection on items that have arrived. Note that the technology according to the present disclosure is not limited to the above examples, and may be applied to various applications that involve updates of statuses regarding item management. An item may be a non-living object (for example, a machine, equipment, a tool, material, a consumable good, a component, a vehicle, or a robot) or a living object (for example, an animal or a plant).

FIG.1illustrates two places10aand10bunder management of the item management system1. There are a user20a, and items30a,30band30cin the place10a. There are a user20b, and an item30din the place10b. The users20aand20bcan freely move across the places10aand10b(and other places).

The item management system1makes use of wireless devices, which are also referred to as tags, for the purpose of item management. In the present embodiment, the item management system1includes three types of tags. A first type of tags (first wireless devices) are item tags which are attached to respective items managed in the item management system1. A second type of tags (second wireless devices) are user tags carried by users. A third type of tags (third wireless devices) are position tags which are installed in respective places in which a work is conducted by the users in the item management system1.

In the example ofFIG.1, position tags40aand40bare installed in the places10aand10b, respectively. The installation position of each of the position tags40aand40bmay be fixed or can be changed. When a place itself moves (for example, a work-site may move), the corresponding position tag may be relocated in conjunction with the movement of the place. Item tags50a,50b,50cand50dare attached to the items30a,30b,30cand30d, respectively. Each item tag moves as a corresponding item moves. The user20acarries a user tag60a, and the user20bcarries a user tag60b. The user tags60aand60bmay be IC card-type devices such as employee ID cards or admission cards, for example. Note that, in this specification, the expression that a user carries a certain target should broadly comprehend various modes in which the user moves together with the target (for example, moves in a state where he or she holds or wears the target, etc.).

In the following descriptions, the places10aand10bare collectively referred to as places10by omitting the trailing characters from the reference signs when they do not need to be distinguished from each other. The same applies to the items30(items30a,30b, . . . ), the position tags40(40a,40b, . . . ), the item tags50(item tags50a,50b, . . . ), and the user tags60(user tags60a,60b, . . . ), as well as any other elements. The number of places10and the number of items30managed in the item management system1are not limited to the example illustrated inFIG.1but may be any numbers. Likewise, the number of users20utilizing the item management system1is also not limited to the example illustrated inFIG.1but may be any number.

In the present embodiment, each of the tags such as the position tags40, the item tags50and the user tags60is assumed to be a passive-type RFID tag (a passive tag). A passive tag is composed of: a small integrated circuit (IC) chip with an embedded memory; and an antenna, and has identification information for identifying the tag and some other information stored in the memory. In this specification, identification information is simply referred to as an ID, and identification information for identifying a tag is referred to as a tag ID. It should be noted that the tag ID may be considered as information for identifying an object to which the tag is attached. The IC chip of a passive tag operates by utilizing energy of an electromagnetic wave emitted from a tag reader, and modulates the information such as the tag ID and some other information stored in the memory into an information signal to transmit (send back) the information signal from the antenna.

In the example ofFIG.1, the item tags50a,50b,50cand50dhave specific tag IDs51a,51b,51cand51dembedded in the tags, respectively. The tag ID51(first identification information) of each item tag50is associated with the item30to which the item tag50is attached in a database described below. The user tags60aand60balso have respective specific tag IDs embedded in the tags. The tag ID (second identification information) of each user tag60is associated with the user20who carries the user tag60. The position tags40aand40balso have respective specific tag IDs embedded in the tags. The tag ID (third identification information) of each position tag40is associated with the place in which the position tag40is installed.

It should be noted that, in another embodiment, each tag may be an active-type RFID tag. If each tag actively (for example, periodically) transmits information to its vicinity by utilizing power from a built-in battery, such a tag may be called a beacon tag. In a further embodiment, each tag may be a wireless device which sends back information in response to a signal from a reader in accordance with Near Field Communication (NFC) protocol or Bluetooth (registered trademark) protocol, for example. Each tag may have any name such as an IC tag, an IC card, or a responder.

The user20acarries a tag reader100aand a user terminal160ain addition to the user tag60a. The user20bcarries a tag reader100band a user terminal160bin addition to the user tag60b. The tag reader100and the user terminal160may be considered to constitute a portable system that is carried by the user20. The item management system1includes such a portable system, and a management server200. One or both of the tag readers100and the user terminals160, and the management server200are connected to a network5. The network5may be a wired network, a wireless network, or any combination thereof. Examples of the network5may include the Internet, an intranet, and a cloud network.

The tag reader100is a reading apparatus that is capable of reading, from wireless devices such as RFID tags, information stored in the wireless devices. The tag reader100can detect an item30to which an item tag50is attached by reading a tag ID51from the item tag50, for example. The tag reader100performs reading periodically or in response to a certain trigger such as a user operation, and transmits a tag reading result to the management server200. The tag reader100may be capable of communicating with the management server200directly or indirectly via a certain relay apparatus (for example, the user terminal160). An example of a particular configuration of the tag reader100will be further described below.

The user terminal160may be any type of terminal apparatus such as a notebook personal computer (PC), a tablet PC, a smartphone, or a smart watch, for example. The user terminal160may be utilized for the item management system1to interact with a user20. An example of a particular configuration of the user terminal160will be further described below.

The management server200is an information processing apparatus that manages work-related statuses, position information and other information of a plurality of items30in a database. The management server200may be implemented as an application server, a database server, or a cloud server by using a high-end general-purpose computer, for example. The management server200receives tag reading results from tag readers100, and updates the database based on the received tag reading results. An example of a particular configuration of the management server200will be further described below.

Though a single management server200is illustrated inFIG.1, the functions of the management server200, which will be described in detail below, may be provided by a single apparatus or by physically-separate multiple apparatuses which operate in conjunction with each other. In addition, though an example where the management server200maintains a database will be described in the present embodiment, an apparatus other than the management server200may maintain a part or all of the database. For example, a part of data may be maintained by a wireless device, a tag reader100or a user terminal160.

Note thatFIG.1shows an example where the tag reader100and the user terminal160are physically-separate apparatuses. However, the tag reader100may have a part or all of the functions of the user terminal160described below, or the user terminal160may have a part or all of the functions of the tag reader100described below, for example. Moreover, the functions of the management server200described in the present embodiment may be realized within the user terminal160.

2. CONFIGURATION EXAMPLE OF TAG READER

FIG.2is a block diagram illustrating an example of a configuration of the tag reader100according to an embodiment. With reference toFIG.2, the tag reader100comprises a control unit111, a storage unit112, a communication unit113, a measuring unit114, an operation unit115, and a reading unit116.

The control unit111consists of a memory to store computer programs, and one or more processors (for example, central processing units (CPUs)) to execute the computer programs. The control unit111controls overall functionality of the tag reader100described in this specification. For example, the control unit111causes the reading unit116to perform reading from an RFID tag within a tag reading range, and causes the storage unit112to temporarily store the read information, the time of the reading and the received signal level as reading result data. In parallel to the reading from RFID tags, the control unit111also causes the measuring unit114to measure the position of the tag reader100, and the storage unit112to store a measurement result Then, the control unit111transmits, to the management server200via the communication unit113, the reading result data and the measurement result data stored in the storage unit112together with reader identification information (also referred to as a reader ID) that identifies the apparatus itself.

The storage unit112may include any kind of storage medium such as a semiconductor memory (a read only memory (ROM), a random access memory (RAM), or the like), an optical disk, or a magnetic disk, for example. In the present embodiment, the storage unit112stores the above-described reading result data, measurement result data, and the reader ID of the tag reader100.

The communication unit113is a communication interface for the tag reader100to communicate with the management server200. For example, the communication unit113may be a wireless local area network (WLAN) interface that communicates with a WLAN access point, or a cellular communication interface that communicates with a cellular base station. Alternatively, the communication unit113may be a connection interface (e.g. a Bluetooth (registered trademark) interface or a universal serial bus (USB) interface) for connection with a relay apparatus.

The measuring unit114is a unit that is capable of measuring a position of the tag reader100. In the present embodiment, the measuring unit114uses the self-localization technique, also referred to as pedestrian dead reckoning (PDR) to measure an amount of relative movement of the tag reader100from a certain reference position, and outputs the measured amount of movement to the control unit111. The reference position of measurement of the amount of relative movement may be, for example, the position of the tag reader100at the time when the tag reader100is activated. The measuring unit114may have sensors including a three-axis acceleration sensor, a gyro sensor, and a geomagnetic sensor to perform PDR, for example. As described below, in the present embodiment, the positional coordinates of the installation position of each position tag40is known and registered in a database. Therefore, the control unit111can estimate the current (positional coordinates of) absolute position of the tag reader100based on the amount of relative movement from the point in time when it detected a position tag40to the current point in time, and the known positional coordinates of that position tag40.

In another embodiment, the measuring unit114may measure the current geographical position of the tag reader100by utilizing the global positioning system (GPS). In yet another embodiment, the measuring unit114may perform base station positioning or wireless LAN positioning in which the current position is estimated by utilizing known positional coordinates of a base station or a wireless LAN access point to which the apparatus is connected.

The operation unit115detects a user operation. The operation unit115includes physical input devices such as a button, a switch, or a lever disposed on a housing of the tag reader100, for example. The operation unit115detects an operation by the user20through an input device, and outputs an operation signal to the control unit111. In addition, the operation unit115may include an audio input interface such as a microphone.

The reading unit116is a unit that is capable of reading, from each of the tags such as the position tags40, the item tags50, and the user tags60described above, information stored in the tag. With reference toFIG.2, the reading unit116includes an RF controller120, a power amplifier121, a filter122, a first coupler123, a second coupler124, an antenna125, a power detector126, and a canceler127. The RF controller120outputs a transmission signal (for example, a signal modulated in the UHF band) from a TX terminal to the power amplifier121in accordance with control by the control unit111. The power amplifier121amplifies the transmission signal input from the RF controller120to output it to the filter122. The amplification rate of the transmission signal here may be controllable in variable manner, and a higher amplification rate will enhance an output strength of an electromagnetic wave emitted from the tag reader100. The filter122may be a low-pass filter, for example, and filters out unnecessary frequency components from the transmission signal amplified by the power amplifier121. The first coupler123distributes the transmission signal that has passed the filter122to the coupler124and the power detector126. The second coupler124outputs the transmission signal input from the first coupler123to the antenna125, and outputs a received signal input from the antenna125to the RF controller120. The antenna125transmits the transmission signal input from the coupler124to the air as an electromagnetic wave. Further, the antenna125receives a signal that has been sent back from an RFID tag that exists within the reading range of the tag reader100in response to the transmission signal, and outputs the received signal to the coupler124. As an example, the antenna125may be an omnidirectional antenna. As another example, the antenna125may be a directional antenna of which beam direction can be variably controlled. The power detector126detects a power level of the signal input from the first coupler123, and outputs a signal ‘RF_DETECT’ indicative of the detected power level to the control unit111. The canceler127receives a signal ‘CARRIER_CANCEL’ indicative of a power level of a carrier from the control unit111. Then, the canceler127cancels the carrier component of the received signal at the second coupler124from the antenna125based on the CARRIER_CANCEL, and thereby extracts an intended signal component of the received signal to be output to the RX terminal of the RF controller120. The RF controller120demodulates the signal input from the RX terminal to obtain a tag ID and other information sent back from the RFID tag, and outputs the obtained information to the control unit111. The RF controller120also measures a reception level (also referred to as received strength) of the signal input from the RX terminal, and outputs the measurement result to the control unit111.

In the present embodiment, the reading unit116can attempt tag reading periodically (for example, once per second) without requiring any explicit command from a user. Data transmission from the communication unit113to the management server200can also be performed periodically (for example, every few seconds) or whenever the tag reading is done without requiring any explicit command from a user. The control unit111may exclude, from the data to be transmitted, the same record as the most recent record that has already been transmitted in a predetermined time period to omit redundant data transmission and reduce a communication load. When a reception level of a received signal from an RFID tag exceeds a preset minimum detection level, the control unit111may determine to have detected the RFID tag, and transmit a reading result data about the detected RFID tag to the management server200. Noted that, in another embodiment, one or both of an attempt of tag reading by the reading unit116and data transmission to the management server200may be performed in response to detecting a user input via the operation unit115. In a case where the communication unit113performs communication with the management server200indirectly via a relay apparatus, the data transmission to the management server200may be performed only while there is an effective connection between the communication unit113and the relay apparatus.

3. CONFIGURATION EXAMPLE OF USER TERMINAL

FIG.3is a block diagram illustrating an example of a configuration of the user terminal160according to an embodiment. With reference toFIG.3, the user terminal160comprises a control unit161, a storage unit162, a communication unit163, a connection unit164, an operation unit165, and a display unit166.

The control unit161consists of a memory to store computer programs, and one or more processors (for example, CPUs) to execute the computer programs. The control unit161controls overall functionality of the user terminal160described in this specification. For example, when a work by a user such as pre-shipment confirmation or acceptance inspection is carried out in the item management system1, the control unit161accesses the management server200via the communication unit163, and causes the display unit166to display an application screen provided by the management server200. On this screen, the user20can give an instruction to start or stop updating a work status, or can check its progress. Some examples of application screens provided by the management server200will further be described below.

The storage unit162may include any kind of storage medium such as a semiconductor memory (ROM, RAM, or the like), an optical disk, or a magnetic disk, for example. In the present embodiment, the storage unit162temporarily store work-related information received from the management server200described below for the purpose of screen display, for example.

The communication unit163is a communication interface for the user terminal160to communicate with the management server200. For example, the communication unit163may be a WLAN interface or a cellular communication interface.

The connection unit164is a connection interface for connecting the user terminal160to peripheral equipment. For example, the connection unit164may be a Bluetooth (registered trademark) interface or a USB interface. In a case where the user terminal160relays communications between the tag reader100and the management server200, the connection unit164establishes a communication connection with the tag reader100.

The operation unit165receives operations or information inputs from the user20. The operation unit165includes input devices such as a touch sensor, a key pad, a keyboard, a button, or a pointing device, for example. The operation unit165detects an operation by the user20through an input device, and outputs an operation signal to the control unit161. In addition, the operation unit165may further include some other types of input devices including an audio input interface such as a microphone, a sensor to detect a vibration, or the like.

4. CONFIGURATION EXAMPLE OF MANAGEMENT SERVER

4-1. Basic Configuration

FIG.4is a block diagram illustrating an example of a configuration of the management server200according to an embodiment. With reference toFIG.4, the management server200comprises a communication unit210, an item database (DB)220, and a management unit230.

The communication unit210is a communication interface for the management server200to communicate with other apparatuses. The communication unit210may be a wired communication interface or a wireless communication interface. In the present embodiment, the communication unit210communicates with the tag readers100and the user terminals160. The item DB220is a database that stores work-related statuses, position information and other information of each of a plurality of items under management of the system. In the present embodiment, the item DB220includes an item table310, a place table320, a reader table330, a user table340, a reading result table350, a work table370, and a work detail table380. The management unit230is a set of software modules that provide management functions for managing data within the item DB220. The individual software modules can run by one or more processors (not shown) of the management server200executing computer programs stored in a memory (not shown). In the present embodiment, the management unit230includes a tag processing unit231and a work management unit232.

4-2. Data Configuration Examples

The item table310has six data elements, namely Tag ID311, Item ID312, Name313, Type314, Place315, and Coordinates316. Tag ID311is identification information that uniquely identifies an item tag50attached to each of the items30under management of the system. The value of Tag ID311is the same as the value of the tag ID stored within the corresponding item tag50. Item ID312is identification information that uniquely identifies each item30. Name313represents a name of each item30. In the example ofFIG.5A, the items identified by item IDs “IT01”, “IT02”, “IT03” and “IT04” are given the names of “Item A”, “Item B”, “Item C” and “Item D”, respectively. “Item A”, “Item B”, “Item C” and “Item D” here may correspond respectively to the items30a,30b,30cand30dillustrated inFIG.1. Type314represents a type into which each item30is classified. In the example ofFIG.5A, the type of “Item A” and “Item B” is “Type 1”, and the type of “Item C” and “Item D” is “Type 2”. The values of Name313and Type314of each item30are determined by a user, and may be registered in advance via a user interface provided by the management unit230. Alternatively, the values of Name313and Type314may be stored in item tags50as item-related information and read by a tag reader100. In the latter case, upon initial tag reading from the item tag50of each item30, the management server200may receive the values of Name313and Type314of that item30from the tag reader100, and register them in the item table310. Place315represents a place where each item30has been last detected by a tag reader100with a place ID which identifies that place. In the example ofFIG.5A, “Item A”, “Item B” and “Item C” exist in the place identified by the place ID “PL01”. “Item D” exists in the place identified by the place ID “PL02”. Coordinates316represents positional coordinates of a point at which each item is estimated to be positioned. The values of Place315and Coordinates316may be updated by the tag processing unit231when the tag reader100has detected a movement of an item as will be described below.

The place table320has four data elements, namely Tag ID321, Place ID322, Name323, and Coordinates324. Tag ID321is identification information that uniquely identifies a position tag40installed in each of the places10under management of the system. The value of Tag ID321is the same as the value of the tag ID stored within the corresponding position tag40. Place ID322is identification information that uniquely identifies each place10. Name323represents a name of each place10. In the example ofFIG.5B, the name of the place10identified by the place ID “PL01” is “Place A”, and the name of the place10identified by the place ID “PL02” is “Place B”. Noted that these names may be, in practice, such as “Factory”, “Warehouse” and “Work Site”, for example. Coordinates324represents positional coordinates of an installation position of a position tag40installed in each place10.

In the present specification, the position information may be, for example, information indicating a certain position with positional coordinates or an identifier that identifies one of a plurality of predefined places. That is, each of Place315and Coordinates316of the item table310and Coordinates324of the place table320may serve as a kind of position information. The positional coordinates may be two-dimensional coordinates indicating a position in a horizontal plane, or may be three-dimensional coordinates that includes a component of height direction as well.

FIGS.6A to6Cillustrate respective configuration examples of the reader table330, the user table340, and the reading result table350.

The reader table330has three data elements, namely Reader ID331, Name332, and User333. Reader ID331is identification information that uniquely identifies each of the tag readers100utilized in the system. Name332represents a name of each tag reader. In the example ofFIG.6A, the tag readers100identified by reader IDs “RD01”, “RD02”, and “RD03” are given the names of “Reader A”, “Reader B”, and “Reader C”, respectively. User333identifies a user20who is using each tag reader with a user ID that identifies the user20. Some examples of techniques to determine which user20is using a certain tag reader100will be described below. Note that there may be a tag reader100of which associated user is unknown among the users20and the field of User333for such a tag reader100may be blank.

The user table340has four data elements, namely User ID341, Name342, Tag ID343, and Authentication Data344. User ID341is identification information that uniquely identifies each of the users20who utilize the item management system1. Name342represents a name of each user. In the example ofFIG.6B, the name of the user20identified by the user ID “U001” is “User A”, the name of the user20identified by the user ID “U002” is “User B”, and the name of the user20identified by the user ID “U003” is “User C”. Tag ID343is identification information that uniquely identifies a user tag60carried by each user20. The value of Tag ID343is the same as the value of the tag ID stored within the corresponding user tag60. Authentication Data344is an element in which data utilized for user authentication by each user20at the time of logging in the item management system1is stored. The user authentication may be performed with any authentication scheme such as password authentication or biometric authentication, for example.

The reading result table350is a table for accumulating records of reading result data received from the tag readers100(hereinafter referred to as reading result records). The reading result table350has five data elements, namely Reading Time351, Tag ID352, Reader ID353, Reception Level354, and Coordinates355. Reading Time351represents a time at which a tag ID was read for each reading result record. Tag ID352represents the tag ID that has been read for each reading result record. Reader ID353is identification information that identifies the tag reader100that has performed tag reading for each reading result record. In the example ofFIG.6C, the first record in the reading result table350indicates that the tag reader100identified by the reader ID “RD01” has read the tag ID “TGU1” (for example, the tag ID41aof the user tag60aof the user20a) at time “T01”. The second record indicates that the tag reader100has read the tag ID “TG01” (for example, the tag ID of the item tag50aof the item30a) at time “T02”. The third record indicates that the tag reader100has read the tag ID “TG02” (for example, the tag ID of the item tag50bof the item30b) at time “T03”. Reception Level354represents a reception level of a signal received by the tag reader100at the time of tag reading for each reading result record. Coordinates355represents positional coordinates of a point at which the tag reader100existed at the time of tag reading (that is, coordinates based on measurement result data received from the tag reader100).

FIG.7illustrates an example of a configuration of the work table370. The work table370is a table for storing information related to works to be carried out by the users20in the item management system1. The work table370has nine data elements, namely Work ID371, Work Type372, Deadline373, Place374, Transaction ID375, Registered-By376, Status377, Completed-At378, and Worker379. Work ID371is identification information that uniquely identifies each work. Work Type372represents a type of each work. In the present embodiment, the value of Work Type372may indicate “Shipment” or “Inspection”. In the example ofFIG.7, the types of works identified by work IDs “SH01” and “SH02” are set to “Shipment” representing pre-shipment confirmation, and the types of works identified by work IDs “AC01” and “AC02” are set to “Inspection” representing acceptance inspection. Deadline373represents a deadline by which each work should be completed. Place374represents a place in which each work is scheduled to be carried out with a place ID that identifies the place. Transaction ID375is identification information for associating each work with transaction information. Though it is not illustrated, the item DB220may further include a table that maintains transaction information such as a name of a transaction, a name of a transaction partner, an address, a name of person-in-charge, and a date of contract, for example, and Transaction ID375identifies a record of such transaction information. Registered-By376represents a name of a user20who registered each record of the work table370(hereinafter, referred to as a work record) in the work table370. Status377represents a status of work progression for each work record. The value of Status377may be “Uncompleted”, “In Progress”, “Completed” or “Deregistered”, for example. Completed-At378represents, for a work record of which work has already been completed, the time (date and time) at which the work was completed. Worker379represents a name of a user20who has completed each work. For work records for which Status377indicates “Uncompleted”, the fields of Completed-At378and Worker379may be blank.

FIG.8illustrates an example of a configuration of the work detail table380. The work detail table380is a table for maintaining a list of one or more target items of each work registered in the work table370and statuses regarding the work for respective items. The work detail table380has six data elements, namely Work ID381, Target Item382, Status383, Read-At384, Coordinates385, and Reader386. Work ID381is identification information that identifies one of work records registered in the work table370. Target Item382represents one of target items of the work identified by the value of Work ID381with an item ID that identifies the item. As seen inFIG.8, it is possible to register one or more target items for one work in the work detail table380. Status383represents whether tag reading for each target item has been completed or not. The value of Status383may be “Uncompleted”, “Completed” or “Deleted”, for example. In a case where the value of Status383indicates “Completed” for a certain target item, it means that confirmation on existence of the target item has been done in the corresponding work. Read-At384represents, for a target item of which tag has already been read, the time (date and time) at which the tag was read. Coordinates385represents, for a target item of which tag has already been read, positional coordinates of a point at which the tag was read. Reader386represents, for a target item of which tag has already been read, a tag reader100that has read the tag with a reader ID that identifies the tag reader100. For work records for which Status383indicates “Uncompleted”, the fields of Read-At384, Coordinates385and Reader386may be blank.

4-3. Position Tracking

The tag processing unit231processes the reading result data and the measurement result data received from the tag readers100. For example, the tag processing unit231adds, to the reading result table350, each record of reading result data received from the tag readers100via the communication unit210as a reading result record. When adding a reading result record to the reading result table350, the tag processing unit231determines values of positional coordinates to be set to Coordinates355based on measurement data received from the tag readers100. The values set to Coordinates355represent positional coordinates of a tag reader100at the time of reading the tag. The values may be sum of the positional coordinates of detection position of a position tag40and the amount of relative movement of the tag reader100from that detection position, for example.

Upon receiving reading result data for an item tag50, the tag processing unit231also updates the values of Coordinates316of the item table310. The values of Coordinates316of each item30in the item table310may be the same as the values of Coordinates355of the reading result record most-recently added to the reading result table350for that item30. Furthermore, the tag processing unit231also updates the field of Place315of the corresponding item30in the item table310in a case where the place10in which the item30exists has changed.

4-4. Work Status Management

The work management unit232accepts login by a user20to the item management system1, and provides a user terminal160of the user20who has logged in with an application screen related to a work to be carried out by the user20. The application herein may be a web browser or a dedicated application for item management that runs in the user terminal160, for example. The application screen may be displayed by the display unit166of the user terminal160. Prior to the login, the work management unit232causes the display unit166of the user terminal160to display a menu screen400as illustrated inFIG.9in response to an access from the user terminal160, for example.

With reference toFIG.9, the menu screen400includes five buttons401,402,403,404and405. When the user20operates the button401in the menu screen400, the work management unit232prompts the user20to input authentication information such as an ID and a password, for example, and perform user authentication based on the input authentication information. When the user authentication is successful, the user20enters a login state in the item management system1. The login state continues until the user20selects logout (or until a predetermined time length elapses without any operation being performed).

(1) Work Registration

The button402is a button for calling a management screen utilized when a shipment list is registered or modified. The button403is a button for calling a management screen utilized when an inspection list is registered or modified. Also when the user20operates the button402or403, the work management unit232may prompt the user20to input authentication information if he or she has not yet logged in, and perform user authentication. As a shipment list management screen and an inspection list management screen may have similar configurations, only the shipment list management screen will be described herein.

FIG.10illustrates the shipment list management screen410as an example. The shipment list management screen410includes radio buttons414,412, and413for the user to select a management option, for example. The radio button411may be selected when newly registering a shipment list. The radio button412may be selected when modifying a registered shipment list. The radio button413may be selected when deregistering a registered shipment list. Note that the shipment list herein means a list of one or more items that are subject to a pre-shipment confirmation.

The shipment list management screen410further includes a work ID field421and a transaction ID field422. The work ID field421displays a work ID corresponding to a shipment list to be newly registered or an existing shipment list to be modified. In the case of newly-registering a shipment list, the work management unit232may automatically assign a work ID corresponding to the shipment list to be newly registered such that it does not conflict with an existing work ID. The transaction ID field422accepts an input of a transaction ID corresponding to a shipment list to be newly registered or an existing shipment list to be modified, or displays a transaction ID that has already been input. In the case of modifying or deregistering a shipment list, the work management unit232searches the work table370for a corresponding work when the user20enters a work ID or a transaction ID in the corresponding field421or422. Then, the work management unit232obtains information related to a work specified as a result of the search from the work table370and the work detail table380, and reflect it in the shipment list management screen410. Note that the search key to search for an intended work is not limited to a work ID or a transaction ID, but may be any one or combination of information elements maintained in the item DB220.

The shipment list management screen410further includes radio buttons431and432for the user to select a search mode to search for a candidate item to be included in the shipment list, a reader ID field433, a reading time field434, and an item name field435. In addition, the shipment list management screen410includes a candidate display button436, a candidate item area441, an item list area442, an add icon443, a delete icon44, and an OK button451.

The radio button431may be selected when searching for a candidate item from results of tag reading by a tag reader100. When the user selects the radio button431, the user designates a reader ID and a reading time as search conditions in the reader ID field433and the reading time field434, and operates the candidate display button436. Then, the work management unit232extracts, from the reading result table350, a list of item tags50that were detected by the designated tag reader100at a time close to the designated time. Then, the work management unit232causes the list of items30corresponding to the extracted item tags50to be displayed in the candidate item area441.

The radio button432may be selected when searching for a candidate item by designating an item name of a specific item30. When the user selects the radio button432, the user designates a name of an intended item in the item name field435, and operates the candidate display button436. Then, the work management unit232specifies an item having the designated name in the item table310, and causes the specified item30to be displayed in the candidate item area441. The work management unit232may specify one or more items30by fuzzy search on item names based on a string designated in the item name field435, and cause the list of specified items30to be displayed in the candidate item area441.

In the example ofFIG.7, three pairs of item IDs and names of items30are displayed in the candidate item area441together with checkboxes. The user can add one or more candidate items to the shipment list by toggling the checkboxes of the candidate items displayed in the candidate item area441and operating the add icon443.

The item list area442is an area in which a list of target items included in the shipment list to be newly registered or being modified is displayed. In the example ofFIG.7, two pairs of item IDs and names of items30are displayed in the item list area442together with checkboxes. The user can delete one or more target items from the list by toggling the checkboxes of the target items displayed in the item list area442and operating the delete icon444.

Once the list of target items displayed in the item list area442is set as intended, the user operates the OK button451. Then, the work management unit232reflects the shipment list modified by the user and related information in the work table370and the work detail table380. For example, in the case of newly-registering a shipment list, the work management unit232adds a record of a newly-assigned work ID to the work table370. The information such as Deadline373and Place374of the work table370may be input through further input fields that are not illustrated in the figure, or may be obtained from another table based on the transaction ID. The work management unit232also adds one or more records, each identified by a pair of the work ID of the new shipment list and an item ID of a target item, to the work detail table380. The values of Status377of the newly-added record of the work table370and Status383of the newly-added records of the work detail table380are set to “Uncompleted”. On the other hand, in the case of modifying a shipment list, the work management unit232reflects the addition and deletion of the target items of the shipment list in the work detail table380.

In a case where the user wants to deregister an existing shipment list, he or she selects the radio button413and designates a work ID or a transaction ID of the intended shipment list in the field421or422. Then, the work management unit232extracts a list of target items of the corresponding work from the work detail table380, and causes it to be displayed in the item list area442. Then, when the user operates the OK button451, the work management unit232changes the value of Status377of a corresponding record in the work table370to “Deregistered”, for example.

Note that the shipment list management screen410described usingFIG.10is a mere example of a screen for managing work-related information and a list of target items. The management screen may have different screen configuration from the illustrated one. For example, a work list in a table form that is similar to the configuration of the work table370illustrated inFIG.7may be displayed on a screen, and a user may be allowed to select a work in the displayed list to transition therefrom to a management screen for the individual work.

(2) Update of Work Status

In the present embodiment, the work management unit232performs status update regarding a work (pre-shipment confirmation or acceptance inspection) registered in the work table370only in a state where the user20has logged into the item management system1and a user operation representing a start of the work has been detected. The user operation (first user operation) herein may be any type of operation such as a GUI operation or a speech operation. Typically, the first user operation is detected on the application screen provided by the work management unit232to the user terminal160of the login user. That is, upon detecting that the first user operation has been performed by the login user at the user terminal160, the work management unit232starts a status update session regarding a specific work. During this session, the work management unit232updates a status of a target item regarding the work to “Completed” when it is determined that the tag reader100has read the tag ID from the item tag50of the target item. The status update session may be terminated when status update for all of the target items has been completed, another user operation to instruct terminating the session has been detected, or a preset time length has elapsed. Examples of transition between application screens according to such embodiments will be described below.

Referring back toFIG.9, the button404of the menu screen400is a button for calling an application screen (hereinafter, referred to as shipment screen) utilized when a user20performs the pre-shipment confirmation. The button405is a button for calling an application screen utilized when a user20performs acceptance inspection. Also when the button404or405is operated, the work management unit232may prompt the user20to input authentication information if he or she has not yet logged in, and perform user authentication based on the input authentication information. As the configuration of the application screen for the acceptance inspection may be similar to the configuration of the application screen for the pre-shipment confirmation, only the application screen for the pre-shipment confirmation will be described herein.

FIGS.11A to11Cillustrate respective examples of the shipment screen provided for the pre-shipment confirmation. The shipment screen500aillustrated inFIG.11Aincludes a work ID field511and a related information display area512, a start reading button521, and an item list display area530, for example. The work ID field511is a field for the login user to select a work ID of an intended work. Herein, it is assumed that the login user is the user20a(whose name is “User A”). In the shipment screen500a, the work ID field511provides selectable options of work IDs of works of which work type is “shipment” in the work table370. The related information display area512is a display area for displaying work-related information for the selected work. The item list display area530is a display area for displaying a list of target items registered for the selected work.

In the example ofFIG.11A, the work ID “SH02” is selected in the work ID field511, and information related to the corresponding work including the transaction partner, work deadline, and work place is displayed in the related information display area512. The status of the selected work is displayed below the work ID field511, and the status is “Uncompleted” here. The value of this work status corresponds to the value of Status377of the work table370. In the item list display area530, item IDs, names, and reading statuses of three target items registered in the work detail table380for the selected work are displayed. Herein, the target items are “Item D”, “Item E” and “Item F”, and none of the target items has not yet been read. The value of the reading status of each target item displayed in the item list display area530corresponds to the value of Status383of the work detail table380(for example, “Uncompleted” may correspond to “NO”, and “Completed” may correspond to “YES”).

The above-described first user operation that is a condition to update the status is herein an operation on the start reading button521(for example, a touch or a click) That is, when the start reading button521is operated on the shipment screen500a, the work management unit232starts a session to update statuses based on results of tag reading for the target items displayed in the item list display area530

After the start reading button521is operated, when the tag reader100aused by the user20ahas read the tag ID from the item tag50of “Item D”, for example, the shipment screen500atransitions to the shipment screen500billustrated inFIG.11B. The shipment screen500bhas a similar configuration to the shipment screen500aexcept that the start reading button521is changed into a stop reading button522. As shown with a dashed box531in the figure, the reading status of “Item D” has been updated to “YES”. In addition, as shown with a dashed box513, the work status has been updated to “In Progress”. The status “In Progress” means that the work has been started but there remains a target item for which tag reading has not yet been completed.

Furthermore, when the tag reader100aused by the user20ahas read the tag IDs from the item tags50of “Item E” and “Item F”, the screen transitions to the shipment screen500cillustrated inFIG.11C. The shipment screen500chas a similar configuration to the shipment screen500bexcept that the stop reading button522has disappeared. As shown with dashed boxes532and533in the figure, the reading statuses of “Item E” and “Item F” have been updated to “YES”. In addition, as shown with a dashed box514, the work status has been updated to “Completed”.

In this manner, the user20proceeds reading of tag IDs from item tags50of respective target items while the user20keeps in the login state and the status update session is ongoing. Then, upon finishing reading of tag IDs for all of the target items has finished, the work management unit232becomes aware that the work as a whole has been completed, and updates the value of Status377of the corresponding work record in the work table370to “Completed”.

(3) Various Status Update Conditions

Update conditions for the work management unit232to update work-related statuses at least include that the user20has logged into the item management system1and has performed the user operation representing a start of the intended work at the user terminal160as described above.FIG.12is an explanatory diagram for explaining such a basic status update condition.

In the example ofFIG.12, there exist items30d,30eand30fin the place10a. It is assumed that the item30dis a target item of pre-shipment confirmation. There are two users20aand20bwho are active in the place10a. The user20auses the user terminal160ato access the management server200, succeeds in login, and operates the start reading button521of the shipment screen500a. A status update session for the pre-shipment confirmation in which the item30dis a target item is thus started. As the item30dis within the reading range Raof the tag reader100acarried by the user20a, the tag reader100areads the tag ID from the item tag50dof the item30d(the arrow A1in the figure). The work management unit232can update the value of Status383of the record corresponding to the item30din the work detail table380to “Completed” based on this result of tag reading.

However, the item30dis also within the reading range Rbof the tag reader100bcarried by the user20b. Accordingly, there is possibility that the tag reader100breads the tag ID from the item tag50dof the item30dwhile the status update session is ongoing (the arrow A2in the figure). Depending on system requirements, the status may be allowed to be updated based on results of tag reading by such a tag reader used by a user other than the login user, or by a tag reader that is not associated with a specific user. If this is allowed, in a situation where multiple users are jointly involved in a work, it will be possible for all of the users using respective tag readers to efficiently proceed tag reading by just one user logging into the system and starting a status update session. In addition, by preparing a tag reader that is not associated with a specific user in a work site, it will also be possible for an arbitrary user who has logged into the system and started the status update session to carry out the work using that tag reader.

Conversely, the status may be prevented from being updated based on a result of tag reading by a tag reader that is not the login user's tag reader100in use by introducing an additional status update condition in addition to the above-described basic status update condition. In other words, the work management unit232may update a work-related status of a target item only when it is determined that a tag reader100used by the login user has read a tag ID from an item tag50of the target item.

For example, the work management unit232may determine that a login user is using a tag reader100in a case where reading result data indicating that the tag reader100has read a tag ID of a user tag60of the login user is received.FIG.13is an explanatory diagram for explaining such an additional status update condition.

In the example ofFIG.13, there exist a plurality of items30including the item30din the place10a. It is assumed that the item30dis a target item of pre-shipment confirmation. There is a user20awho is active in the place10a. The user20auses the user terminal160ato access the management server200, succeeds in login, and performs a predetermined user operation to start a status update session for pre-shipment confirmation. The tag reader100acarried by the user20areads the tag ID from the user tag60a(the arrow A3in the figure), and further reads the tag ID from the item tag50dof the item30d(the arrow A4in the figure). Based on these results of tag reading, the work management unit232determines that the tag reader100aused by the user20awho is the login user has read the tag ID from the item tag50dof the item30dwhich is a target item. Then, the work management unit232updates the value of Status383of the record corresponding to the item30din the work detail table380to “Completed”. Note that the work management unit232may update the status only in a case where a difference in reading time of the tag IDs read from the user tag60and the item tag50is smaller than a predetermined time threshold. Moreover, the work management unit232may update the status only in a case where a difference in reading position of the tag IDs read from the user tag60and the item tag50is smaller than a predetermined distance threshold.

In this manner, statuses of target items may be updated based only on results of tag reading in which a login user is involved so as to prevent an inconvenient situation where a tag reader that should be irrelevant to a work would cause a status update that is not intended by a user. This makes status updates even more reliable.

The work management unit232may determine which user20is using which tag reader100based on history of tag reading over multiple times instead of a single result of tag reading from a user tag60. For example, assume that the tag reader100ahas detected the user tag60amany times within a certain period in the past while the tag reader100bhas detected the user tag60aonly few times. In this case, the work management unit232determines that the user20ais using the tag reader100abased on the history of tag reading. The value of User333of the reader table330ofFIG.6Amay be set based on such determination.

In an alteration example, an association between a tag reader100in the reader table330and a user20who uses the tag reader100may be given in advance without relying on reading of tag IDs from user tags60. For example, in a case where the user20aalways uses the tag reader100a, in order to associate the user20awith the tag reader100a, the user ID “U001” that identifies the user20ais registered in the field of User333of the corresponding record in the reader table330in advance. The work management unit232may determine that the user20ais using the tag reader100abased on this user ID in User333.

In another alteration example, the work management unit232may determine that a user20is using a tag reader100based on that the user terminal160used by the user20for the login has a communication connection with the tag reader100. For example, the user terminal160aestablishes a local communication connection with the tag reader100avia the connection unit164. When the user20ahas logged into the item management system1using the user terminal160a, the control unit161of the user terminal160atransmits the reader ID of the tag reader100aobtained through the communication connection with the tag reader100ato the management server200. The work management unit232can determine that the user20awho is the login user is using the tag reader100aby receiving this reader ID.

An additional status update condition may include that the tag reader100has read a tag ID from a position tag40of the place10in which the work is scheduled to be done.FIG.14is an explanatory diagram for explaining such an additional status update condition.

In the example ofFIG.14, again, there exist a plurality of items30including the item30din the place10a. It is assumed that the item30dis a target item of pre-shipment confirmation. In addition, it is assumed that the place10ais a workplace that is registered in advance in the work table370for the pre-shipment confirmation that the user20ais going to carry out. The user20auses the user terminal160ato access the management server200, succeeds in login, and performs a predetermined user operation to start a status update session for pre-shipment confirmation. The tag reader100acarried by the user20areads the tag ID associated with the place ID “PL01” of the place10afrom the position tag40ainstalled in the place10a(the arrow A5in the figure). Further, after the user20amoves, the tag reader100areads the tag ID from the item tag50dof the item30d(the arrow A6in the figure). The work management unit232determines that the status update conditions are satisfied based on these results of tag reading, and updates the value of Status383of the record corresponding to the item30din the work detail table380to “Completed”. According to such a status update condition, even if a status update session has been accidentally started in a place where the work is not scheduled to be done, the statuses of respective target items regarding the work can be prevented from being updated as a result. Hence, reliability of status updates can be much more enhanced.

An additional status update condition may include that a second user operation is detected at the tag reader100. As an example, the second user operation is assumed to be pressing a button of the operation unit115of the tag reader100. In this example, the work management unit232may update a work-related status of a target item only when the tag ID of the item tag50of the target item has been read in a state where the user20is pressing the button on the tag reader100. Alternatively, the work management unit232may update the work-related status of the target item only when the tag ID has been read during a period from the button on the tag reader100being pressed by the user20to a time when a certain time length elapses or when the button is pressed again. The control unit111of the tag reader100may include a flag (or an indication in an arbitrary format) indicating that the second user operation has been detected in reading result data and transmits it to the management server200, for example. In this manner, the work management unit232can promptly obtain the reading result data to which the flag is added from the reading result table350to efficiently determine whether to update a status for each target item.

Though numerous examples of status update conditions have been described in this section, the described conditions may be combined in any way with each other. For example, in addition to the basic status update condition, two or more of reading of a user tag60of a login user, reading of a position tag40, and detection of the second user operation may be adopted as the status update conditions.

5. FLOW OF PROCESSING

FIG.15is a flowchart illustrating an example of a flow of status update processing that may be performed by the management server200in the present embodiment. This status update processing may be started when the user20calls the application screen for pre-shipment confirmation or acceptance inspection at the user terminal160, for example. Note that, before starting the status update processing, it is assumed that some works and their lists of target items have already been registered in the work table370and the work detail table380. In the following descriptions, a process step is abbreviated as S (step).

First, in S111, the work management unit232accepts a login by a user20to the item management system1. The work management unit232may perform user authentication (login authentication) based on authentication information input by the user20on the screen of the user terminal160, for example. Herein, it is assumed that the authentication is successful and the user20enters a login state in the item management system1.

Next, in S113, the work management unit232causes the user terminal160of the user20who is the login user to display the application screen regarding a work. For example, if the work indented by the user20is pre-shipment confirmation, the shipment screen500aillustrated inFIG.11Amay be displayed by the display unit166of the user terminal160.

Next, in S115, the work management unit232accepts designation of a work from the user20on the displayed screen. For example, the user20designates one of uncompleted (or ongoing but suspended) works from among works registered in advance.

Next, in S117, the work management unit232obtains data regarding the work designated by the user20from the work table370, and a list of one or more target items from the work detail table380.

Next, in S119, the work management unit232waits for detection of the first user operation representing a start of the work of tag reading for status update. When a notification that the first user operation has been detected is received from the user terminal160, the processing proceeds to S121. At this point, the work management unit232may update the value of Status377of the work table370for the work designated in S115to “In Progress”.

In S121, the work management unit232determines whether the status update conditions other than reading of tag IDs from item tags50of target items are satisfied. The status update conditions herein includes one or more of the followings, for example:1) reading of the tag ID from the user tag60of the login user;2) detection of the second user operation at the tag reader100; and3) reading of the tag ID from the position tag40installed in the work place.
When it is determined that the required conditions are satisfied, the processing proceeds to S123. In a case where it is determined that any of the conditions is not satisfied, the work management unit232may cause the user terminal160to display a message for prompting to perform a corresponding action (for example, “read the user tag”, “press the button of the tag reader”, and so on).

In S123, the communication unit210receives reading result data from the tag reader100. In a practical example, the tag reader100from which the reading result data is received herein is the tag reader100that is determined to be used by the login user. In another practical example, the tag reader100from which the reading result data is received herein is an arbitrary tag reader100. The tag processing unit231adds reading result records corresponding to the received reading result data to the reading result table350.

The subsequent processing branches in S125depending on whether there are any tag IDs indicated by the reading result data which are tag IDs of item tags50of the target items included in the list obtained in S117. In a case where there are any tag IDs of item tags50of the target items, the processing proceeds to S127. Otherwise, the processing proceeds to S131.

In S127, the work management unit232updates the value of Status383of the work detail table380for the target item to “Completed” as it is determined that the tag ID have been read from the item tag50of the target item in a state where the status update conditions are satisfied.

Next, in S129, the work management unit232determines whether tag reading has been completed for all of the target items of the work in progress or not. In a case where tag reading has been completed for all of the target items, the processing proceeds to S133. Meanwhile, in a case where there remains a target item for which tag reading has not been completed, the processing proceeds to S131.

In S131the work management unit232determines whether to continue the status update processing or not. For example, in a case where a user operation for instructing to stop the work has been detected at the user terminal160(for example, operation of the button522of the shipment screen500binFIG.11B), the work management unit232determines to terminate the status update processing. In a case where the work management unit232determines to continue the status update processing, it goes back to waiting for reading result data in S123.

In a case where tag reading has been completed for all of the target items, the work management unit232updates the value of Status377of the work table370for the work designated in S115to “Completed”. Then, the status update processing of illustrated inFIG.15ends.

Various embodiments, practical examples and alteration examples of the technology according to the present disclosure have been described in detail with reference toFIGS.1to15. According to the above-described embodiments, a list of one or more items that are subject to a work by a user and a status of each item regarding the work are managed in a database in an item management system. A wireless device that stores identification information is attached to each item. A reading apparatus attempts to read identification information from wireless devices. Then, the status of a first item regarding the work is updated when it is determined that first identification information has been read from a first wireless device attached to the first item included in the list in a state where a user has logged into the system and a user operation representing a start of the work has been detected. With this configuration, it is possible to easily discern a reading result obtained at a timing intended by a user who is in charge of the work from among a large number of tag reading results accumulated over time in the system and to appropriately update the status of each item regarding the work. This enhances reliability of updating item management statuses based on results of tag reading. In a case where the user operation representing a start of the work is detected on an application screen provided to a user terminal, the user does not need to individually turn on and off the reading apparatus each time he or she conducts the work. Therefore, cumbersome operations are reduced and a risk of mistake that a tag reader is kept in off-state at a timing when it should be active can be eliminated as well.

According to the above-described embodiments, update conditions to update statuses regarding the work include that the reading apparatus used by the user who has logged into the system has read the first identification information from the first wireless device. In this case, it is possible to prevent an inconvenient situation where a reading apparatus that should be irrelevant to the work would cause a status update that is not intended by the user. This can make status updates even more reliable. According to a practical embodiment, users carry respective second wireless devices, and which reading apparatus the login user is using may be determined based on a result of reading the second identification information from the second wireless device carried by the login user. With this configuration, as associations between users and reading apparatuses are dynamically determined based on results of reading the second identification information, the reading apparatuses can be flexibly treated by a plurality of users (for example, each user is not forced to use a specific reading apparatus). According to an alteration example, when a reading apparatus is associated with the login user in advance in the database, it may be determined that the login user is using the reading apparatus. In this case, each user does not need to carry the second wireless device. According to another alteration example, it may be determined that the login user is using the reading apparatus based on that a terminal apparatus the login user is using has a communication connection with the reading apparatus. In this case as well, each user does not need to carry the second wireless device and, in addition, each user can also use a different reading apparatus for each work.

According to the above-described embodiments, the update conditions may include that the reading apparatus has read the first identification information from the first wireless device in a state where a further user operation has been detected at the reading apparatus. In this case, the reading apparatus can give an indication such as a flag to a reading result that should trigger a status update from among reading results that are accumulated over time, which makes updates to work-related statuses even more efficient.

According to the above-described embodiments, the update conditions may include that third identification information has been read from a third wireless device installed in a place where the work is performed. In this case, even if a user operation representing a start of the work has been accidentally performed in a place where the work is not scheduled to be done, the statuses can be prevented from being undesirably updated as a result.

According to the above-described embodiments, each wireless device is an RFID tag, and the reading apparatus reads information sent back from the RFID tag utilizing energy of electromagnetic waves emitted to a reading range. In this case, a wireless device attached to each item does not need a battery and a complicated transceiver mounted thereon, and the mechanism according to the above-described embodiments can be introduced with low cost even in a situation where there are a large number of items under management of the item management system.

7. OTHER EMBODIMENTS

According to the present invention, reliability of updating item management statuses based on results of tag reading will be enhanced.