Operator management device and control program thereof

Abstract

To provide an operator management device for correctly managing operation time of an operator, and a control program of the same.SOLUTION: In a POS (Point Of Sales) system 1, a shop server 20 which is an operator management device detects an event generated according to operation of an operator from a POS terminal 10, and when the event is generated according to start command operation of a task relating to evaluation of the operator, the shop server 20 starts clocking operation. When the event is generated according to end command operation of the task, the shop server 20 ends the clocking operation. When the event is generated according to an interruption command operation of the task, the shop server 20 stops the clocking operation, and when the event is generated according to a restart command operation of the task, the shop server 20 restarts the clocking operation. The shop server 20 records a time clocked by the clocking operation as an evaluation time of the operator.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] An embodiment of the present invention relates to an operator management device that manages operators of POS (Point Of Sales) terminals and a control program therefor. [Background technology]

[0002] In stores where many employees work as POS terminal operators, the number of times a POS terminal is operated and the operation time are managed as evaluation items for the operators. The number of operations is, for example, the number of times a product is registered. The operation time is, for example, the time required to register the number of products registered. Generally, the more products an operator can register in a short time, the higher the evaluation.

[0003] However, there are times when an operator must leave the register while registering an item. For example, this may occur when the operator needs to go to a shelf to check the price of an item or to replace a defective item. In such cases, the operator puts the POS terminal into a pause state before leaving the register. When the operator returns to the register, he or she releases the pause state of the POS terminal.

[0004] In conventional operator management devices, even if there was a pause during product registration, the operation time of the operator was managed including the pause, and therefore the time when the operator left the register was included in the operation time, making it impossible to properly manage the operation time of the operator. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2015-103023 A Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the embodiments of the present invention is to provide an operator management device that can correctly manage the operation time of an operator. [Means for solving the problem]

[0007] In one embodiment, the operator management device includes a detection means, a start means, an end means, a stop means, a restart means, and a recording means. The detection means detects an event that has occurred in response to an operation by an operator from a POS terminal. The start means starts a timing operation when the event has occurred in response to an operation commanding the start of a task related to the operator's evaluation. The end means ends the timing operation when the event has occurred in response to an operation commanding the end of the task. The stop means stops the timing operation when the event has occurred in response to an operation commanding the interruption of the task. The restart means restarts the timing operation when the event has occurred in response to an operation commanding the restart of the task. The recording means records the time clocked by the timing operation as the operator's evaluation time. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic configuration diagram of a POS system 1 according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing a main circuit configuration of a store server. [Diagram 3] FIG. 4 is a schematic diagram showing a data structure of a timer memory. [Figure 4] FIG. 4 is a schematic diagram showing the data structure of a status memory. [Diagram 5] FIG. 4 is a schematic diagram showing a data structure of an evaluation table. [Figure 6] FIG. 4 is a schematic diagram showing a data structure of an aggregation table. [Figure 7] 4 is a flowchart showing the main steps of a main process executed by a processor. [Figure 8] 4 is a flowchart showing the main steps of a main process executed by a processor. [Figure 9] 4 is a flowchart showing the main steps of a main process executed by a processor. [Figure 10]4 is a flowchart showing the main steps of a main process executed by a processor. [Figure 11] 4 is a flowchart showing a main procedure of a timer interrupt process executed by a processor. [Figure 12] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 13] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 14] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 15] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 16] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 17] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. [Figure 18] 11 is a timing chart showing an example of patterns of waiting time, registration time, and closing time managed by the store server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of an operator management device will be described with reference to the drawings. In this embodiment, a store server of a POS system has a function as an operator management device.

[0010] 1 is a schematic diagram of a POS system 1 according to this embodiment. The POS system 1 includes a plurality of POS terminals 10, a store server 20, and a communication network 30. The communication network 30 connects each of the POS terminals 10 and the store server 20 so that data communication can be freely performed. The communication network 30 is, for example, a LAN (Local Area Network). The LAN may be a wired LAN or a wireless LAN.

[0011] The POS terminal 10 is a well-known electronic device having information processing functions related to product registration, payment, etc. Therefore, a detailed description of the POS terminal 10 will be omitted. In this embodiment, an employee called a cashier, an accountant, etc. can be an operator of the POS terminal 10.

[0012] The store server 20 is a computer having a service function for centrally managing a plurality of POS terminals 10. The service function includes a function for notifying the POS terminal 10 of product data such as the product name and price of each product, and a function for managing sales, inventory, etc. of the entire store based on the product data registered in each POS terminal 10. Since such functions are well known, a description thereof will be omitted here. In this embodiment, the store server 20 further has a function as an operator management device. Therefore, the configuration and operation related to the function as an operator management device will be described in detail below with reference to Figs. 2 to 18. First, the configuration will be described with reference to Figs. 2 to 6.

[0013] 2 is a block diagram showing the main circuit configuration of the store server 20. The store server 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, an input / output interface 25, and a communication interface 26. The processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, the input / output interface 25, and the communication interface 26 are each connected to a system transmission path 27. The system transmission path 27 includes an address bus, a data bus, a control signal line, and the like. In the store server 20, the processor 21, the main memory 22, and the auxiliary storage device 23 are connected by the system transmission path 27 to form a computer that performs information processing for controlling the store server 20.

[0014] The processor 21 corresponds to the central part of the computer. The processor 21 controls each part to realize various functions of the store server 20 according to an operating system or an application program. The processor 21 is, for example, a CPU (Central Processing Unit).

[0015] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or an application program in the nonvolatile memory area. The main memory 22 stores data required for the processor 21 to execute processes for controlling each part in the volatile memory area. The main memory 22 also uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0016] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage device 23, for example, well-known storage devices such as EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disc Drive), or SSD (Solid State Drive) are used alone or in combination. The auxiliary storage device 23 stores data used by the processor 21 when performing various processes and data generated by the processes in the processor 21. The auxiliary storage device 23 may also store application programs.

[0017] The application programs stored in the main memory 22 or the auxiliary storage device 23 include a control program, which will be described later. There is no particular limitation on the method for installing the control program in the main memory 22 or the auxiliary storage device 23. The control program can be recorded on a removable recording medium, or distributed by communication via a network, and installed in the main memory 22 or the auxiliary storage device 23. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0018] The clock 24 functions as a time information source for the store server 20. The processor 21 keeps track of the current date and time based on the time information kept by the clock 24.

[0019] The input / output interface 25 is a circuit for connecting peripheral devices to the store server 20. For example, peripheral devices such as a keyboard, a display, a touch panel, a pointing device, a printer, etc. are connected to the store server 20 via the input / output interface 25.

[0020] The communication interface 26 is a circuit for performing data communication with each POS terminal 10 connected via the communication network 30 .

[0021] In order for the store server 20 configured as described above to function as an operator management device, part of the volatile memory area of ​​the main memory 22 is used as an area for a timer memory 221 and an area for a status memory 222. The store server 20 also uses part of the memory area of ​​the auxiliary memory device 23 as an area for an evaluation table 231 and an area for an aggregation table 232.

[0022] 3 is a schematic diagram showing the data structure of the timer memory 221. As shown in the figure, the timer memory 221 stores timer counters TCa to TCz in association with a plurality of POSIDs, respectively. The POSID is a unique code set for each POS terminal 10 in order to identify each POS terminal 10. The timer counters TCa to TCz count up in synchronization with the oscillation frequency of a clock oscillation circuit (not shown). Then, every time the timer counters TCa to TCz count a value equivalent to, for example, one second, the store server 20 outputs a timer interrupt signal.

[0023] 4 is a schematic diagram showing the data structure of the status memory 222. As shown in the figure, the status memory 222 stores statuses Sa to Sz in association with a plurality of POSIDs, respectively. The statuses Sa to Sz indicate the state of the POS terminal 10 identified by the corresponding POSID. In this embodiment, the statuses Sa to Sz indicate three states: "0", "1", and "2". Specifically, the statuses Sa to Sz indicate a standby state with "0", a state in which a product is being registered with "1", and a state in which payment is being made with "2".

[0024] FIG. 5 is a schematic diagram showing the data structure of the evaluation table 231. As shown in the figure, the evaluation table 231 stores a plurality of evaluation items in association with an employee ID. The employee ID is a unique code set for each employee to identify each employee. The evaluation items are items necessary for evaluating employees involved in the operation of the POS terminal 10. The evaluation items include a waiting time WTA, a registration time RTA, a closing time STA, an operating time OTA, a registration count RNA, and a customer count CNA. The waiting time WTA is the time spent waiting for the start of product registration. The registration time RTA is the time spent registering products. The closing time STA is the time required for payment after product registration. The operating time OTA is the sum of the waiting time WTA, the registration time RTA, and the closing time STA. The registration count RNA is the number of times an operator has registered a product. The customer count CNA is the number of customers the operator has handled from product registration to payment.

[0025] 6 is a schematic diagram showing the data structure of the tally table 232. As shown in the figure, the tally table 232 stores an employee ID, a payment flag F, and a plurality of tally items in association with a POSID. The payment flag F is one-bit data for identifying whether or not a payment has started. In this embodiment, the payment flag before the start of a payment is set to "0", and the payment flag F after the start of a payment is set to "1". The tally items are items necessary for tallying up the evaluation items for the operator of the POS terminal 10. The tally items include waiting time WTB, registration time RTB, closing time STB, number of registrations RNB, and number of customers CNB.

[0026] 7 to 10 are flow charts showing the main steps of the main processing executed by the processor 21 according to the control program. FIG. 11 is a flow chart showing the main steps of the timer interrupt processing executed by the processor 21 according to the control program. Below, the main operations related to the function as an operator management device will be explained using each figure. Note that the operation explanation explained below is an example. As long as similar results are obtained, the procedures are not particularly limited.

[0027] 7, the processor 21 waits for a sign-on command as ACT1. The sign-on command is output from the POS terminal 10 where the sign-on operation has been performed. That is, when an operator who starts using the POS terminal 10 performs a sign-on operation by, for example, inputting an employee ID, the sign-on command is transmitted from the POS terminal 10 to the store server 20. The sign-on command is received by the communication interface 26 of the store server 20 via the communication network 30. The sign-on command includes the POSID of the POS terminal 10 and the employee ID of the operator who has signed on. In the following, the POS terminal 10 where the sign-on operation has been performed is referred to as a POS terminal 10x.

[0028] When the processor 21 receives a sign-on command, it determines YES in ACT1 and proceeds to ACT2. The processor 21 acquires a POSID from the sign-on command in ACT2. The processor 21 also acquires an employee ID from the sign-on command in ACT3. The processor 21 then sets the employee ID in association with the POSID in the tally table 232 in ACT4.

[0029] Processor 21 resets the timer counter associated with the POSID in timer memory 221 as ACT5. Hereinafter, this timer counter will be referred to as timer counter TCx. Processor 21 sets the payment flag F associated with the POSID in tally table 232 to "0" as ACT6. Processor 21 clears the tally item associated with the POSID in tally table 232 to "0" as ACT7. Processor 21 sets the status associated with the POSID in status memory 222 to "0" as ACT8. Hereinafter, this status will be referred to as status Sx.

[0030] After completing the above process, the processor 21 starts the timer counter TCx in ACT 9. This causes the timer counter TCx to start counting up. The processor 21 proceeds to ACT 11 in FIG.

[0031] The processor 21 checks whether or not a sign-off command has been received from the POS terminal 10x in ACT11. If the sign-off command has not been received, the processor 21 judges NO in ACT11 and proceeds to ACT12. The processor 21 checks whether or not a pause start command has been received from the POS terminal 10x in ACT12. If the pause start command has not been received, the processor 21 judges NO in ACT12 and proceeds to ACT13. The processor 21 checks whether or not a product registration command has been received from the POS terminal 10x in ACT13. If the product registration command has not been received, the processor 21 judges NO in ACT13 and returns to ACT11. Here, the processor 21 waits for reception of a sign-off command, a pause start command, or a product registration command from the POS terminal 10x in ACT11 to ACT13.

[0032] The sign-off command is output from the POS terminal 10 on which the sign-off operation has been performed. The operator performs the sign-off operation when ending use of the POS terminal 10x. When the sign-off operation is performed, the sign-off command is transmitted from the POS terminal 10x to the store server 20. The sign-off command is received by the communication interface 26 of the store server 20 via the communication network 30. The sign-off command includes the POS ID of the POS terminal 10x.

[0033] The pause start command is output from the POS terminal 10 on which the pause start operation has been performed. The operator performs the pause start operation when temporarily leaving the cash register. When the pause start operation is performed, the pause start command is transmitted from the POS terminal 10x to the store server 20. The pause start command is received by the communication interface 26 of the store server 20 via the communication network 30. The pause start command includes the POSID of the POS terminal 10x.

[0034] The product registration command is output from the POS terminal 10 where the product registration operation has been performed. When an operator registers a product to be purchased by a customer, the operator performs a product registration operation such as scanning the barcode of the product. When the product registration operation has been performed, the product registration command is transmitted from the POS terminal 10x to the store server 20. The product registration command is received by the communication interface 26 of the store server 20 via the communication network 30. The product registration command includes the POSID of the POS terminal 10x.

[0035] When a sign-off command is received in the command waiting state of ACT11 to ACT13, the processor 21 judges YES in ACT11 and proceeds to ACT14. The processor 21 stops the timer counter TCx based on the POSID included in the sign-off command in ACT14. The processor 21 also clears the employee ID stored in the tally table 232 in association with the POSID included in the sign-off command in ACT15. With this, the processor 21 ends the information processing for the POS terminal 10x where the sign-on operation has been performed.

[0036] When the processor 21 receives a pause start command in the command waiting state of ACT11 to ACT13, the processor 21 judges YES in ACT12 and proceeds to ACT16. In ACT16, the processor 21 waits for a pause end command from the POS terminal 10x.

[0037] The pause end command is output from the POS terminal 10 where the pause end operation was performed. The operator who temporarily left the cash register performs the pause end operation when he returns to the cash register. When the pause end operation is performed, the pause end command is transmitted from the POS terminal 10x to the store server 20. The pause end command is received by the communication interface 26 of the store server 20 via the communication network 30. The pause end command includes the POSID of the POS terminal 10x.

[0038] When the processor 21 receives the pause end command, the processor 21 judges YES in ACT16 and returns to ACT12. That is, the processor 21 enters a command standby state in ACT11 to ACT13.

[0039] When a product registration command is received in the command waiting state of ACT11 to ACT13, the processor 21 judges YES in ACT13 and proceeds to ACT17. The processor 21 increments the registration count stored in the tally table 232 in association with the POSID included in the product registration command by "1" in ACT17. Hereinafter, this registration count is referred to as the registration count RNBx.

[0040] The processor 21 acquires the employee ID and waiting time stored in association with the POSID from the tally table 232 as ACT18. Hereinafter, this waiting time will be referred to as waiting time WTBx. Also, the waiting time stored in the evaluation table 231 in association with the employee ID will be referred to as waiting time WTAx.

[0041] The processor 21 adds the waiting time WTBx to the waiting time WTAx as ACT 19. The waiting time WTBx will be made clear in the timer interrupt process (FIG. 11) described later.

[0042] The processor 21 sets the status Sx to “1” in ACT 20. After that, the processor 21 proceeds to ACT 21 in FIG.

[0043] In ACT21, the processor 21 checks whether or not a product registration command has been received from the POS terminal 10x. If the product registration command has not been received, the processor 21 determines NO in ACT21 and proceeds to ACT22. In ACT22, the processor 21 checks whether or not a pause start command has been received from the POS terminal 10x. If the pause start command has not been received, the processor 21 determines NO in ACT22 and proceeds to ACT23. In ACT23, the processor 21 checks whether or not a batch cancel command has been received from the POS terminal 10x. If the batch cancel command has not been received, the processor 21 determines NO in ACT23 and proceeds to ACT24. In ACT24, the processor 21 checks whether or not a registration end command has been received from the POS terminal 10x. If the registration end command has not been received, the processor 21 determines NO in ACT24 and returns to ACT21. Here, in ACT21 to ACT24, the processor 21 waits to receive a product registration command, a suspension start command, a collective cancellation command, or a registration end command from the POS terminal 10x.

[0044] The bulk cancel command is output from the POS terminal 10 where the bulk cancel operation has been performed. An operator performs the bulk cancel operation, for example, when a customer requests to cancel shopping. When the bulk cancel operation has been performed, the bulk cancel command is transmitted from the POS terminal 10x to the store server 20. The bulk cancel command is received by the communication interface 26 of the store server 20 via the communication network 30. The bulk cancel command includes the POSID of the POS terminal 10x.

[0045] The registration end command is output from the POS terminal 10 where the registration end operation has been performed. After completing the registration operation of the products purchased by the customer, the operator performs the registration end operation, such as inputting a subtotal key. When the registration end operation has been performed, the registration end command is transmitted from the POS terminal 10x to the store server 20. The registration end command is received by the communication interface 26 of the store server 20 via the communication network 30. The registration end command includes the POS ID of the POS terminal 10x.

[0046] When a product registration command is received in the command standby state of ACT21 to ACT24, the processor 21 judges YES in ACT21 and proceeds to ACT25. The processor 21 increments the registration count RNBx by "1" based on the POSID included in the product registration command in ACT25. After that, the processor 21 returns to ACT21. That is, the processor 21 enters the command standby state of ACT21 to ACT24.

[0047] When the processor 21 receives a pause start command in the command waiting state of ACT21 to ACT24, the processor 21 judges YES in ACT22 and proceeds to ACT26. The processor 21 stops the timer counter TCx based on the POSID included in the pause start command in ACT26. The processor 21 then waits for a pause end command from the POS terminal 10x in ACT27. When the processor 21 receives a pause end command, the processor 21 judges YES in ACT27 and proceeds to ACT28. The processor 21 restarts the timer counter TCx based on the POSID included in the pause end command in ACT28. The processor 21 then returns to ACT21. That is, the processor 21 enters a command waiting state of ACT21 to ACT24.

[0048] When the processor 21 receives a batch cancel command in the command waiting state of ACT21 to ACT24, the processor 21 judges YES in ACT23 and proceeds to ACT29. The processor 21 stops the timer counter TCx based on the POSID included in the batch cancel command in ACT29. The processor 21 then returns to ACT7 in Fig. 7. That is, the processor 21 clears the tally item associated with the POSID in the tally table 232 to "0". The processor 21 also sets the status Sx to "0". The processor 21 then starts the timer counter TCx. The processor 21 then enters a command waiting state of ACT11 to ACT13.

[0049] When a registration end command is received in the command waiting state of ACT21 to ACT24, the processor 21 judges YES in ACT24 and proceeds to ACT30. The processor 21 acquires the employee ID, registration time, and registration count RNBx stored in the tally table 232 in association with the POSID included in the registration end command in ACT30. Hereinafter, this registration time is referred to as the registration time RTBx. Also, the registration time stored in the evaluation table 231 in association with the employee ID is referred to as the registration time RTAx, and the registration count is referred to as the registration count RNAx.

[0050] The processor 21 adds the registration time RTBx to the registration time RTAx as ACT 31. The processor 21 also adds the registration count RNBx to the registration count RNAx as ACT 32. The registration time RTBx will be made clear in the timer interrupt process (FIG. 11) described later.

[0051] The processor 21 sets the status Sx to "2" in ACT33. Then, the processor 21 proceeds to ACT41 in Fig. 10. The processor 21 checks the payment flag F associated with the POSID and stored in the tally table 232 in ACT41. Here, if the payment flag F is already set to "1", the processor 21 determines YES in ACT41 and proceeds to ACT44.

[0052] On the other hand, if the payment flag F has not yet become "1", the processor 21 judges NO in ACT41 and proceeds to ACT42. The processor 21 checks whether a product registration command has been received from the POS terminal 10x in ACT42. If a product registration command has not been received, the processor 21 judges NO in ACT42 and proceeds to ACT43. The processor 21 checks whether a payment start command has been received from the POS terminal 10x in ACT43. If a payment start command has not been received, the processor 21 judges NO in ACT43 and proceeds to ACT44.

[0053] The processor 21 checks whether or not a pause start command has been received from the POS terminal 10x in ACT44. If a pause start command has not been received, the processor 21 judges NO in ACT44 and proceeds to ACT45. The processor 21 checks whether or not a batch cancel command has been received from the POS terminal 10x in ACT45. If a batch cancel command has not been received, the processor 21 judges NO in ACT45 and proceeds to ACT46.

[0054] The processor 21 checks the payment flag F again in ACT46. If the payment flag F is not "1", the processor 21 judges NO in ACT46 and returns to ACT41. On the other hand, if the payment flag F is "1", the processor 21 judges YES in ACT46 and proceeds to ACT47. The processor 21 checks whether or not a payment end command has been received from the POS terminal 10x in ACT47. If the payment end command has not been received, the processor 21 judges NO in ACT47 and returns to ACT41.

[0055] In this way, when the settlement flag F is "0", the processor 21 waits to receive a product registration command, a payment start command, a pause start command, or a batch cancellation command from the POS terminal 10x in ACT42 to ACT45. On the other hand, when the settlement flag F is "1", the processor 21 waits to receive a pause start command, a batch cancellation command, or a payment end command from the POS terminal 10x in ACT44, ACT45, and ACT47.

[0056] The payment start command is output from the POS terminal 10 where the payment start operation has been performed. After completing the registration of the product, the operator performs the payment start operation to select the customer's desired payment method from among payment methods such as cash, credit card, or electronic money. When the payment start operation has been performed, the payment start command is transmitted from the POS terminal 10x to the store server 20. The payment start command is received by the communication interface 26 of the store server 20 via the communication network 30. The payment start command includes the POS ID of the POS terminal 10x.

[0057] The payment completion command is output from the POS terminal 10 that has completed the payment process using the payment method selected by the payment start operation. For example, if cash or electronic money is selected as the payment method, the payment completion command is sent from the POS terminal 10x to the store server 20 in response to the issuance of a purchase receipt. For example, if a credit card is selected as the payment method, the payment completion command is sent from the POS terminal 10x to the store server 20 in response to the issuance of a credit slip. The payment completion command is received by the communication interface 26 of the store server 20 via the communication network 30. The payment completion command includes the POSID of the POS terminal 10x.

[0058] When a product registration command is received in the command standby state of ACT42 to ACT45, that is, in the command standby state when the settlement flag F is "0", the processor 21 judges YES in ACT42 and proceeds to ACT48. The processor 21 sets the status Sx to "1" in ACT48. The processor 21 also increments the registration count RNBx by "1" in ACT49. After that, the processor 21 returns to ACT21 in Fig. 9. That is, the processor 21 enters the command standby state of ACT21 to ACT24.

[0059] In the command waiting state with the settlement flag F being "0", when a payment start command is received, the processor 21 judges YES in ACT43 and proceeds to ACT50. In ACT50, the processor 21 increases the customer number CNB stored in the tally table 232 in association with the POSID included in the payment start command by "1". Hereinafter, this customer number CNB will be referred to as customer number CNBx.

[0060] The processor 21 sets the payment flag F stored in the tally table 232 in association with the POSID as ACT51 to "1". After that, the processor 21 returns to ACT41. That is, the processor 21 enters a standby state for ACT44, ACT45, and ACT47, that is, a standby state for a command when the payment flag F is "1".

[0061] When the processor 21 receives a pause start command in a command waiting state when the payment flag F is "0" or "1", the processor 21 judges "YES" in ACT44 and proceeds to ACT52. The processor 21 stops the timer counter TCx based on the POSID included in the pause start command in ACT52. The processor 21 then waits for a pause end command from the POS terminal 10x in ACT53. When the processor 21 receives a pause end command, the processor 21 judges "YES" in ACT53 and proceeds to ACT54. The processor 21 restarts the timer counter TCx based on the POSID included in the pause end command in ACT54. The processor 21 then returns to ACT41. That is, the processor 21 enters a command waiting state when the payment flag F is "0" or "1".

[0062] When the processor 21 receives a batch cancel command in a command standby state with the settlement flag F being "0" or "1", the processor 21 judges YES in ACT45 and proceeds to ACT55. The processor 21 stops the timer counter TCx based on the POSID included in the batch cancel command in ACT55. The processor 21 then returns to ACT6 in FIG. 7. That is, the processor 21 sets the settlement flag F associated with the POSID in the tally table 232 to "0". The processor 21 also clears the tally item associated with the POSID in the tally table 232 to "0". The processor 21 also sets the status Sx to "0". The processor 21 then starts the timer counter TCx. The processor 21 then enters a command standby state in ACT11 to ACT13.

[0063] In the command waiting state with the settlement flag F at "1", when a payment completion command is received, the processor 21 judges YES in ACT47 and proceeds to ACT56. The processor 21 acquires the employee ID, closing time, and customer number CNBx stored in the tally table 232 in association with the POSID included in the payment completion command in ACT56. Hereinafter, this closing time will be referred to as closing time STBx. Also, the closing time stored in the evaluation table 231 in association with the employee ID will be referred to as closing time STax, the operating time as operating time OTA, and the number of customers as customer number CNAx.

[0064] The processor 21 adds the closing time STBx to the closing time STax as ACT 57. The processor 21 also adds the number of customers CNB to the number of customers CNAx as ACT 58. The closing time STAX will be made clear in the timer interrupt process (FIG. 11) described later.

[0065] In ACT59, the processor 21 adds the waiting time WTAx, the registration time RTAx, and the cut-off time STAx to the operating time OTAx. After completing the above processing, the processor 21 returns to ACT6 in Fig. 7. That is, the processor 21 sets the settlement flag F associated with the POSID in the tally table 232 to "0". The processor 21 also clears the tally item associated with the POSID in the tally table 232 to "0". The processor 21 also sets the status Sx to "0". The processor 21 also starts the timer counter TCx. The processor 21 then enters a command waiting state in ACT11 to ACT13.

[0066] Now, every time the timer counter TCx, which started in ACT9 in Fig. 7, counts one second, the store server 20 outputs a timer interrupt signal. Every time the processor 21 detects a timer interrupt signal, the processor 21 executes a timer interrupt process according to the procedure shown in Fig. 11.

[0067] That is, the processor 21 obtains the POSID from the timer interrupt signal as ACT 61. The timer interrupt signal includes the POSID that is associated with the timer counter TCx and stored in the timer memory 221.

[0068] The processor 21 checks whether the status Sx stored in the status memory 222 in association with that POSID as ACT62 is "0". If the status Sx is "0", the processor 21 determines YES in ACT62 and proceeds to ACT63. The processor 21 increases the waiting time WTBx stored in the aggregation table 232 in association with that POSID as ACT63 by "1". With this, the processor 21 ends the timer interrupt processing.

[0069] If the status Sx is not "0", the processor 21 judges NO in ACT62 and proceeds to ACT64. The processor 21 checks whether the status Sx is "1" in ACT64. If the status Sx is "1", the processor 21 judges YES in ACT64 and proceeds to ACT65. The processor 21 increments the registration time RTBx, which is associated with the POSID and stored in the aggregation table 232, by "1" in ACT65. With this, the processor 21 ends the timer interrupt processing.

[0070] If the status Sx is not "1", that is, if the status Sx is "2", the processor 21 judges NO in ACT64 and proceeds to ACT66. The processor 21 increments the cut-off time STBx, which is associated with the POSID and stored in the tally table 232, by "1" in ACT66. With this, the processor 21 ends the timer interrupt process.

[0071] As is clear from the above description of the operation, the store server 20 has functions as a detection means, a start means, an end means, a stop means, a restart means, a recording means, a counting means, and a clearing means. That is, the store server 20 detects events that occur in response to the operation of the POS terminal 10 in response to reception of, for example, a sign-on command, a sign-off command, a product registration command, a registration end command, a payment start command, a payment end command, a pause start command, a pause end command, a collective cancellation command, etc. (detection means).

[0072] When the event occurs in response to a command to start a task related to the evaluation of the operator, the store server 20 starts a timing operation. That is, when the status Sx becomes "0" in response to the reception of a sign-on command, the store server 20 starts a timing operation of the waiting time WTBx using the tally table 232 (starting means).

[0073] When the status Sx becomes "1" in response to receiving the product registration command, the store server 20 ends the timing operation of the waiting time WTBx (termination means). Then, the store server 20 starts timing the registration time RTBx using the tally table 232 (start means). The store server 20 also adds the waiting time WTBx to the waiting time WTAx in the evaluation table 231 associated with the employee ID of the operator (recording means).

[0074] When the status Sx becomes "2" in response to receiving the registration end command, the store server 20 ends the timing operation of the registration time RTBx (termination means). Then, the store server 20 starts the timing operation of the cut-off time STBx using the tally table 232 (start means). The store server 20 also adds the registration time RTBx to the registration time RTAx in the evaluation table 231 associated with the operator's employee ID (recording means).

[0075] When the status Sx becomes "0" in response to receiving the payment completion command, the store server 20 ends the timing operation of the cut-off time STBx (termination means). Then, the store server 20 starts timing the waiting time WTBx in the tallying table 232 (starting means). The store server 20 also adds the cut-off time STBx to the cut-off time STAx in the evaluation table 231 associated with the operator's employee ID (recording means).

[0076] When the store server 20 receives a pause start command while the status Sx is "1" or "2", it stops the time counting operation by the timer counter TCx (stop means). After that, when it receives a pause end command, it resumes the time counting operation by the timer counter TCx (restart means).

[0077] Furthermore, when the store server 20 receives a batch cancel command while the status Sx is "1" or "2", it stops the time counting operation by the timer counter TCx. Then, the store server 20 clears the waiting time WTAx, the registration time RTBx, and the cut-off time STBx (clearing means).

[0078] The store server 20 counts the number of registrations RNBx using the tally table 232 every time it receives a product registration command (counting means). Then, when it receives a registration end command, the store server 20 adds the number of registrations RNBx to the number of registrations SRNAx in the evaluation table 231 associated with the employee ID of the operator (recording means).

[0079] Furthermore, each time the store server 20 receives a payment start command, it counts the number of customers CNBx using the tally table 232 (counting means). Then, when the store server 20 receives a payment end command, it adds the number of customers CNBx to the number of customers CNAx in the evaluation table 231 associated with the employee ID of the operator (recording means).

[0080] Figures 12 to 18 are timing diagrams showing example patterns of waiting time WTA, registration time RTA, and cut-off time STA managed by the store server 20. In Figures 12 to 18, the symbol CMa indicates a sign-on command. The symbol CMb indicates a product registration command. The symbol CMc indicates a registration end command. The symbol CMd indicates a payment start command. The symbol CMe indicates a payment end command. The symbol CMf indicates a sign-off command. The symbol CMg indicates a pause start command. The symbol CMh indicates a pause end command. The symbol CMi indicates a bulk cancel command.

[0081] 12 shows an example of an event in which commands are issued from the POS terminal 10 in the following order: sign-on command CMa, product registration command CMb, registration end command CMc, payment start command CMd, payment end command CMe, and sign-off command CMf. In this example, the time from the sign-on command CMa to the first product registration command CMb and the time from the payment end command CMe to the next product registration command CMb or sign-off command CMf are measured as the waiting time WTA. The time from the first product registration command CMb to the registration end command CMc is managed as the registration time RTA. The time from the registration end command CMc to the payment end command CMe is managed as the closing time STA.

[0082] 13 shows an example of an event in which a product registration command CMb occurs after a registration end command CMc. In this example, the time from the first registration end command CMc to the product registration command CMb and the time from the next registration end command CMc to the payment end command CMe are managed as a cut-off time STA.

[0083] 14 shows an example of an event in which a pause start command CMg and a pause end command CMh occur during the time the waiting time WTA is being measured. In this example, the timer counter TCx does not stop during the period from when the pause start command CMg is received to when the pause end command CMh is received, so this period is included in the waiting time WTA.

[0084] 15 shows an example of an event in which a pause start command CMg and a pause end command CMh occur during the time that the registration time RTA is being measured. In this example, the timer counter TCx stops during the period from when the pause start command CMg is received to when the pause end command CMh is received, and is therefore excluded from the registration time RTA.

[0085] 16 shows an example of an event in which a pause start command CMg and a pause end command CMh occur during the time when the cut-off time STA is being counted. In this example, the timer counter TCx stops during the period from when the pause start command CMg is received to when the pause end command CMh is received, and is therefore excluded from the cut-off time STA.

[0086] 17 shows an example of an event in which a collective cancel command CMi occurs while the registration time RTA is being measured. In this example, when the collective cancel command CMi occurs, the registration time RTB in the tally table 232 is cleared to "0," so it is not included in the registration time RTA. However, the waiting time WTB in the tally table 232 has already been added to the waiting time WTA.

[0087] 18 shows an example of an event in which a batch cancel command CMi occurs while the cutoff time STA is being measured. In this example, when the batch cancel command CMi occurs, the cutoff time STB in the tally table 232 is cleared to "0," so it is not included in the cutoff time STA. However, the waiting time WTB and registration time RTB in the tally table 232 have already been added to the waiting time WTA and registration time RTA.

[0088] According to this embodiment, the time when the operator temporarily leaves the register during product registration or payment is excluded from the registration time RTA or closing time STA related to the evaluation of the operator. Meanwhile, the registration count RNA and customer count CNA of the operator are counted regardless of whether there is a break. Therefore, the time when the operator actually operates the POS terminal 10 can be properly managed together with the productivity-related counts such as the registration count RNA and customer count CNA associated with the operation.

[0089] In addition, if a customer requests a bulk cancellation during product registration or payment, the registration time RTB or cut-off time STB up to that point will not be added to the registration time RTA or cut-off time STA related to the evaluation. In this case, the operator's registration count RNA and customer count CNA will not be counted. Therefore, in this regard as well, the above-mentioned action and effect will be achieved.

[0090] Although the embodiment of the operator management device has been described above, the embodiment is not limited to this.

[0091] In the above embodiment, the store server 20 of the POS system 1 has a function as the operator management device. In another embodiment, a dedicated server that functions as the operator management device may be connected to the communication network 30. Alternatively, the dedicated server may be configured as a cloud system and may be accessible via the store server 20.

[0092] In the above embodiment, the POS terminal 10 having information processing functions related to product registration, settlement, etc. is exemplified. The POS terminal may be a two-person POS terminal in which product registration and settlement are separately performed. In this case, the waiting time WTA and registration time RTA are managed for the POS terminal performing product registration. The waiting time WTA and closing time STA are managed for the POS terminal performing settlement. In addition, if the POS terminal performing product registration is operated by a store clerk, but the POS terminal performing settlement is operated by a customer, management of the POS terminal performing settlement may be omitted.

[0093] In the above embodiment, a case has been exemplified in which the timing operation is performed in real time upon receiving a command output from the POS terminal 10 to the store server 20. In this regard, the timing operation does not have to be performed in real time. For example, a log file of operation history may be received from the POS terminal 10, and the timing operation may be performed by batch processing.

[0094] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. The invention as originally claimed in the present application is set forth below. [1] An operator management device comprising: a detection means for detecting an event occurring in response to an operator's operation from a POS terminal; a start means for starting a timing operation when the event is an event occurring in response to a command to start a task related to the operator's evaluation; a termination means for terminating the timing operation when the event is an event occurring in response to a command to end the task; a stop means for stopping the timing operation when the event is an event occurring in response to a command to interrupt the task; a restart means for restarting the timing operation when the event is an event occurring in response to a command to resume the task; and a recording means for recording the time clocked by the timing operation as the operator's evaluation time. [2] An operator management device as described in Appendix [1], further comprising a counting means for counting the number of times the event is executed when the event occurs in response to an execution operation of the business, and the recording means records the number of times the event is executed in association with the evaluation time. [3] The operator management device according to appendix [2], wherein the task includes a product registration task, and the number of times the registration task is performed is the number of times the product is registered. [4] The operator management device according to appendix [2], wherein the operation includes a settlement operation of a commercial transaction, and the number of times the settlement operation is performed is the number of times the commercial transaction is settled. [5] An operator management device described in any one of appendices [1] to [4], further comprising a clearing means for clearing the time clocked by the timing operation when the event occurs in response to a cancellation command operation of the service. [6] A control program for causing a computer of an operator management device that manages operators of POS terminals to function as: a detection means for detecting an event that has occurred in response to the operation of the operator from the POS terminal; a starting means for starting a timing operation when the event has occurred in response to a command to start a task related to the evaluation of the operator; a terminating means for terminating the timing operation when the event has occurred in response to a command to end the task; a stopping means for stopping the timing operation when the event has occurred in response to a command to interrupt the task; a restarting means for restarting the timing operation when the event has occurred in response to a command to resume the task; and a recording means for recording the time clocked by the timing operation as the evaluation time of the operator. [Explanation of symbols]

[0095] 1...POS system, 10...POS terminal, 20...store server, 21...processor, 22...main memory, 23...auxiliary storage device, 24...clock, 25...input / output interface, 26...communication interface, 27...system transmission path, 30...communication network, 221...timer memory, 222...status memory, 231...evaluation table, 232...aggregation table.

Claims

1. a receiving means for receiving a command output from the POS terminal in response to an operation by an operator; a start means for starting a timing operation when the command received by the receiving means is a command output in response to a start command operation of a task related to the evaluation of the operator; a termination means for terminating the timing operation when the command received by the receiving means is a command output in response to an operation for instructing the termination of the task; a stop means for stopping the clocking operation when the command received by the receiving means is a command output in response to an interrupt command operation of the task; restarting means for restarting the timekeeping operation when the command received by the receiving means is a command output in response to an operation for instructing restart of the task; a waiting time counting means for, when a command output in response to a command to start a task related to the evaluation of the operator is a sign-on command, counting a time from when the sign-on command is received until when a product registration command output when a product registration operation is performed at the POS terminal is received as a waiting time, and not stopping the counting of the waiting time while the waiting time is being counted even if a command output in response to a command to interrupt the task is received; a recording means for recording the time including the waiting time measured by the timing operation as an evaluation time of the operator; An operator management device comprising:

2. a counting means for counting the number of executions when the command received by said receiving means is a command output in response to an execution operation of said business; Further comprising: The operator management device according to claim 1 , wherein the recording means records the number of executions in association with the evaluation time.

3. The operator management device according to claim 2 , wherein the task includes a task of registering a product, and the number of times the registration task has been performed is the number of times the product has been registered.

4. The operator management device according to claim 2 , wherein the transaction includes a settlement transaction, and the number of executions of the settlement transaction is the number of times the transaction has been settled.

5. a clearing means for clearing the time measured by the timing operation when the command received by the receiving means is a batch cancel command output in response to a cancel instruction operation for the task; The operator management device according to any one of claims 1 to 4, further comprising:

6. A computer of an operator management device that manages operators of the POS terminals, a receiving means for receiving a command output from the POS terminal in response to an operation by an operator; a start means for starting a timing operation when the command received by the receiving means is a command output in response to a start command operation of a task related to the evaluation of the operator; a termination means for terminating the timing operation when the command received by the receiving means is a command output in response to an operation for instructing termination of the task; a stop means for stopping the clocking operation when the command received by the receiving means is a command output in response to an interrupt command operation of the task; a restart means for restarting the timekeeping operation when the command received by the receiving means is a command output in response to a restart instruction operation of the operation; a waiting time counting means for, when a command output in response to a command to start a task related to the evaluation of the operator is a sign-on command, counting the time from when the sign-on command is received until when a product registration command output when a product registration operation is performed at the POS terminal is received as a waiting time, and not stopping the counting of the waiting time while the waiting time is being counted even if a command output in response to a command to interrupt the task is received; and a recording means for recording the time including the waiting time measured by the timing operation as an evaluation time of the operator; A control program that functions as a

Images