JP2013254325A - Defective tag detection system and defective tag detection method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a defective tag detection system and a defective tag detection method by which a defective tag can be easily detected.SOLUTION: An automatic settlement system 1 is a defective tag detection system for detecting a defective tag associated with a commodity (dish). The automatic settlement system 1 includes a tag R/W unit 16 capable of reading information of a plurality of tags in settlement of a commodity, and a server 2 for managing respective usage histories of the plurality of tags read by the tag R/W unit 16.

Description

  The present invention relates to a defective tag detection system and a defective tag detection method for detecting a defective tag (defective tag).

  In Patent Document 1 below, an auto cash register terminal is proposed in which a tray on which tableware with an ID tag attached or embedded is placed. The automatic cash register terminal is provided with an ID tag reading device, and the ID tag reading device reads the ID code from the ID tag of the tableware on the tray. The ID code is associated with the name and price of the dish arranged on the tableware. In the auto register terminal, settlement processing is performed for the dish on the tray based on the ID code read by the ID tag reading device. It can be performed.

JP 2001-256449 A

  In the auto cash register terminal of Patent Document 1, it is assumed that a tray on which a plurality of dishes are placed is placed on the auto cash register terminal, and the ID tag reader reads ID codes from a plurality of ID tags at a time. If any of the plurality of ID tags is a defective tag that has failed, the ID tag reader cannot detect which ID tag is the defective tag, so the dish of the dish with the defective ID tag is attached. There is a concern that the settlement process for the restaurant will not be carried out and the sales at the cafeteria will decrease accordingly.

However, in order to find a defective tag, it is necessary to set tableware one by one in the auto cash register terminal and check each ID tag whether the ID code of the ID tag is correctly read by the ID tag reader. Inefficient and time consuming.
The present invention has been made under such a background, and an object thereof is to provide a defective tag detection system and a defective tag detection method capable of easily finding a defective tag.

The invention according to claim 1 is a defective tag detection system for detecting a defective product of a tag associated with a product, and when reading the product, reading means capable of reading information of a plurality of tags, And a management unit for managing each usage history of the plurality of tags read by the reading unit.
The invention described in claim 2 includes receiving means for receiving input of a predetermined condition for extracting a defective tag, and extracting means for extracting a defective tag based on the usage history and the predetermined condition. The defective tag detection system according to claim 1.

According to a third aspect of the present invention, the predetermined condition is a condition for detecting a tag whose usage record is relatively low within a predetermined period from the start of introduction, and the number of times the tag is used within the predetermined period. The defective tag detection system according to claim 2, comprising at least one of a tag last use date and a continuous tag non-use day within a predetermined period.
According to a fourth aspect of the present invention, the usage history includes the presence / absence of use of each tag on each day of a predetermined period, and is based on the presence / absence of use before a predetermined evaluation date within a predetermined period and the use / non-use of other tags 2. A calculation means for calculating a failure possibility of each tag on the evaluation date, and an extraction means for extracting a defective tag based on the failure possibility calculated by the calculation means. It is a defective tag detection system of description.

A fifth aspect of the present invention is the defective tag detection system according to any one of the second to fourth aspects, further comprising notification means for notifying the defective tag extracted by the extraction means.
The invention according to claim 6 is a defective tag detection method for detecting a defective product of a tag associated with a product, the step of reading information of a plurality of tags when the product is settled, and the plurality of read A method for detecting a defective tag, comprising: managing each usage history of a tag; and extracting a defective tag based on a predetermined condition for extracting a defective tag and the usage history. is there.

  The invention according to claim 7 is a defective tag detection method for detecting a defective product of a tag associated with a product, the step of reading information of a plurality of tags when the product is settled, and the plurality of read Based on the step of managing each tag's usage history, the presence / absence of each tag and the use / non-use of other tags before a predetermined evaluation date within a predetermined period, the possibility of failure of each tag on that evaluation date is calculated And a step of extracting a defective tag based on the calculated possibility of failure.

  According to the first aspect of the present invention, in the defective tag detection system, the managing means manages the usage history of each tag read by the reading means when the product is settled. The usage frequency is lower than other tags) based on the usage history and can be grasped early. Then, if it is tested whether or not only the narrowed-down tags (which are suspected of being defective tags) can be read by the reading means, it is not necessary to test all the tags, and the time required for detecting the defective tags can be shortened. As a result, a defective tag can be easily found.

According to the second and sixth aspects of the invention, a tag suspected of being a defective tag can be extracted with high accuracy based on the use history and predetermined conditions (can be narrowed down), so that the defective tag can be found more easily. .
Since the predetermined condition mentioned in the invention of claim 3 is a condition that can detect a tag having a relatively low usage record within a predetermined period after the introduction is started, if such a predetermined condition is used, Defective tags can be extracted with high accuracy.

According to the inventions of claims 4 and 7, a defective tag is determined based on the possibility of failure of each tag calculated based on statistical data such as the presence / absence of use before a predetermined evaluation date within a predetermined period and the use / non-use of other tags. Extraction can be performed with higher accuracy.
According to the fifth aspect of the present invention, it is convenient because the defective tag can be grasped by the notification content of the notification means.

FIG. 1 is a block diagram showing the overall configuration of an automatic settlement system 1 as a defective tag detection system according to the present invention. FIG. 2 is a perspective view of the tableware 17 to which the tag 18 is attached as viewed from the bottom side. FIG. 3 is a diagram illustrating a state in which the user makes a payment in the automatic payment system 1. FIG. 4 is a flowchart showing the flow of settlement before and after the user has a meal. FIG. 5 is a diagram showing data stored in the server 2 of the automatic settlement system 1. FIG. 6 is a flowchart showing the flow of the stocktaking work of the tableware 17. FIG. 7 is a diagram showing data stored in the server 2. FIG. 8 is a diagram showing data stored in the server 2. FIGS. 9A and 9B are diagrams showing data stored in the server 2.

Embodiments of the present invention will be specifically described below with reference to the drawings. In the following, a terminal that calculates a payment amount and performs automatic payment with electronic money or the like is referred to as “auto register”.
FIG. 1 is a block diagram showing the overall configuration of an automatic settlement system 1 as a defective tag detection system according to the present invention.

With reference to FIG. 1, this automatic payment system 1 is applied to a cafeteria in a company or the like, for example. Since the automatic payment system 1 performs payment automatically, a staff member engaged in payment in the dining room is not required.
The automatic settlement system 1 includes a server 2 as a management means, a cafeteria client 3, an auto cash register 4, and a card processing terminal 5. The server 2, the cafeteria client 3, the auto cash register 4, and the card processing terminal 5 are communicably connected via a LAN 6 formed of a wired or wireless communication line. The LAN 6 may be connected to the external network 8 via the router 7.

  The server 2 is a computer that manages the settlement history of dishes in the cafeteria, and is installed in a dedicated server room, for example. As a specific configuration, the server 2 is provided with a control unit 9 (accepting means, extracting means, calculating means, notifying means) constituted by a microcomputer or the like. The control unit 9 includes a CPU, a memory (ROM, RAM), and the like. The control unit 9 is for controlling the operation of the server 2.

  In addition, the server 2 is provided with a storage unit 10 that stores the above-described settlement history and information (menu, price, etc.) of each dish provided in the cafeteria. The server 2 is provided with an operation unit 11 composed of a keyboard or the like, and an attendant can give a desired instruction to the server 2 by operating the operation unit 11. Further, the server 2 is provided with a display unit 12 which is a liquid crystal display, for example, and information stored in the storage unit 10 is displayed on the display unit 12.

The cafeteria client 3 is a computer used to set (change) the information (menu, price, etc.) of each dish described above, and is installed in a staff office in the cafeteria, for example. The information is extracted from the server 2 and set by the cafeteria client 3.
The server 2 and the cafeteria client 3 may exist separately as shown in FIG. 1 in a state where they can communicate with each other, or may exist as an integrated computer.

The auto cash register 4 is installed in a settlement corner in the cafeteria. In FIG. 1, two auto registers 4 are shown, but the number of auto registers 4 can be determined arbitrarily. In the auto register 4, automatic payment by electronic money is possible.
Here, the user of the cafeteria carries the payment card 13 with an electronic money function. The card 13 according to this embodiment is a prepaid card corresponding to prepaid (prepaid) electronic money, and stores the amount of electronic money as a prepaid value. Note that the prepaid value of the card 13 can be additionally accumulated (charged) in a dedicated terminal (not shown).

The auto register 4 mainly includes a display unit 14, a tray mounting table 15, a tag R / W (Read / Write) unit 16 as a reading unit, and a control unit 20.
The display unit 14 is, for example, a liquid crystal display. The tray mounting table 15 is a table whose top surface is flat in the horizontal direction. The top surface of the tray mounting table 15 may be provided with a recess into which the tray 19 of the cafeteria can be fitted. In this case, the position of the tray 19 can be prevented from shifting during settlement. The tag R / W unit 16 is, for example, an IC tag reader and is built in the tray mounting table 15. The control unit 20 is composed of a microcomputer or the like, and is built in the auto register 4 and controls the operation of the auto register 4.

  The card processing terminal 5 is provided so as to have a one-to-one relationship with each auto register 4. The card processing terminal 5 can directly communicate with the corresponding auto register 4. The card processing terminal 5 stores an application for performing automatic payment using electronic money. The card processing terminal 5 can read and rewrite the amount of electronic money stored in the card 13 described above after starting the application according to an instruction from the control unit 20 of the corresponding auto register 4. The card processing terminal 5 may be regarded as a part of the corresponding auto register 4.

In all tableware 17 handled in the dining room of this embodiment, a tag 18 is attached to the thread end (bottom). In FIG. 2, the tableware 17 to which the tag 18 is attached is viewed from the bottom side. The tag 18 is an IC tag in which an IC chip, a coil and an antenna (not shown) are built.
As shown in FIG. 1, the tableware 17 has a plurality of types such as a rice bowl 17A, a soup bowl 17B, a small plate 17C for serving side dishes, etc., but each type of the tableware 17 has an identification number. Has been granted. For example, the identification number of rice bowl 17A is 001, the identification number of soup bowl 17B is 002, the identification number of small plate 17C is 003, and so on. The identification number is basically a number determined for each type of tableware 17. A menu and price of a dish are assigned to each identification number, and the menu and price for each identification number are stored in the storage unit 10 of the server 2. The storage unit 10 of the server 2 stores the number of stocks of all tableware 17 present in the cafeteria for each type.

  In the tableware 17 having the same identification number, a serial number is assigned to each tableware 17. Is assigned. Serial No. Is for identifying the individual tableware 17 in each type (identification number). The serial number is assigned to an IC chip (not shown) constituting the tag 18 attached to each tableware 17. Is recorded. The storage unit 10 of the server 2 has a serial number. And an identification number are stored in association with each other (see FIG. 5 to be described later). If the serial number is known, The identification number, cooking menu and price of the tableware 17 can be grasped. That is, serial No. The tag 18 in which is recorded is associated with a product (here, a dish) to be served on the tableware 17 to which the tag 18 is attached.

FIG. 3 is a diagram illustrating a state in which the user makes a payment in the automatic payment system 1. FIG. 4 is a flowchart showing the flow of settlement before and after the user has a meal.
A series of payments in the automatic payment system 1 will be briefly described with reference to FIGS. 1 to 4. First, the user takes the tray 19 (see FIG. 1) after entering the cafeteria, and likes it. The dishes 17 on which the dishes (products) are arranged are selected and placed on the tray 19 (step S1 in FIG. 4). Then, the user sets the tableware to settle for the dish he / she has chosen before he / she sits for a meal (before meal) or after he / she has eaten the dishes 17 after he / she has eaten (after the meal). Go to the payment corner with the tray 19 with 17 (see FIG. 3).

  Then, the user who arrives at the payment corner places the tray 19 on the tray mounting table 15 of the vacant auto register 4 (including the corresponding card processing terminal 5) as shown in FIG. Step S2 in FIG. Then, in the auto register 4, the information stored in the tag 18 of each tableware 17 placed on the tray 19 (in other words, the serial number of each tableware 17) is non-contacted by the tag R / W unit 16. Read. Here, when a plurality of dishes 17 are placed on the tray 19, the tag R / W unit 16 can read the information of the tags 18 (a plurality of tags 18) of these dishes 17 at a time.

  In response to the reading of the tag 18 by the tag R / W unit 16, the control unit 20 of the auto register 4 reads all the serial numbers read. The information corresponding to the menu (the menu and price of all the dishes selected by the user and placed on the tray 19) and the identification number described above are called from the server 2 (the food information stored in advance on the auto register 4 side is called). May be displayed collectively on the display unit 14.

Before and after the dish information is collectively displayed on the display unit 14, the card processing terminal 5 activates the application described above, whereby the payment processing preparation is completed. The prepaid value (the amount of electronic money) can be read without contact.
In this state, when the user holds his / her card 13 over the card processing terminal 5, the prepaid value stored in the card 13 is read and rewritten by the card processing terminal 5. As a result, the amount of electronic money stored in the card 13 is subtracted by the total amount of the aforementioned dishes (all dishes selected by the user and placed on the tray 19).

  When the rewriting of the prepaid value of the card 13 is completed, the settlement process using electronic money is completed for all dishes of the tableware 17 placed on the tray 19 of the tray mounting table 15 (step S2 in FIG. 4). After that, if the user settles before meals, he takes a seat and eats, and if he settles after meals, he takes the tray 19 on which the tableware 17 is placed to the tableware return corner. However, compared to pre-meal payments, after-meal payments can be settled relatively in line at the payment corner, or the tray 19 is lighter (easier to hold) because there is no food in the tableware 17, and dishes from the tableware 17 This is advantageous in that there is no risk of spilling.

  After the settlement (it may be performed at the same time as the completion of settlement), the control unit 20 of the auto register 4 that has finished the settlement process notifies the server 2 of information related to the current settlement process as the settlement information (step S3 in FIG. 4). The settlement information includes the identification number and serial number of the settled dish (tableware 17 on which the dish is arranged). And the date and time (use date and time) when the settlement process is completed. The control unit 20 notifies the server 2 of the payment information each time one payment process is completed.

The control unit 9 (see FIG. 1) of the server 2 that has received the notification of the settlement information, in the storage unit 10 (see FIG. 1) based on the settlement information, the corresponding tableware 17 (the tableware 17 for the settled dish). The use date and time is recorded every time (step S4 in FIG. 4).
FIG. 5 is a diagram showing data stored in the server 2 of the automatic settlement system 1.
Specifically, a table 50 as shown in FIG. 5 is stored in the storage unit 10, and data such as the use date and time of each tableware 17 is recorded in this table 50. In the table 50 of FIG. 5, for each tableware 17, an identification number (“003” in FIG. 5), serial No. ("00001" to "00005" in FIG. 5), the previous inventory date, the last usage date, the usage date, the usage count, and the status are recorded side by side. Note that, in each of the previous inventory date and time and the last use date and time, the date and time are recorded in separate columns, but they may be recorded together in the same column. In FIG. 5, only the data of the tableware 17 having the identification number 003 is shown, but actually, the data of the tableware 17 having other identification numbers is also stored in the table 50.

  The previous inventory date / time is the latest date / time among the date / time when the tableware 17 was recently invented, the date / time when the tableware 17 was introduced into the cafeteria, and the first use date / time of the tableware 17. The previous inventory date may be manually input by the operator of the server 2 by operating the operation unit 11 (see FIG. 1), and a terminal (not shown) at the time of inventorying, introducing, or using the tableware 17 for the first time. May be automatically input by causing the tag 18 of the tableware 17 to be read. When a new tableware 17 is introduced into the cafeteria, an identification number is assigned to the tableware 17 and the serial number of the tableware 17 is assigned. And the introduction date and time (which is the previous previous inventory date and time) are recorded in the table 50. When the tableware 17 introduced into the cafeteria is subsequently inventoried, the previous inventory date for the tableware 17 is updated by manual input or automatic input as described above. In addition, since not all tableware 17 is introduced at the same timing or receives inventory, the previous inventory date may vary for each tableware 17 (refer to the previous inventory date of serial No. 00004). ).

The last use date / time is the latest use date / time most recently received by the server 2 from the auto register 4 for each tableware 17. In other words, the tableware 17 was used most recently (the tag 18 of the tableware 17 has the tag R / Date and time).
The number of days of use is the total number of days that the server 2 has received the date of use (settlement information) in the period from the previous inventory date to the present time for each tableware 17. For example, serial no. In the case of tableware 17 having a value of 00001, since the number of days of use is 173 days, from the last inventory date (2011/4/1 15:13) to the current (last use date (2011/12/20 12:31) and later ), The tableware 17 has been used for 173 days (the tag 18 of the tableware 17 has been recognized by the tag R / W unit 16 for 173 days).

  The number of uses is the total number of times that the server 2 received the use date and time for each tableware 17 in the period from the previous inventory date to the present time. For example, serial no. In the case of the tableware 17 having a number of 00001, the number of use days is 208, so that the tableware 17 has been used 208 times during the period from the previous inventory date to the present (the tag 18 of the tableware 17 has the tag R / 208 times). It is recognized by the W unit 16).

Each time the control unit 9 of the server 2 receives the notification of the payment information, the serial number included in the payment information in the table 50 is displayed in the table 50. The last use date and time, the use days, and the use frequency of the tableware 17 are updated. The update here may be performed when a warning condition described later is input.
The status is a special note about each tableware 17 and will be described later with a specific example.

These data (previous inventory date / time, last use date / time, number of use days, number of use and status for tableware 17 of each serial No.) This is also the usage history of the tag 18 that stores. Therefore, the server 2 manages each usage history of the plurality of tags 18 read by the tag R / W unit 16 in the storage unit 10 (table 50).
Next, the inventory work performed in the cafeteria will be described.

FIG. 6 is a flowchart showing the flow of the stocktaking work of the tableware 17.
In the cafeteria, the tableware 17 is stocked regularly (for example, once a month) by a staff member of the cafeteria (which may be a specialized trader different from the staff member). In the inventory, the tableware 17 in the cafeteria is checked one by one by a staff member, and whether or not the actual stock number of the tableware 17 matches the stock number stored in the server 2 is determined for each type of the tableware 17 (described above). Confirmed for each identification number).

  At the time of inventory, whether or not the tableware 17 itself is damaged is confirmed by an attendant, and a malfunction (failure) of the tag 18 attached to the tableware 17 is also confirmed. For example, the IC chip may be damaged in the tag 18 or the coil may be disconnected due to heat or impact. The tag 18 (hereinafter, sometimes referred to as “defective tag”) that has failed and becomes a defective product in this way cannot be recognized by the tag R / W unit 16. The presence or absence of a failure of the tableware 17 can be easily found by visual observation, but it is difficult to visually confirm the presence or absence of a failure of the tag 18. The operation of checking whether or not there is a defect in the tag 18 is to check whether the tag 18 of each tableware 17 is recognized by the tag R / W unit 16 by holding the tableware 17 one by one on the tag R / W unit 16. If you need to check all the dishes 17 in the cafeteria, it will be very hard work.

In order to solve such a problem, the automatic settlement system 1 can automatically detect a defective product (defective tag) of the failed tag 18. Then, by following the following procedure using the automatic settlement system 1, the presence / absence of a defect in the tag 18 (presence / absence of a defective tag) can be easily found.
Referring to FIG. 6, the staff first extracts the failed tag 18 and sets a warning condition for warning the failure of the tag 18 (step S11). The warning condition is a predetermined condition for extracting the failed tag 18 (strictly speaking, the possibility of failure) from the tableware 17 registered in the table 50 (see FIG. 5). . The tableware 17 to which the failed tag 18 is attached has less usage record from the last use date and time than the other tableware 17 (the tag 18 is not broken). That is, the malfunctioning tag 18 is a tag 18 that has a relatively low usage record within a predetermined period (for example, a period from the start of introduction to the present) after the start of introduction. This is a condition for detecting such a tag 18.

  In the case of the tableware 17 to which the failed tag 18 is attached, for example, the last use date / time is significantly before (the previous) of the other tableware 17 (the tag 18 is not in failure). It tends to be significantly less than other tableware 17. The warning condition for the last use date and time is that the last use date and time (the time does not matter) is a predetermined number of days before the current inventory work, and the warning condition for the use days and the number of use times is a predetermined period. The number of use days and the number of uses are less than the respective threshold values. The clerk sets (selects) an optimal one of the warning conditions according to the operating status of the cafeteria, and inputs the warning condition (selected) to the server 2 by operating the operation unit 11 of the server 2 To do. Note that the number of warning conditions is not limited to one, and a plurality of warning conditions (including other warning conditions described later) may be appropriately combined and selected. That is, for example, a warning condition for both the last use date and time and the number of times of use may be selected, and the tag 18 of the tableware 17 caught first on either warning condition may be warned as a defective tag.

  In the server 2 in which the warning condition is input, the control unit 9 receives the input of the warning condition. And the control part 9 determines whether the said warning conditions are caught about the data of all the tableware 17 in the table 50, and when applicable tableware 17 is found, it performs warning determination (step S12). . Here, the control unit 9 has extracted the defective tag based on the data in the table 50 (the above-described usage history for each tag 18) and the warning condition.

Hereinafter, the description will be continued assuming that the tableware 17 caught in the warning condition has been found.
Referring to FIG. 5, for example, the last use date and time is a predetermined number of days (here, 7 days) before the current inventory work date (2011/12/20), that is, the last use date and time. If the warning condition is that 7 days or more have passed since the last use date is 2011/12/12, the identification number 003 is the serial number. 00003 tableware 17 gets caught in the warning condition. In this case, the control unit 9 determines the warning for the tableware 17 by setting the status of the tableware 17 (serial No. 00003) to “warning” in the table 50.

  As another warning condition, the number of use days is less than a predetermined number of days (the above-mentioned threshold, for example, 150 days), or the number of use is less than a predetermined number of times (the above-mentioned threshold, for example, 160). May be adopted. However, when the previous inventory date and time, which is a standard for determining the number of use days and the number of use, is the same for all the dishes 17, it is preferable to set the use days and the number of use as a warning condition. Because the previous inventory date and time is not necessarily the same for all the dishes 17 as described above, the table 17 having a previous inventory date and time after the other dishes 17 has a warning condition even though the tag 18 has not failed. (See Tableware 17 of Serial No. 00004).

  Therefore, in order to avoid that the tableware 17 in which the tag 18 has not failed is caught in the warning condition, as another warning condition, the number of usages per usage day (hereinafter referred to as “unit usage frequency”) The value obtained by dividing the number of times of use of the table 50 by the number of days of use) may be less than a certain number of times. Assuming that the general tableware 17 is used once a day, the certain number of times is set to 0.9 times / day, for example. The tableware 17 is assumed to be used once a day, but the actual set value (predetermined number of times) is a slightly lower value considering that there is a possibility that the dish is not popular. It may be. In the case of FIG. Only the tableware 17 of 00003 has a unit usage count of 0.88 (≈153 times ÷ 173 days) times / day, which is less than the predetermined number of times (0.9 times / day). . In this case, the control unit 9 determines the warning for the tableware 17 by setting the status of the tableware 17 (serial No. 00003) to “warning” in the table 50.

  After warning determination using a desired warning condition as described above, the control unit 9 uses the identification number and serial number of the tableware 17 as information on the tableware 17 (tag 18) caught in the warning condition. Is displayed on the display unit 12 (see FIG. 1) of the server 2 (step S13). In this case, information on other tableware 17 having the same identification number (type) as the tableware 17 caught in the warning condition may be displayed on the display unit 12, and in this case, the registered contents of the table 50 in FIG. 5. May be displayed on the display unit 12 as they are.

  As described above, the identification number of the tableware 17 matches the type of the tableware 17 (rice bowl, rice bowl, small plate, etc.). The type may be displayed on the display unit 12. Further, an image for each type of tableware 17 (for example, an image of rice bowl) is stored in the server 2, and the image of the tableware 17 is displayed together with the identification number and type of the tableware 17 or in place of them. 12 may be displayed. In this way, in step S13, the control unit 9 displays information on the tableware 17 (tag 18) to be warned on the display unit 12 (server screen), thereby notifying the staff of the defective tag extracted in step S12. . For the staff, it is convenient because the defective tag can be grasped by the content of the notification on the display unit 12 by the control unit 9.

  With the identification number 003 described above, the serial No. If the tableware 17 of 00003 (see FIG. 5) is caught by the warning condition, the attendant browses the information of the tableware 17 displayed on the display unit 12 and includes the tag 18 in the tableware 17 group having the identification number 003. Figure out that the broken tableware 17 is misplaced. In this embodiment, the serial number is displayed on the surface of the tag 18. Is not displayed, even if the tag 18 is viewed, the serial number recorded in the tag 18 is not displayed. Although it is not known, the type of the tableware 17 in which the tag 18 has failed can be narrowed down from all types by the identification number of the tableware 17 displayed on the display unit 12.

  The attendant holds all the tableware 17 of the type corresponding to the identification number caught in the warning condition (here, 003) one by one over the tag R / W unit 16 of the auto register 4, and the tag 18 of each tableware 17 is a tag. A reading test is performed to determine whether or not the recognition is normally performed by the R / W unit 16 (step S14). As a result, the serial no. Since only the tableware 17 (00003 here) is not recognized by the tag R / W unit 16, in response to this result, the clerk can recognize the serial number that has not been recognized by the tag R / W unit 16. The tag 18 (defective tag) of the tableware 17 of 00003 is excluded (step S14).

  The clerk removes the tag 18 of the tableware 17 caught in the warning condition, confirms that there is no other tag 18 caught in the warning condition, and then operates the operation unit 11 of the server 2. In response to this operation, the control unit 9 changes the status of the tableware 17 (here, the tableware 17 of serial No. 00003) in the table 50 from “warning” shown in FIG. 5 to “removed” shown in FIG. (Step S15).

  When all the inventory work is completed, the clerk operates the operation unit 11 of the server 2 to confirm the completion of the inventory work. In response to this operation, the control unit 9 clears the number of use days and the number of use to 0 (zero) for all tableware 17 except the tableware 17 whose status is “removed” in the table 50, and performs the previous inventory. The date / time is changed (updated) to the completion date / time of the current inventory work (for example, 17:00 on 2011/12/20). The table 50 in a state where these data changes have been completed is shown in FIG. Note that all data regarding the tableware 17 whose status is “removed” may be deleted from the table 50.

  As described above, in the automatic settlement system 1, the server 2 manages the usage history of each tag 18 read by the tag R / W unit 16 when a product (here, a dish) is settled. Therefore, the tag 18 suspected of being a defective tag is narrowed down based on the usage history (strictly, the types of tableware 17 with the tag 18 suspected of being a defective tag are narrowed down). ), Can be grasped early. Then, if it is tested whether or not only the narrowed down tags 18 (which are suspected of being defective tags) can be read by the tag R / W unit 16, it is not necessary to test all the tags 18. This time can be shortened. As a result, a defective tag can be easily found.

In particular, a tag 18 that is suspected of being a defective tag can be extracted with high accuracy based on the usage history and warning conditions (conditions for detecting a tag 18 that has a relatively low usage record within a predetermined period after the start of introduction). Since it can be narrowed down, a defective tag can be found more easily.
Since it is possible to easily find a defective tag, it is possible to eliminate a defective tag at an early stage, thereby reducing the sales loss of the cafeteria caused by an overlooked defective tag.

Further, in such an automatic settlement system 1, it is possible to find a tag 18 that is suspected of malfunctioning only by changing software (stored contents of the server 2 or operation of the control unit 9) without changing hardware. There is also an advantage in that
The present invention is not limited to the contents of the above embodiments, and various modifications can be made within the scope of the claims.

For example, the serial number stored in the tag 18 is placed on the surface of the tag 18 or the surface of the tableware 17. May be displayed so as to be visible. In this case, the serial no. The tableware 17 with the tag 18 can be found and removed immediately without checking the tag R / W unit 16 of the auto register 4.
Moreover, in the table 50, the continuous non-use days (Elapsed days from the last use to the next use) of each tableware 17 (tag 18) may be managed. When the tag 18 breaks down, the tag 18 is not used thereafter. Therefore, the number of days from the time of failure to the next inventory for this tag 18 is the number of consecutive non-use days. The warning condition described above may be that the number of consecutive non-use days within a predetermined period exceeds a predetermined threshold and is extremely large.

  In the embodiment described above, the warning condition is set using the last use date and time, the number of use days, the number of use (including the above-mentioned unit use number) and the continuous non-use days in each tableware 17, and the warning condition is caught. It is estimated that the tag 18 of the tableware 17 is broken. The failure tag 18 can be easily found with considerable accuracy simply by using the last use date and time, the number of use days, the use frequency, and the continuous non-use days, but in order to increase the detection accuracy of the failed tag 18. Includes a method using the following statistical data.

FIGS. 9A and 9B are diagrams showing data stored in the server 2.
In addition to the table 50 described above, a table 60 shown in FIG. 9A and a table 61 shown in FIG. 9A are stored in the storage unit 10 (see FIG. 1) of the server 2.
Referring to FIG. 9A, in the table 60, for each tableware 17, the identification number (type of tableware 17) and the serial number. And data No. And the daily use presence / absence i (T) of a predetermined evaluation period (here, 11 days from 1/16 to 1/26) are stored. Here, T is each day in the evaluation period (in the case of FIG. 9A, one of 1/16 to 1/26). In FIG. 9A, only the data of the tableware 17 having the identification number 003 is shown, but actually the data of the tableware 17 having other identification numbers is also stored in the table 60.

  Data No. Is provided for associating the data of each tableware 17 in the table 60 (the above-mentioned daily use presence / absence i (T)) between the tableware 17 having the same identification number, and in FIG. Data No. Are serial numbers such as 1 → 2 → 3 → 4 → 5. In FIG. 5, as an example, the data No. 1 Is the serial number. Corresponds to the data of “00001” (use / non-use i (T)). Is the serial number. Corresponds to data of 00005.

  The daily usage i (T) indicates the serial number. The tableware 17 is provided on each day of the evaluation period described above. For example, the presence / absence of use (i (T)) of the tableware 17 that has been used on any day of the evaluation period (the above-mentioned use date and time was transmitted to the server 2) is “0 (zero), meaning that there is use. (See, for example, 1/16 of i (T (= 1/16)) in the serial number of 00001). On the other hand, the presence / absence i (T) of the tableware 17 that has not been used on any day of the evaluation period (the above-mentioned usage date / time has not been transmitted to the server 2) on that day is “1”, meaning that there is no usage. (For example, see 1/17 i (T (= 1/17)) in the serial number of 00002). For example, on Saturdays and Sundays when the cafeteria is a holiday, the use / non-use i (T) of all tableware 17 becomes “1” (for example, i (T (1/2 (1) and 1/22 in all serial numbers) = 1/21, 1/22)))). On weekdays when the cafeteria is open, the use / non-use i (T) of all tableware 17 is “0” until the end of the business hours, and the use of that table at the time after the end of the business hours. The use / non-use i (T) of the tableware 17 that has never occurred is recorded in the table 60 as “0” → “1”. As described above, the server 2 uses the usage presence / absence i (T) of each tableware 17 (each tag 18) on each day of the predetermined period (evaluation period) in the table 60 of the storage unit 10 as the usage history of the tag 18. I manage.

The table 60 also records the average m (T) of the daily use / non-use i (T) of the evaluation period for all the dishes 17 having the same identification number (see the bottom column of the table 60). . For example, the average m (T (= 1/16)) at 1/16 is 0.2 (= (0 + 0 + 0 + 0 + 1) / 5).
When the clerk operates the operation unit 11 of the server 2 in order to carry out the inventory after the evaluation period described above (for example, the day after the evaluation period expires), the control unit 9 performs FIG. 9 based on the data in the table 60. The table 61 of (b) is created. In the table 61, for each tableware 17, the identification number (type of the tableware 17) and the serial number. And data No. And the daily evaluation value K (T) of the previous evaluation period is stored. In FIG. 9B, only the data for the tableware 17 with the identification number 003 is shown, but actually, the data for the tableware 17 with other identification numbers is also stored in the table 61.

  Data No. , Identification number and serial number. Is the data No. of the table 60 (see FIG. 9A). , Identification number and serial number. Is consistent with That is, in the table 61 as well as the table 60, the data No. 1 is the serial number. Corresponds to data (evaluation value K (T) in the table 61). 5 is a serial number. Corresponds to data of 00005.

The daily evaluation value K (T) is the serial number. Is calculated by the following formula (1) based on the presence / absence of use i (T) and average m (T) on each day of the evaluation period described above.
K (T) = a.K (T-1) + b.i (T). (1-m (T)) (1)
Here, the variables a and b are empirically obtained variables, the variable a is 0.9, and the variable b is 1. K (T-1) is K (T) of the previous day. I (T) is the same serial number of the same day in the table 60 (see FIG. 9A). The usage presence / absence of i (T). Further, m (T) is an average m (T) on the same day in the table 60.

  For example, for each tableware 17 on the first day of the evaluation period (here, 1/16), K (T−1) becomes 0 (zero) (the evaluation value K ( T) does not exist). Only the use / non-use i of 00005 (T (= 1/16)) is “1”, and the average m (T (= 1/16)) is 0.2 (see FIG. 9A). By substituting these values into the equation (1), the serial number is 1/16. Only the evaluation value K (T (= 1/16)) of 00005 is calculated as 0.80. The evaluation values K (T (= 1/16)) of (00001 to 00004) are all calculated as 0.00.

  Also, for example, serial No. In the tableware 17 of 00002, K (T-1 (= 1/17)) on the previous day (1/17) is 0.80, and usage (i (T (= 1/18))) on the day (1/18) Is 1, and the average m (T (= 1/18)) on the day is 0.2 (see FIG. 9A). By substituting these values into the equation (1), the serial number in 1/18 is obtained. The evaluation value K (T (= 1/18)) of 00002 is calculated as 1.52.

  In this way, the control unit 9 calculates the evaluation value K (T) for all the days of the evaluation period for each tableware 17. FIG. 9B shows a state where calculation of all evaluation values K (T) has been completed. The staff operates the operation unit 11 of the server 2 with respect to the evaluation value K (T (= 1/26)) of each tableware 17 on the last day of the evaluation period (also referred to as an evaluation date, here 1/26). Thus, a predetermined threshold value (here, 2.00) is set, and the warning condition is that the evaluation value K (T) on the last day is equal to or greater than the threshold value. In this case, the evaluation value K (T) on the last day is 2.12 and the identification number 003 is the serial number. 00003 tableware 17 is caught in the warning condition. In this case, the control unit 9 determines the warning for the tableware 17 by setting the status of the tableware 17 (serial No. 00003) to “warning” in the table 50 (see FIG. 5). Subsequent processing is the same as in the above-described embodiment (see step S13 and subsequent steps in FIG. 6).

  In this case, the control unit 9 determines each tag on the evaluation date based on the usage presence / absence i (T) before the predetermined evaluation date within the predetermined period (evaluation period) and the usage presence / absence i (T) of the other tag 18. Is calculated as an evaluation value K (T), and defective tags are extracted based on the evaluation value K (T). That is, the evaluation value K (T) of the tableware 17 takes into account not only the use / non-use of each day of the evaluation period of the tableware 17 but also the presence / absence of holidays and the use / non-use of other tableware 17 i (T). Failure possibility (of each tag 18). Thus, a defective tag is determined depending on the possibility of failure of each tag 18 calculated based on the statistical data such as the presence / absence of i (T) before the predetermined evaluation date within the predetermined period and the presence / absence of i (T) of other tags 18. Can be extracted with higher accuracy.

  Moreover, the automatic payment system 1 shown in FIG. 1 is applicable not only to the cafeteria mentioned above but also to payment at a store such as a convenience store or a supermarket. In the case of a store, a tag 18 is attached to each product displayed in the store. For example, a customer selects a plurality of products and puts them in a basket and goes to a cash register. When the customer sets a bag in the auto register 4 provided in the cash register, all the tags 18 of the products in the bag are read almost simultaneously by the tag R / W unit 16 and the product name is displayed on the display unit 14 of the auto register 4 (FIG. 1). The customer makes his / her own card 13 read by the card processing terminal 5 to make a settlement for the merchandise selected by the customer.

In the above-described embodiment, the tag 18 caught in the warning condition is excluded. If there is no problem with the tableware 17 to which the tag 18 is attached, the tag 18 is replaced from a defective product to a normal product. The tableware 17 may be reused.
In the above-described embodiment, the prepaid system (prepaid system) electronic money and the prepaid card 13 are used. However, the electronic money is a postpay system (postpay system) and the card 13 is a credit card. It may be configured to collect later (in the case of an employee cafeteria, it is deducted from employee salary).

  In FIG. 9, “0 (zero)” is recorded when the tableware 17 is used, but this “0” may not be displayed. In short, it is only necessary to know whether or not the tableware 17 has been used.

1 Automatic payment system 2 Server 9 Control unit 16 Tag R / W unit 18 Tag

Claims (7)

A defective tag detection system for detecting defective tags associated with a product,
Reading means capable of reading information from a plurality of tags when the product is settled;
Management means for managing each usage history of the plurality of tags read by the reading means;
A defective tag detection system comprising: Receiving means for receiving an input of a predetermined condition for extracting a defective tag;
Extraction means for extracting a defective tag based on the usage history and the predetermined condition;
The defective tag detection system according to claim 1, comprising:   The predetermined condition is a condition for detecting a tag having a relatively low usage record within a predetermined period after the introduction is started, and the number of times the tag is used within the predetermined period, the last use date of the tag, and 3. The defective tag detection system according to claim 2, comprising at least one of continuous non-use days of the tag within a predetermined period. The usage history includes usage of each tag on each day of a predetermined period,
A calculation means for calculating the possibility of failure of each tag on the evaluation date based on the presence / absence of use before a predetermined evaluation date within a predetermined period and the use / non-use of other tags;
Extraction means for extracting defective tags based on the possibility of failure calculated by the calculation means;
The defective tag detection system according to claim 1, comprising:   5. The defective tag detection system according to claim 2, further comprising a notification unit configured to notify the defective tag extracted by the extraction unit. A defective tag detection method for detecting defective tags associated with a product,
Reading the information of multiple tags when the product is settled;
A step of managing each usage history of the plurality of read tags;
Extracting a defective tag based on a predetermined condition for extracting a defective tag and the usage history;
A defective tag detection method comprising: A defective tag detection method for detecting defective tags associated with a product,
Reading the information of multiple tags when the product is settled;
A step of managing each usage history of the plurality of read tags;
Calculating the possibility of failure of each tag on the evaluation date based on the presence / absence of use of each tag and the use / non-use of other tags within a predetermined period of time,
Extracting defective tags based on the calculated failure possibility;
A defective tag detection method comprising:

Images