JP2007286657A - Equipment management unit and equipment management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an equipment management technology for allowing different operators to perform first and second operations to equipment without individually limiting the different operators to the first and second operations in advance. <P>SOLUTION: An equipment management part 30 is provided with an operator data storage part 42 for storing operator data for setting whether to permit each operator to perform a first operation to equipment. When an operator identified by identification equipment 50 is matched with the authorized operator who is permitted to perform the first operation on the operator data, an equipment status setting part 34 outputs a command for making the equipment set an permitted status to the first operation. When the operator identified by the identification equipment 50 installed in the equipment performs a second operation, an operator data changing part 36 automatically changes setting on the operator data of the identified operator. Thus, when the operator who is allowed to perform the first and second operations in initial setting performs the second operation, it is possible to inhibit the first operation. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

The present invention relates to a device management technique that permits a specific operation of a specific device to the operator when the operator identified by the identification device is the specific operator. In particular, the present invention relates to a device management technique for automatically changing permission / prohibition settings for other specific operations when a specific operator performs a specific operation.
The “device” referred to in this specification is represented by a computer and a POS system, but is not limited thereto. For example, it includes a printer operated via a computer, a game machine that is subject to maintenance work, and the like.

There is known a device management technique that permits a specific operation by an operator when the operator identified by the identification device is a specific operator for a device such as a computer. By restricting the operators who can perform a specific operation, the device is prevented from being illegally operated. The device management technology causes a device to be operated by the operator to be set to a state in which only a specific operator accepts a specific operation.
The device to be operated can be set to either a permitted state for accepting an operation or a prohibited state for not accepting an operation so that an unspecified operator cannot operate.
The device includes an identification device that identifies an operator of the device. The operator is identified by inputting an ID and password assigned to each operator or reading an ID card possessed by the operator. Alternatively, it is performed based on biological information such as an operator's fingerprint, a retinal pattern, and a vein pattern.
An authorized operator who is permitted a specific operation is registered in advance in a device or a device management apparatus that performs device management. The operator causes the identification device to identify himself / herself when performing a specific operation. When the identified operator matches a pre-registered authorized operator, the device or the device management apparatus sets the device to a permitted state for accepting a specific operation by the operator. On the other hand, when the identified operator does not match the pre-registered permitted operator, that is, when the identified operator is a non-permitted operator, the device or the device management apparatus operates the device. A prohibited state in which a specific operation by the user is not accepted. In the following, it is assumed that the device management apparatus sets a device to either a permitted state or a prohibited state.
An operator who is permitted a specific operation is referred to as a permitted operator for that operation. An operator who is not permitted a specific operation is referred to as a non-permitted operator for that operation.
Patent Document 1 discloses such a technique. The technique of Patent Document 1 includes a unit (identification device) that authenticates a person (operator) who operates a device, and a storage unit that stores a list of devices that can be operated in association with the authenticated person. When the authentication unit authenticates a specific person, the device group in the stored list is switched to an operable state, that is, a permission state for accepting an operation. By doing so, a plurality of device groups can be operated by one authentication. According to the technique described in Patent Literature 1, it is possible to set a device group associated with an authenticated person to a permitted state that can be operated simultaneously by one authentication.

JP 2003-248735 A

By the way, in a device or a group of devices for which a plurality of operations are prepared, it may be desired to prohibit other operations from an operator who has performed a predetermined operation. On the other hand, there are cases where it is desired to allow other operations only to an operator who has performed a predetermined operation.
When two objectives are achieved by connecting two processes executed by two different operations, the former is illegal because two operators are required for the two operations. Can be achieved. In the latter case, the purpose is achieved by one operator, so the responsibility for achieving the purpose can be clarified. Which case is better depends on the purpose achieved by the processing corresponding to the operation and the situation in which the device (or device group) is used.
As described above, there is a demand for a device management apparatus that can flexibly change the permitted operator / non-permitted operator for other operations in accordance with an operator who performs a predetermined operation on the device. Even when the number of operations is two or more, similarly, depending on the operator who performed the predetermined operation group, the permitted operator / non-permitted operator for the operation group different from the predetermined operation group can be flexibly changed. A device management apparatus that can be used is desired.
In the technique of Patent Document 1, a list of operable devices associated with an authenticated person is stored in advance in the storage device. Not only the technique of Patent Document 1, but in a conventional device management apparatus, a permitted operator for a specific operation on a specific device is set in advance. In the following, data for setting whether or not a specific operation is permitted for each operator will be referred to as operator data. The operator data is stored in a storage device accessible by the device management apparatus.
The device management device operates the device that is the target of the operation so as to accept the operation of the authenticated person only when the authenticated person matches the authorized operator set in the operator data. Set to a permission state that can be accepted. When changing the permitted operator for a specific operation, the operator or other operator must bother to correct the operator data. Therefore, whenever the operator who performs a specific operation differs, the operator data must be updated according to the operator. Each time the operator who performs a specific operation changes, it is complicated for the operator or another operator to correct the operator data.

  This invention was created in view of the said subject. The present invention relates to a device management apparatus that sets a state of a device that can be set to either a permission state for accepting a specific operation performed by an operator identified by the identification device and a prohibition state for not accepting a specific operation. Can be realized. The device management apparatus includes a device state setting unit that causes a device to be set to either a permitted state or a prohibited state for a specific operation performed by the operator according to a past operation performed by the identified operator. Prepare.

  According to the device management apparatus described above, the device can be set to either a permitted state or a prohibited state for a specific operation performed by the operator in accordance with a past operation performed by the operator. . This makes it unnecessary for the operator or another operator to modify the operator data each time the operator who performs a specific operation changes.

The device management apparatus further includes an operator data storage device that stores operator data for setting whether each operator is a permitted operator or a non-permitted operator, and an operator that changes settings on the operator data. It is preferable to include a data change unit and a device state setting unit that sets a device state based on operator data.
The operator data storage device stores, for each operator, operator data for setting whether to permit the first operation on the device.
The operator data changing unit changes the setting on the operator data of the identified operator when the operator identified by the identification device performs the second operation.
The device state setting unit sets the device to a permitted state for the first operation when the operator identified by the identification device matches the permitted operator permitted for the first operation on the operator data. In addition, when the operator identified by the identification device matches the non-permitted operator who does not permit the first operation on the operator data, the first operation is performed on the device that is the target of the first operation. Is set to a prohibited state.

Setting the device to the permitted state means, for example, setting the door for accessing the operation unit of the device to an unlocked state, or setting the device to enable the operation of the device by the operator. “Enabling” means executing a process corresponding to an operation by the operator. On the other hand, setting the device to the prohibited state means, for example, setting the door for accessing the operation unit of the device to the locked state, or setting the state to invalidate the operation of the device by the operator. .
According to the device management apparatus, when the operator identified by the identification device included in the device performs a second operation on the device, the operator data changing unit changes the operator data in accordance with the operation. . The operator data changing unit changes the setting state for the first operation of the operator who has performed the second operation to an unauthorized operator. Alternatively, the setting state for the first operation of the operator who performed the second operation is changed to the permitted operator.
In the former case, the first operation is prohibited for the operator who has performed the second operation. The first operation and the second operation can be permitted to different operators. In the latter case, the first operation is permitted for the operator who has performed the second operation. The first operator and the second operation can be permitted to the same operator.
As described above, according to the device management apparatus, when the operator performs the second operation, the permission / prohibition setting for the first operation of the operator is automatically changed in conjunction with the second operation. It is not necessary to bother to change the operator data each time the operator who performs the second operation is different.
Note that the device may be normally set to a prohibited state. Only when the identified operator matches the authorized operator registered in advance, the device management apparatus sets the device to a permitted state for accepting a specific operation by the operator, and when the operation is completed. You may make it set to a prohibition state again. Even in such a case, if the identified operator does not match the authorized operator registered in advance, the device management apparatus sets the device in a prohibited state in which a specific operation by the operator is not accepted. Is equivalent to

Further, in the conventional technique, every time the operator who performs the second operation is different, a predetermined operator modifies the operator data in order to change the first operation to permitted / prohibited for the operator. There must be. The situation where the operator data can be frequently modified by the operator may cause the security of limiting the specific operation to the specific operator.
According to the device management apparatus of the present invention, when a specific operator performs the second operation, the setting of permission / prohibition of the first operation for the specific operator on the operator data is automatically changed. Is done. As in the prior art, every time the operator who performs the second operation is different, there is no need for a predetermined operator to correct the operator data. Security for operation can be ensured more reliably.

In addition, the device management apparatus according to the present invention includes an operation history storage device that stores operation history data that specifies an operator and an operation performed by the operator, instead of having operator data, and the operator has a second An operation restriction condition data storage device may be provided that stores operation restriction condition data for setting whether to prohibit the first operation for the operator when an operation is performed. In this case, the device state setting unit refers to the operation history data, and detects that the operator identified by the identification device has performed the second operation in the past on the operation restriction condition data. When the past second operation is set to the condition for permitting the first operation, the device is set to the permitted state for the first operation, and the past second operation is set to the first operation. Is set to a prohibition condition, the device is set to a prohibition state for the first operation.
If the operation history data and the operation restriction condition data are provided instead of the operator data, the device state setting unit realizes the same functions as those having the operator data by referring to the data. be able to.

Even when the device state setting unit sets the device in a prohibited state for the first operation performed by the operator identified by the identification device, that is, the first operation is performed on the identified operator. Even in the case of prohibition, it may be assumed that the operator wants to allow the first operation. For example, when there is only one operator on the spot such as midnight. In such a case, it is preferable that the operator who wants to perform the first operation can be reset to the permitted state again even if the device is once set to the prohibited state for the first operation. .
In consideration of such a situation, the device management apparatus performs the identified operator when the device state setting unit sets the device in a prohibited state for the first operation performed by the identified operator. It is preferable to further include an output unit that presents an inquiry message as to whether or not to accept the first operation to the identified operator. In this case, it is preferable that the device state setting unit resets the device to a permitted state for the first operation when the identified operator inputs an instruction to accept the first operation.
According to the above configuration, an operator who wants to perform the first operation is originally set as a non-permitted operator, but an inquiry as to whether or not to accept the first operation is output. The operator can recognize that the first operation that is originally prohibited is accepted by the device as an exception. By doing so, self-control can be urged to the operator who is going to perform the first operation and the second operation for an illegal purpose.

When the device state setting unit resets the device to a permitted state in accordance with an instruction of an operator originally set as a non-permitted operator, the device management apparatus further includes the identified operator (first operation). It is preferable to provide a storage device that stores an operator who inputs an instruction to perform the operation in association with the first operation.
According to the above configuration, when an operator who is set as an unauthorized operator for the first operation dares to change the setting of the device and performs the first operation, the fact is stored. An operator who has performed an exceptional operation can be identified at a later date. With such a configuration, it is possible to identify an operator who has performed an unauthorized device operation.
The above-described operation history storage device may also be used as the storage device.

  It is also preferable that the operator data storage device stores data of an operator group associated with a predetermined operator. In this case, the operator data changing unit is configured to notify the predetermined operator on the operator data when the identified operator is the predetermined operator and the operator performs the second operation. It is preferable to change the setting for the first operation of the operators belonging to the associated operator group.

For example, when there are a large number of devices to be operated, such as game table maintenance, it is efficient for a plurality of operators to separately operate the game table. Here, in order to maintain the game table, for all the game tables, an operation (second operation) for unlocking the door of the housing storing the operation device for maintenance, and the respective game tables It is assumed that an operation (first operation) of the operation device for maintenance is prepared for each. It is assumed that the operators are divided into two groups, and in order to clarify the responsibility for each group, only the operators of one of the groups perform maintenance of the game machine. In such a case, according to the above configuration, when a predetermined operator of the first group performs an operation (second operation) to unlock the door of the housing, the operator data change unit The operator who performed operation 2 is set as an unauthorized operator for the operation of the maintenance operation device (first operation). In other words, the setting for the first operation of the operator who performed the second operation is changed to “prohibited”.
At the same time, the operator data changing unit sets the operators belonging to the first group excluding the operator who has performed the second operation as permitted operators for the first operation. In other words, the setting for the first operation of the operators belonging to the first group excluding the operator who performed the second operation is set to “permitted”.
On the other hand, an operator belonging to the second group is set as an unauthorized operator for the first operation. In other words, the setting for the first operation of the operators belonging to the second group is set to “prohibited”.
As a result, the first operation is permitted only to operators who belong to the first group and who are not operators who have performed the second operation.
In accordance with an operator who has performed an operation (second operation) for unlocking the door of the housing, an authorized person for the operation (first operation) of the maintenance operation device can be automatically changed. Even when an operator different from the previous one performs the second operation at a later date, the permitted operator for the first operation is changed according to the operator. The permitted operator for the first operation can be automatically changed according to the operator for the second operation.

  The above-mentioned effect due to the fact that the operator data storage device stores the data of the operator group associated with the predetermined operator can also be realized by using operation restriction data instead of the operator data. can do. That is, the operation restriction condition data may include data for setting whether or not the first operation is prohibited for another specific operator when the specific operator performs the second operation. That's fine. In this case, when the device state setting unit detects that the specific operator has performed the second operation in the past by referring to the operation history data, the device state setting unit performs the operation by the specific operator on the operation restriction condition data. When the second operation is set to a condition for permitting the first operation for the operator identified by the identification device, the device is set to the permitted state for the first operation, and the second operation by the specific operator is performed. When the second operation is set to a condition for prohibiting the first operation for the operator identified by the identification device, the device is set to a prohibited state for the first operation.

  The device management apparatus according to the present invention may change an authorized operator for each operation for a plurality of operations prepared for one device, or may be used for a plurality of devices connected via a network. The permitted operator may be changed for the prepared operation. One device management apparatus can set either a permitted state or a prohibited state for a plurality of devices.

The same functions as those of the device management apparatus can be realized by a computer program. This program is a device management program that sets a state of a device that can be set to either a permitted state for accepting a specific operation performed by an operator identified by the identification device or a prohibited state for not accepting a specific operation. It is. This program is for causing a computer that can access operator data for setting whether or not to permit a first operation to a device for each operator to realize an operator data change function and a device state setting function. It is a device management program.
The operator data change function is a function for changing the setting on the operator data of the identified operator when the operator identified by the identification device performs the second operation.
The device state setting function sets the device to a permitted state for the first operation when the operator identified by the identification device matches the permitted operator permitted for the first operation on the operator data. And a function for setting the device to a prohibited state for the first operation when the operator identified by the identification device matches the non-permitted operator who does not permit the first operation on the operator data. is there.

It can also be realized by the following computer program. This program is a device management program that sets a state of a device that can be set to either a permitted state for accepting a specific operation performed by an operator identified by the identification device or a prohibited state for not accepting a specific operation. It is. The program records operation history data specifying an operator and an operation performed by the operator, and whether or not the first operation is prohibited for the operator when the operator performs the second operation. The following functions are realized on a computer that can access the operation restriction condition data. The function refers to the past second data on the operation restriction condition data when it is detected that the operator identified by the identification device has performed the second operation in the past by referring to the operation history data. When the operation is set to a condition for permitting the first operation, the device is set to a permission state for the first operation, and the past second operation is set to a condition for prohibiting the first operation. A device state setting function for setting the device to a prohibited state for the first operation.
By causing the computer to execute the program, a computer having the same functions and effects as the device management apparatus can be realized.

  According to the present invention, when a specific operator performs a specific operation, a device management apparatus that automatically changes permission / non-permission settings for other specific operations for the specific operator. Can be provided. According to the present invention, every time an operator who performs a specific operation is different, an operation for correcting the permission / non-permission setting for the other specific operation of the operator can be made unnecessary.

<First embodiment>
Hereinafter, embodiments will be described in detail with reference to the drawings. The present embodiment is a device management apparatus that manages various devices such as POS terminals in a game arcade. First, the configuration of the game hall 100 will be described.
FIG. 1 shows a block diagram of the game room 100. The game hall 100 includes a hall computer 10, a game machine 12, a counting device 14, a POS terminal 16, and a POS host 18. Although the game hall 100 has a plurality of game tables 12, only one game table 12 is shown in FIG. In addition to the above-described devices, the game hall 100 includes a device that manages the number of stored balls of all the game tables 12 installed in the game hall 100, but these devices are not shown in FIG. It is.
The hall computer 10, the game machine 12, the counting device 14, the POS terminal 16, and the POS host 18 are mutually connected to devices that require data transmission / reception via a network.
The hall computer 10 includes a game data storage unit 24 and a device management unit 30 for storing game data. The hall computer 10 further includes a module for managing the hall, but is omitted in FIG. The device management unit 30 will be described in detail later.

In the game hall 100, the player plays a game on the game table 12. The game machine 12 is a game machine that uses pachinko balls as game media. First, a player purchases a game card similar to a so-called prepaid card at the game hall 100.
A card unit 20 is connected to each game table 12. The player can receive a predetermined number of pachinko balls by inserting the purchased game card into the card unit 20 and performing a predetermined operation. The player plays a game on the gaming table 12 using the rented pachinko balls.
In accordance with the game of the player, the number of throwing balls, the number of payout balls, the number of special prizes, and the like change on the gaming table 12. The game data such as the number of balls inserted, the number of balls paid out, and the number of special prizes of each game table 12 is sent to the hall computer 10. The hall computer 10 is provided with a game data storage unit 24, and game data sent from each game machine 12 is stored for each game machine 12.

  The counting device 14 is a device that counts pachinko balls acquired by the player. The player passes the acquired pachinko ball to the employee of the game hall 100. The employee operates the operation panel 52d connected to the counting device 14 to cause the counting device 14 to count the pachinko balls passed. The counting device 14 displays the counted number of pachinko balls on the display device 54d, and outputs from the printer 56 predetermined paper on which the counted number of pachinko balls is recorded as a barcode. The player receives the form and presents the form at the prize exchange. The player can obtain various prizes at the prize exchange according to the number of pachinko balls acquired.

A POS terminal 16 is installed at the gift exchange. The employee of the gift exchange office causes the reader 58 connected to the POS terminal 16 to read the barcode on the paper presented by the player. The display device 54c of the POS terminal 16 displays the number of pachinko balls that have been bar-coded on paper. At the same time, a list of prizes is also displayed on the display device 54c. Each prize has a predetermined number of pachinko balls or medals required for exchanging with the prize.
When the player tells the employee the desired prize, the employee operates the operation panel 52c of the POS terminal 16 and inputs the desired prize for the player. The POS terminal 16 calculates the number of pachinko balls corresponding to the prize by subtracting the number of pachinko balls corresponding to the prize from the number of pachinko balls read by the reader 58 and input to the POS terminal 16. A process for reducing the stock data of the prize by 1 is performed. The employee then gives the prize to the player.
The POS terminal 16 is connected to the POS host 18 and the hall computer 10 via a network. The POS terminal 16 and the POS host 18 manage the stock of prizes and exchange the prizes with the POS terminal 16 and the hall computer 10. The number of paid-out balls is managed.

The POS host 18 has a premium data storage unit 26. An example of the premium data storage unit 26 is shown in FIG. In the prize data storage unit 26, a prize ID for the POS terminal 16 or the POS host 18 to identify a prize, a prize name represented by the prize ID, and the number of pachinko balls necessary for exchange with the prize The number of medals necessary for exchanging the prize is stored. For example, the premium ID 1001 represents tobacco A. Tobacco A can be exchanged for 80 pachinko balls or 8 medals. Also, for example, the prize ID 1003 represents the candy A. Sweets A can be exchanged for 40 pachinko balls or 4 medals.
The prize data stored in the prize data storage unit 26 is corrected whenever the prize changes or when the number of pachinko balls or medals required for exchange is corrected for each prize. Correction of the prize data stored in the prize data storage unit 26 is performed by the employee operating the operation panel 52b while looking at the display device 54b connected to the POS host 18.

  An identification device 50a, an operation panel 52a, and a display device 54a are connected to the hall computer 10. The employee operates the operation panel 52a to correct the game data stored in the game data storage unit 24. In the game data correction, for example, a device (not shown) that counts the number of balls inserted, the number of balls paid out, the number of special prizes, etc. on the gaming table 12 has failed, and incorrect game data is recorded in the game data storage unit 24. In some cases, this is done to correct an error in the game data. Alternatively, the game data storage unit 24 deletes game data such as the number of balls thrown in and the number of balls to be paid out by an employee who should not be stored in the game data storage unit 24 originally.

For the sake of security, the above operation for correcting the game data stored in the game data storage unit 24 cannot be freely operated by an unspecified number of persons, for example, a player or a part-time job clerk. Therefore, the identification device 50 a is connected to the hall computer 10. Similarly, an identification device 50b, an identification device 50c, an identification device 50d, and an identification device 50e are connected to the POS host 18, the POS terminal 16, the counting device 14, and the card unit 20, respectively. Each identification device 50a-50d stores an employee ID and password assigned to each employee.
In addition, devices such as the POS host 18 and the counting device 14 including the hall computer 10 are invalid even if the operation panel 52d or the like is operated unless a permission command is input from the device management unit 30 of the hall computer 10. It is set to be. An operation panel (not shown) for maintaining the card unit 20 is disposed inside the card unit 20. The operation panel is disposed behind the electronically lockable door provided in the card unit 20 so that the player cannot touch it. The door of the card unit 20 is normally locked, and is not unlocked unless an unlocking command is input from the device management unit 30 of the hall computer 10. If the door provided on the card unit 20 is not unlocked, no one can touch the operation panel of the card unit 20.
In other words, each device can be set to either a permitted state in which an operation by the operator is accepted or a prohibited state in which an operation by the operator is not accepted. When each device receives a permission command output from the device management unit 30, each device is set to a permission state in which an operation by the operator is accepted. Conversely, when each device receives a non-permission command output by the device management unit 30, it is set in a prohibited state in which an operation by the operator is not accepted.
As described above, devices such as the card unit 20 and the POS terminal 16 can be operated only by specific employees.

Here, the operations targeted in this embodiment include the following operations.
(1) An operation of correcting the premium data stored in the premium data storage unit 26. This operation is performed when the employee operates the operation panel 52 b connected to the POS host 18. This operation is referred to as a premium data correction operation.
(2) An operation of the POS terminal 16 performed when providing a prize to the player according to the number of pachinko balls acquired by the player. This operation is performed when the employee operates the operation panel 52c connected to the POS terminal 16. This operation is referred to as a POS terminal operation.
(3) An operation for correcting the game data stored in the game data storage unit 24. This operation is performed when an employee operates the operation panel 52a connected to the hall computer 10. This operation is referred to as a game data correction operation.
The contents of the operations (1) to (3) are as described above.
(4) An operation for making the game data accessible from the operation panel 52a in order to correct the game data stored in the game data storage unit 24. The game data stored in the game data storage unit 24 is the most important data for the game hall 100. In order to enhance the security of the game data, a main operation for making the game data accessible from the operation panel 52a is prepared separately from the game data correction operation of (3). This operation is also performed when the employee operates the operation panel 52 a connected to the hall computer 10. This operation is referred to as a game data unlock operation.
(5) An operation for making the game data accessible by the operator data unlocking operation inaccessible again. This operation is also performed when the employee operates the operation panel 52 a connected to the hall computer 10. This operation is called a game data lock operation.
(6) An operation for maintaining the card unit 20. This operation is performed by an employee operating an operation panel (not shown) provided in the card unit 20. This operation is called card unit maintenance operation. This operation is, for example, an operation for changing the number of balls lent out at one time.
(7) Operation for making an operation panel provided in the card unit 20 accessible. The card unit 20 is provided for each gaming table 12. As described above, the operation panel is disposed at the back of an electronic lockable door (not shown) provided on the card unit 20 so as not to be mischieved by the player. Unless the door is unlocked and opened, the operation panel of the card unit 20 cannot be touched. Locking / unlocking the door of the card unit 20 can be operated from an operation panel 52 a connected to the hall computer 10. By this operation, all the card units 20 in the game hall 100 can be unlocked / locked at the same time. This operation is referred to as a card unit lock operation.
In other words, in this embodiment, the hall computer 10, the POS terminal 16, the POS host 18, and the card unit 20 have a permission state for accepting a specific operation performed by an operator identified by the identification device and a specific operation. This corresponds to a device that can be set to any of the prohibited states that are not accepted.

When an employee of the game hall 100 performs a specific operation on a specific device, his / her ID and password are input to the identification device 50 connected to the device to be operated. Thereafter, the employee performs a desired operation. When the operation is performed, the apparatus does not yet execute processing corresponding to the operation. Here, “identification device 50” means an identification device connected to a device to be operated among the identification devices 50a to 50e.
The identification device 50 identifies the employee by comparing the ID and password input by the employee with the stored employee ID and password. The device to which the identification device 50 is connected includes the ID of the identified employee (hereinafter referred to as employee ID), the ID of the device itself (device ID), and the operation ID that identifies the operation performed by the employee. Data is transmitted to the hall computer 10.
The transmitted data is sent to the device management unit 30 of the hall computer 10.

Next, the device management unit 30 will be described.
The device management unit 30 includes an input / output unit 32, a device state setting unit 34, an operator data changing unit 36, a message output unit 38, an operation history storage unit 40, and an operator data storage unit 42.
The operator data storage unit 42 stores operator data for setting whether or not each employee (operator) is permitted to perform each operation.
The input / output unit 32 receives data sent from each device and outputs a command from each unit in the device management unit 30 to each device.
The device status setting unit 34 identifies the device identified by the device ID based on the employee ID, the device ID, and the operation ID data identifying the employee's operation sent from each device. A command is output to the apparatus as to whether to set the permission state to accept the operation to be performed or to set the prohibition state to not accept the operation.
The operator data change unit 36 changes the operator data stored in the operator data storage unit 42 based on the data sent from each device.
The message output unit 38 transmits a predetermined message to the device specified by the device ID when a predetermined condition is satisfied. The message output by the message output unit 38 will be described later.
The operation history storage unit 40 stores the employee ID and operation ID received by the input / output unit 32 of the device management unit 30 together with the time when the data is input. Note that this storage does not store all employee IDs and operation IDs received by the device management unit 30. It is stored only when the device management unit 30 outputs a permission command for setting the device specified by the device ID to the permitted state for the operation specified by the operation ID. The operation history storage unit 40 may store all employee IDs and operation IDs received by the device management unit 30.

Processing performed by each unit of the device management unit 30 will be described. FIG. 3 is a flowchart of processing performed by the device management unit 30.
For example, when the employee performs the premium data correction operation (1) described above, the employee inputs his / her employee ID and password to the identification device 50b of the POS host 18. Thereafter, using the operation panel 52b of the POS host 18, the fact that the operation to be performed is a premium data correction operation is input. This input is performed, for example, by displaying the type of operation on the display device 54b of the POS host 18 and instructing the employee to perform the free gift data correction process on the display.
The POS host 18 transmits the employee ID identified by the identification device 50b, the device ID of the POS host 18 itself, and the operation ID data for specifying the operation of the employee to the device management unit 30 of the hall computer 10. The operation ID here indicates a premium data correction operation.
The input / output unit 32 of the device management unit 30 receives the employee ID sent from the POS host 18, the device ID of the POS host 18 itself, and the operation ID data for specifying the operation of the employee (step). S100).
The input data is sent to the device state setting unit 34. The device state setting unit 34 collates the sent data with the operator data stored in the operator data storage unit 42. The device state setting unit 34 determines whether or not the operation identified by the sent operation ID is permitted for the employee identified by the employee ID on the operator data (step S102). .

A specific example of the contents of the operator data stored in the operator data storage unit 42 is shown in FIG. In the leftmost column of FIG. 4, employee IDs for identifying each employee by the device management unit 30 are described. In the uppermost line of FIG. 4, the names of the respective devices are described. Each operation name is written after the second column from the left of the second row from the top. Whether to allow the operations listed in the second row from the top to the employees listed in the leftmost column in the columns after the third row from the top and after the second column from the left The setting is written. In these columns, “1” or “0” is written. “1” represents that the corresponding operation is permitted to the corresponding employee, and “0” represents that the corresponding operation is not permitted, that is, prohibited. For example, for an employee whose employee ID is A001, “0” is set in the counting device operation column, and “1” is set in the prize data correction operation column. This indicates that the employee identified by ID A001 is not permitted to perform the counting device operation and is permitted to perform the premium data correction operation. An employee who is set to “permitted” for a predetermined operation on the operator data is referred to as a permitted operator for the operation. An employee who is set to “prohibited” for a predetermined operation is referred to as an unauthorized operator for the operation.
In FIG. 4, in the column indicated by the broken lines 80, 82, and 84, the numbers on the left represent the initial settings. The arrows and the numbers on the right side described in these columns will be described later. Further, FIG. 4 does not show the columns for the card unit maintenance operation (6) and the card unit lock operation (7). These operations are shown in FIG. The operator data relating to the card unit maintenance operation and the card unit lock operation is shown in FIG. 7 merely for ease of explanation.

Assume that the employee ID input in step S100 is A001. Hereinafter, an employee whose employee ID is A001 is referred to as employee A001.
The input operation ID indicates a free gift data correction operation. Referring to FIG. 4, “1” is set in the column corresponding to the premium data correction operation of employee A001. Therefore, the employee A001 is set to “permitted” for the premium data correction operation.
The device state setting unit 34 refers to the operator data shown in FIG. 4, and performs an operation (in this case, a prize data correction operation) specified by the input operation ID with respect to the employee ID input in step S100. ) Is allowed. That is, the conditional branch in step S102 is YES. If the conditional branch in step S102 is YES, the process proceeds to step S104. In step S104, permission to set the device ID (in this case, the POS host 18 shown) input in step S100 to a state of accepting the operation (premium data correction operation) specified by the input operation ID. Outputs a command. The device state setting unit 34 also performs the process of step S104. The POS host 18 that has received the permission instruction is set to accept an operation performed by the employee A001. That is, the POS host 18 is set in a state of accepting a premium data correction operation. The fact that the POS host 18 is set to accept the premium data correction operation is displayed on the display device 54b connected to the POS host 18. Employee A001 sees this display and knows that POS host 18 has been set to accept a free gift data correction operation. The employee A001 performs a premium data correction operation on the POS host 18. Since the POS host 18 is set to accept a premium data correction operation, the POS host 18 executes processing according to the premium data correction operation by the employee A001. In this way, the employee A001 can perform a premium data correction operation on the POS host 18.

After executing step S104, the device management unit 30 executes an operator data correction process (step S106). The processing in step S106 is executed by the operator data changing unit 36.
The operator data change unit 36 stores an operator data change condition table that describes conditions for changing operator data. This table describes a condition for changing the setting for another specific operation for the operator in the operator data when the specific operator input in step S100 performs the input operation. .
The contents of the operator data change condition table are shown in FIG. Each operation name is described in the column of “operation name” in FIG. In the “prohibited condition” column, conditions for changing the operation described in the “operation name” column to the “prohibited” setting in the operator data shown in FIG. 4 are described. In the “permitted condition” column, a condition for changing the operation described in the “operation name” column to the “permitted” setting is described. In the table shown in FIG. 5, the leftmost column of “No (number)” is described for the purpose of distinguishing each row for the sake of explanation.
No. of the table shown in FIG. A description will be given by taking 1 row as an example. No. In the “operation name” column in the first row, “Premium data correction operation” is written. The POS terminal operation is written in the “prohibited condition” column. In this case, when the operator input in step S100 performs the POS terminal operation, the setting for the premium data correction operation of the operator is changed to “prohibited” in the operator data.
No. 1 of the first table shown in FIG. A description will be given taking the second row as an example. In the “operation name” column of this line, the POS terminal operation is described. In the “prohibited condition” column, a premium data correction operation is described. In this case, when the operator input in step S100 performs a gift data correction operation, the setting for the operator's POS terminal operation is set to “prohibited” in the operator data shown in FIG.
No. 1 of the first table shown in FIG. A description will be given by taking line 4 as an example. In the “operation name” column of this row, a game data lock operation is described. In the “permitted condition” column, a game data unlock operation is described. In this case, when the operator input in step S100 performs a game data unlock operation, the setting for the game data lock operation of the operator is set to “permitted” in the operator data shown in FIG.
In the present embodiment, when the permission command in step S104 shown in FIG. 3 is output, it is determined that the employee input in step S100 has performed the input operation. In addition, when each device executes a process corresponding to the operation of the employee, it is also preferable that the operation ID for specifying the operation is transmitted to the device management unit 30. In this case, the device management unit 30 may determine that the employee input in step S100 has performed the input operation when the operation ID is received.

  In the example described above, in step S100, the ID of employee A001 and the operation ID for specifying the premium data correction operation are input. In step S104, a command for permitting a gift data correction operation is output to the POS host 18. The device management unit 30 determines that the employee A001 has performed the premium data correction operation based on the output of the command for permitting the premium data correction operation. At this time, the operator data changing unit 36 changes the setting for the POS terminal operation of the employee A001 in the operator data to “prohibited” in accordance with the conditions described in the table shown in FIG. The result of the processing is indicated by a broken line 80 in FIG. In the column indicated by the broken line 80, “1 → 0” is written. That is, the operator data changing unit 36 changes the column for the POS terminal operation of the employee A001 in the operator data from “1” indicating “permitted” to “0” indicating “prohibited”. This process is the “operator data correction” process in step S106 shown in FIG.

When employee A001 performs a free gift data processing operation by the processing in step S106, the POS terminal operation initially set to “permitted” for employee A001 in the operator data is changed to “prohibited”. .
By the processing in step S106, it is possible to prevent the employee A001 from improperly providing a gift exchange for a specific player. Here, the convenience is the following operation. Employee A001 performs a prize data correction operation so that prizes can be exchanged with fewer pachinko balls than usual when a specific player exchanges prizes. After performing the premium data correction operation, the POS terminal operation is performed based on the corrected premium data for the specific player. Thereafter, an operation for recorrecting the contents of the premium data to the original state is performed. Through the series of operations described above, the employee A001 can provide a prize to a specific player under conditions that are more advantageous than those of other players. According to the present embodiment, the device management unit 30 prohibits the POS terminal operation for the employee who performed the premium data correction operation. As a result, the above-described fraud can be prevented.

In the conventional technique, in order to prevent the above-described unauthorized operation, it is necessary to set the operator data as follows. That is, the POS terminal operation is prohibited in advance for employees who are permitted to perform the premium data correction operation. On the contrary, for the employee who is permitted to operate the POS terminal, the premium data correction operation is prohibited in advance. By setting the operator data in such a manner, the above-described unauthorized operation can be prevented. However, such setting of the operator data limits the number of employees who are permitted to perform the premium data correction operation and the number of employees who are permitted to operate the POS terminal. If the number of employees permitted to operate is limited to a small number, the following problems arise. That is, when the premium data correction operation is to be performed, there is a high possibility that the employee who is permitted to perform the operation is absent. Similarly, when the POS terminal operation is to be performed, there is a high possibility that the employee who is permitted to perform the operation is absent. When a certain operation such as POS terminal operation is to be performed and the employee who is permitted to do so is absent, the other employee modifies the operator data so that the employee who is not particularly absent It is necessary to change the setting to allow a predetermined operation to be performed. If the number of employees permitted to operate is limited to a small number of employees, there is a high possibility that the operator data needs to be corrected as described above. Such an operation for correcting operator data is troublesome.
In addition, an operation for correcting the operator data is one of the device operations in the game hall 100. Therefore, the operation for correcting the operator data is also limited to specific employees. When there is no employee who is allowed to perform an operation for correcting the operator data, the operator data cannot be corrected.
On the other hand, if there is a possibility that the employee frequently corrects the operator data due to the above-mentioned reasons, there is a possibility that security that restricts a specific operation to a specific operator may be embodies.
The above-described problem becomes more likely to occur as the number of employees permitted to perform the operations such as the premium data correction operation and the POS terminal operation is limited. Therefore, it is better to allow as many employees as possible for each operation. On the other hand, if a plurality of operations are permitted for each employee, there is room for executing the above-described unauthorized operations.
In the present embodiment, as shown in the operator data of FIG. 4, in the initial state, the premium data correction operation and the POS terminal operation are set to “permitted” for three employees A001, A002, and A003. Here, when the employee A001 performs a free gift data correction operation, the setting for the POS terminal operation of the employee A001 is changed from “permitted” to “prohibited” by the device management unit 30 as indicated by a broken line 80 in FIG. Is done. As a result, the employee A001 who performed the premium data correction operation cannot perform the POS terminal operation. According to the present embodiment, while setting operator data so as to allow a plurality of operations to many employees, for an employee who has performed a specific operation, a setting for another specific operation is set to “ Automatically change from “permitted” to “prohibited”. As a result, operation permission is given to many employees for each operation, and at the same time, other specific operations (in the above example, employees who have performed a specific operation (in the above example, the gift data correction operation) are performed. The setting for “POS terminal operation” can be changed to “prohibited”.
This eliminates the need for frequent operations for correcting operator data by employees. It is possible to reduce the trouble of correcting the operator data. In addition, it is possible to prevent the security from limiting specific operations to specific operators.

The effect of the device management unit 30 of this embodiment will be described using another operation as an example. Here, the game data correction operation (3), the game data unlock operation (4), and the game data lock operation (5) described above are given as examples.
In the game hall 100 of the present embodiment, in order for an employee to perform a game data correction operation, first, a game data unlock operation is performed, and the game data can be accessed from the operation panel 52a connected to the hall computer 10. It is necessary to. This is because the game data is important data for the game arcade 100, so that the game data unlocking operation and the game data correcting operation are performed by separate employees, and the security of the game data correcting operation is increased. Because.
As shown in FIG. 4, in the operator data, a game data unlock operation and a game data correction operation are permitted to employees A001, A002 and A003. In the columns indicated by the broken lines 82 and 84, the numerical values on the left side indicate the initial settings.
Now, it is assumed that employee A002 performs a game data unlock operation. The employee A002 inputs his / her ID number and password to the identification device 50a (see FIG. 1) connected to the hall computer 10, and indicates that the operation to be performed is a game data unlocking operation. To the operation panel 52a connected to the.
The hall computer 10 sends the employee ID (A002 in this example) identified by the identification device 50a and the operation ID specifying the game data unlocking operation input by the employee to the input / output unit 32 of the device management unit 30. Input (step S100 in FIG. 3).
The device state setting unit 34 refers to the operator data shown in FIG. 4 and determines whether or not the game data unlocking operation is permitted for the employee A002 (step S102). As shown in FIG. 4, in the operator data, the game data unlocking operation is set to “permitted” for the employee A002, and therefore the branch determination in step S102 is YES. The device state setting unit 34 outputs a permission command for setting the hall computer 10 to accept the game data unlocking operation via the input / output unit 32 (step S104). The hall computer 10 that has received the permission command is set to a permission state for accepting a game data unlocking operation. The fact that the hall computer 10 is set to the permission state for accepting the game data unlocking operation is displayed on the display device 54a connected to the hall computer 10. Employee A002 sees this display and performs a game data unlock operation. Since the hall computer 10 is set in a permission state for accepting the game data unlock operation, the hall computer 10 executes a process of accepting the operation and unlocking the game data. That is, the hall computer 10 executes a process for making game data accessible. Thus, the game data can be accessed by the game data unlock operation of the employee A002.

  On the other hand, the operator data changing unit 36 refers to the table shown in FIG. 5 and changes the setting of permission / prohibition of a predetermined operation for the employee A002 on the operator data. No. 5 in FIG. As shown in the row 5, the game data correction operation is set to the “prohibition condition” for the game data unlock operation. No. 5 in FIG. As shown in the row 4, the game data unlock operation is set to “permission condition” for the game data unlock operation. The operator data changing unit 36 has a table No. Based on the setting of line 5, the setting for the game data correction operation of employee A002 is changed from “permitted” to “prohibited”. This is indicated by the dashed line 84 in FIG. In the column indicated by the broken line 84, “1 → 0” is written. This indicates that the game data correction operation for the employee A002 was initially set to “1”, that is, “permitted”, but changed to “0”, that is, “prohibited”. At the same time, the operator data changing unit 36 has a table No. Based on the setting of the row 4, the setting for the game data lock operation of the employee A002 is changed from “prohibited” to “permitted”. This is indicated by the broken line 82 in FIG. In the column indicated by the broken line 82, “0 → 1” is written. This indicates that the game data lock operation for the employee A002 was originally set to “0”, that is, “prohibited”, but changed to “1”, that is, “permitted”. The above operator data correction process is performed in step S106 shown in FIG.

The following effects can be obtained by the above operator data correction processing. In other words, the employee A002 who has performed the game data unlock operation is prohibited from the game data correction operation that was originally permitted and the game data lock operation that was originally prohibited.
The employee A002 who has performed the game data unlock operation cannot perform the game data correction operation. As a result, the game data unlock operation and the game data correction operation can be performed by different employees. On the other hand, the game data lock operation is permitted only to the employee A002. As a result, it is possible to prevent other employees from locking the game data without permission, and it is possible to impose a responsibility to always lock the game data to the employee A002 who has unlocked the game data. That is, by permitting only the same employee to perform the unlocking operation and the locking operation of the game data, it is possible to clarify the responsibility of the gaming data unlocking operation and the locking operation.
In the present embodiment, as shown in FIG. 4, the game data unlocking operation and the game data correcting operation are initially permitted to employees A001, A002, and A003. On the other hand, any employee is prohibited from performing the game data lock operation.
That is, game data unlocking operation and game data correcting operation are permitted for many employees. Any of the employees A001, A002, and A003 can operate the game data unlocking operation. On the other hand, game data correction processing is prohibited for employees who have performed a game data unlock operation. At the same time, the game data lock operation is permitted only for the employee.
As described above, according to the device management unit 30 of the present embodiment, a plurality of operations (employees) can be permitted and a plurality of operations can be permitted. Other specific operations can be automatically prohibited or other specific operations can be permitted. There is no need for other employees to bother to modify the operator data according to the operator who performed the specific operation. In other words, since many operations (employees) can be permitted as an initial setting, it is possible to reduce the possibility that there are no permitted operators for the operations to be performed.
In addition, according to the device management unit 30 of the present embodiment, when a specific operator performs a specific operation, the operator corrects the operator data illegally by automatically correcting the operator data. Can be prevented.
Specifically, when the operator identified by the identification device performs a specific operation (second operation), the device management unit 30 performs other specific identification of the identified operator in the operator data. The setting for the operation (first operation) is changed to an unauthorized operator (in other words, the setting is changed to “prohibited”). Alternatively, the setting for another specific operation (first operation) of the identified operator is changed to an authorized operator (in other words, the setting is changed to “permitted”). Then, when the identification device identifies the operator who is set as the permitted operator for the first operation in the operator data, the device is set to the permitted state for the first operation. Further, when the identification device identifies an operator who is set as an unauthorized operator for the first operation in the operator data, the device is set in a prohibited state for the first operation.

Returning to the flowchart of FIG. 3, processing in the case where the employee input in step S100 is set as a non-permitted operator for the input operation in step S102 (step S102: NO) will be described.
In this case, the device state setting unit 34 outputs a non-permission command for setting the device specified by the device ID input in step S100 to a state in which the operation specified by the input operation ID is not accepted. (Step S110). As a result, the device that has received the non-permission command does not execute the operation of the operator.
The device management unit 30 executes the process of step S112 following step S110. In step S112, the message output unit 38 of the device management unit 30 outputs a message “Do you want to execute the operation” to the device specified by the device ID input in step S100. The output message is displayed on a display device connected to the device specified by the device ID. The employee inputs a YES / NO instruction to the displayed message to the device that is the target of the operation. The instruction input by the employee is sent again to the device management unit 30 from the apparatus. In the case where the employee's instruction is YES, that is, an instruction to continue the operation to be performed (step S114: YES), the device state setting unit 34 inputs the operation ID input to the device input in step S100. A permission command for setting to a state of accepting the operation specified by is output (step S116). The permission command is the same as the permission command output in step S104.
The device that has received the permission command is set to a state that accepts an operation that the employee is about to perform. The device displays on the display device that the employee is set to accept an operation to be performed. The employee who sees this display recognizes that the device is set to the permitted state. When the employee performs an operation, the device set in the permitted state executes a process according to the operation.
When the permission command is output in step S116 and the permission command is output in step S104, the device management unit 30 operates the input employee and the input operation together with the time when the data is input. It memorize | stores in the log | history memory | storage part 40 (step S108).
On the other hand, if the employee's instruction to the message “Do you want to execute the operation” is NO (step S114: NO), the process is ended as it is.

Steps S112, 114, and 116 are effective for the following situation. That is, when the employee needs to perform a specific operation that is not permitted by the employee, the device management unit 30 can respond flexibly. For example, as shown in FIG. 4, employee A001 is not permitted to operate the counting device on the operator data. However, there may be situations where employees other than the employee A001 are absent at the place where the counting device 14 is placed. In such a case, the device management unit 30 sets the permitted state to accept the counting device operation even for the employee A001 who is set to “prohibited” for the counting device operation on the operator data. It is better to be able to. When the employee A001 instructs the continuation of the counting device operation in step S116, the device management unit 30 outputs a permission command for accepting the counting device operation to the counting device. By doing so, the device management unit 30 can set the device to exceptionally accept operations that are not originally permitted.
In this case, the message in step S112 is, for example, “This operation is a management target and the operation history is saved. Do you want to cancel it?”, Which is originally permitted to the employee who is going to perform the operation. This means that it is confirmed whether or not an operation that has not been accepted is exceptionally accepted. The confirmation message has an effect of encouraging employees who try to perform an unauthorized operation to suppress the unauthorized operation.
In step S108, the employee ID and operation ID input in step S100 are stored as a history. As a result, even if the operation of the apparatus is performed illegally, it is possible to specify who performed the operation at a later date.

Next, processing of the device management unit 30 will be described by taking (6) card unit maintenance operation and (7) card unit lock operation as an example.
As described above, the game hall 100 is provided with a plurality of game tables 12, and the card unit 20 is connected to each game table 12. Since the game hall 100 includes a large number of card units 20, the card unit maintenance operation is performed by a plurality of employees. On the other hand, in order to perform the card unit maintenance operation, an operation of unlocking the door for accessing the operation panel of the card unit 20 is required. The doors of all the card units 20 can be unlocked / locked all at once by the card unit lock operation for operating the operation panel 52a connected to the hall computer 10.
The employees of the playground 100 are divided into two groups, group A and group B. When the card unit maintenance operation is performed by an employee belonging to group A in order to clarify the responsibility for the operation, the employee belonging to group B cannot perform the operation. Conversely, when an employee belonging to group B performs a card unit maintenance operation, the employee belonging to group A is prevented from performing the operation.

The operator data storage unit 42 stores employee group data for specifying a group to which each employee belongs together with the operator data. The contents of the employee group data are shown in FIG. As shown in FIG. 6, the employee group data indicates that employees A001, A002, A003, and A004 belong to group A, and employees B001, B002, B003, and B004 belong to group B.
FIG. 7 shows the contents of the operator data for the card unit maintenance operation and the card unit lock operation. The operator data shown in FIG. 7 is integrated with the operator data shown in FIG. 4, but one operator data is divided into FIG. 4 and FIG. 7 for easy understanding. It is. In the columns indicated by the broken lines 86, 88, and 90 shown in FIG. 7, the left numerical value indicates the initial setting, and the right numerical value is changed by the operator data changing unit 36, as in the above example. Shows the settings. The processing of the device management unit 30 including the operator data changing unit 36 at this time will be described with reference to the flowchart shown in FIG.

Similar to the premium data correction operation and the game data correction operation described above, the employee A001 inputs his / her employee ID and password to the identification device 50a connected to the hall computer 10. Thereafter, the employee A001 performs the card unit lock operation using the operation panel 52a connected to the hall computer 10. At this time, the hall computer 10 has not executed the processing for the card unit lock operation performed, that is, the processing for unlocking all the card unit 20 doors.
The hall computer 10 inputs the employee ID of the employee A001 identified by the identification device 50a, the device ID, and the operation ID for specifying the card unit lock operation to the input / output unit 32 of the device management unit 30 (step S100). ).
The device state setting unit 34 refers to the operator data shown in FIG. 7 and determines whether or not the card unit lock operation is permitted for the employee A001 (step S102). As shown in FIG. 7, “1” is set as an initial setting in the column corresponding to the card unit lock operation of employee A001. That is, the setting for the card unit lock operation of the employee A001 is “permitted”. The device state setting unit 34 refers to the operator data shown in FIG. 7 and specifies that the card unit lock operation is permitted for the employee A001 input in step S100 (step S102: YES) In this case, the process proceeds to step S104. In step S <b> 104, the apparatus state setting unit 34 outputs a permission command for setting the permission state to accept the card unit lock operation to the hall computer 10. In this way, the hall computer 10 executes processing corresponding to the card unit lock operation operated by the employee A001. That is, the hall computer 10 unlocks the doors of all the card units 20 in the game room 100.

Next, the device management unit 30 proceeds to step S106. In step S106, the operator data changing unit 36 executes processing for changing operator data with reference to the table shown in FIG. 5 and the operator group data shown in FIG.
No. of the table shown in FIG. As described in line 7, there are two types of conditions (a) and (b) for prohibiting the card unit maintenance operation.
The prohibition condition (a) is a card unit lock operation. In accordance with this condition, the device state setting unit 34 changes the setting for the card unit maintenance operation of the employee A001 who performed the card unit lock operation from “permitted” to “prohibited”. This change is shown by the broken line 86 in FIG. That is, the employee A001 cannot perform the card unit maintenance operation permitted in the initial setting by performing the card unit lock operation.
The prohibition condition (b) is a card unit lock operation by another group member. This prohibition condition does not change the setting for another operation for the operator who performed the operation, but when a specific operator performs a specific operation, the permission / rejection for the predetermined operation of the other operator is performed. This is to change the prohibition setting. Here, the “predetermined operation” may be a “specific operation” performed by a specific operator, or may be an operation different from the “specific operation”. In this embodiment, the prohibition condition of (b) is that an employee belonging to group A (specific operator) performs an operation (specific operation) of a card unit lock (another operation) This is a condition that the setting for the card unit maintenance operation (predetermined operation) of the operator is changed from “permitted” to “prohibited”.
The operator data changing unit 36 changes the setting for the card unit maintenance operation of the employees belonging to the group B from “permitted” to “prohibited” in accordance with the condition (b). This change is illustrated by the dashed line 88 in FIG. That is, employees B001, B002, B003, and B004 belonging to group B cannot perform card unit maintenance operations that are permitted by default.

In the first table shown in FIG. As described in line 6, the card unit lock operation by another operator is set to "prohibited" with respect to the card unit lock operation. This condition also does not change the settings for other operations for the operator who performed a specific operation. When a specific operator performs a specific operation, permission for the predetermined operation of the other operator is permitted. / Changes the prohibition setting. No. More specifically, the condition shown in line 6 is that any employee (specific operator) is not one of those employees when the card unit lock operation (specific operation) is performed. The setting for the card unit lock operation (predetermined operation) of all employees (other operators) is changed from “permitted” to “prohibited”.
In accordance with this condition, the operator data changing unit 36 changes the setting for the card unit lock operation of all employees other than the employee A001 who performed the card unit lock operation from “permitted” to “prohibited”. This change is illustrated by the dashed line 90 in FIG. That is, employees A002, A003, A004, B001, B002, B003, and B004 other than the employee A001 cannot perform the card unit lock operation permitted in the initial setting.
The above process is the process of step S106 performed by the operator data changing unit 36.

The above processing by the device management unit 30 is summarized as follows.
In the operator data, the card unit lock operation and the card unit maintenance operation are set to “permitted” for all employees (here, employees belonging to either group A or group B) by default. Has been.
When the employee A001 belonging to the group A performs the card unit lock operation, the setting for the card unit maintenance operation of the employee belonging to the group B is changed from “permitted” to “prohibited” in the operator data. At the same time, the setting for the card unit lock operation of all employees other than employee A001 is changed from “permitted” to “prohibited”.

When the employee A001 belonging to the group A performs the card unit lock operation for unlocking the door of the card unit 20 by the above process, only the employees belonging to the group A other than the employee A001 can perform the card unit maintenance operation. At the same time, the card unit lock operation for locking the door of the card unit 20 can be performed only by the employee A001 who has performed the operation for unlocking the door.
With the above processing, the card unit lock operation for relocking the door of the card unit 20 once unlocked must be performed again only by the employee A001 who unlocked the door. Employees who have unlocked the door are obligated to lock the door. By permitting only the same employee to unlock and lock the door of the card unit 20, it is possible to clarify the responsibilities of the door unlocking and locking.
In addition, the employee who performed the card unit lock operation cannot perform the card unit maintenance operation. This prevents the same employee from unlocking the door of the card unit 20 and maintaining the card unit 20. Unauthorized maintenance operations of the card unit 20 can be prevented.
Furthermore, only employees who belong to the same group as the employee who performed the card unit lock operation can perform the card unit maintenance operation. Employees belonging to other groups cannot perform card unit maintenance operations. This makes it possible to clarify the responsibilities of the group unit for the card unit maintenance operation.

In the operator data, the card unit lock operation is set to “permitted” for all employees by default. Any employee can perform the card unit lock operation. The device management unit 30 of this embodiment automatically changes the prohibition / permission setting for the card unit maintenance operation of the employee according to the employee who performed the card unit lock operation. At the same time, the prohibition / permission setting for the card unit maintenance operation and the card unit lock operation is automatically changed for employees other than the employee.
By doing so, it is possible to save the trouble of changing the operator data according to the employee who performed the card unit lock operation. Furthermore, security for subsequent operations (here, the card unit lock operation and the card unit maintenance operation) can be managed for each group of employees according to the employee who performed the card unit lock operation. In addition, in the initial setting of the operator data, the card unit lock operation and the card unit maintenance operation can be set to “permitted” for many employees. This can reduce the possibility that the employee who is permitted to perform the operation to be performed is absent.

  The operator group data shown in FIG. 6 is data that specifies whether the employee of the game hall 100 belongs to either the group A or the group B. In other words, this operator group data is equivalent to expressing “operator group data associated with a predetermined operator”. For example, when employee A001 is “predetermined operator”, the employees A002, A003, and A004 belong to the same group with respect to employee A001 who is the “predetermined operator”. This is because the employees B001, B002, B003, and B004 are associated as operators belonging to different groups with respect to the employee A001 that is the “predetermined operator”. The above logic is established even if any employee other than the employee A001 is designated as “predetermined employee”.

<Second embodiment>
Next, a second embodiment will be described. In the present embodiment, the configuration of the device management unit 30 is different from that of the first embodiment. The device management unit of the present embodiment has an operation restriction condition data storage unit instead of the operator data storage unit 40 and the operator data change unit 36 (see FIG. 1) included in the device management unit 30 of the first embodiment. . Since the other configuration is the same as that of the device management unit 30 shown in FIG. 1, the block diagram of the entire game hall in the second embodiment is not shown.
In this embodiment, the function of the device state setting unit 34 shown in FIG. 1 is slightly different from that of the first embodiment.
Hereinafter, the second embodiment will be described focusing on differences from the first embodiment.

In the present embodiment, the operation history storage unit 40 (see FIG. 1) is configured so that, when an employee performs some device operation, the employee (operator) and the employee are assigned to all operations to be managed. Data specifying the operation performed is stored in association with each other. The operation to be managed means an operation that can set the device to either a permitted state or a non-permitted state for the operation.
In the present embodiment, the operation restriction condition data storage unit stores data having the same contents as the operator data change condition table (see FIG. 5) in the first embodiment.

  FIG. 8 shows a flowchart of processing of the device management unit of processing in this embodiment. 8 is different from the flowchart of the first embodiment shown in FIG. 3 in the processing of step S201 and step S202 shown in FIG. In FIG. 8, the same number is attached | subjected to the step of the same process as the step shown in FIG. Description of the steps denoted by the same numbers as those in FIG. 3 is omitted.

In the present embodiment, in step S <b> 201, the device state setting unit 34 refers to the operation history data stored in the operation history storage unit 40. And what operation the employee identified by ID input by step S100 performed in the past is extracted.
Next, the device state setting unit 34 refers to operation restriction condition data, that is, data having the same contents as the operator data change condition table shown in FIG.
If the operation extracted in step S201 in the operation restriction condition data is set as a permission condition for the operation specified by the operation ID input in step S100, the device state setting unit 34 determines in step S100. It is determined that the operation specified by the operation ID input in step S100 is permitted for the employee specified by the input ID (step S202: YES). In this case, the process proceeds to step S104.
On the other hand, if the operation extracted in step S201 in the operation restriction condition data is set as a prohibition condition for the operation specified by the operation ID input in step S100, the device state setting unit 34 It is determined that the operation specified by the operation ID input in step S100 is prohibited for the employee specified by the ID input in S100 (step S202: NO). In this case, the process proceeds to step S110.

  With the above processing, in this embodiment, the device management unit has the operation restriction condition data storage unit, and the device state setting unit 34 performs the above processing, so that it is the same as the device management unit 30 of the first embodiment. Function can be realized.

  In the above description, the operation restriction condition data has the same data as the operator data change condition table shown in FIG. The operator data change condition table shown in FIG. 5 includes a column in which no prohibition condition or permission condition is set. In this case, the device management unit of the present embodiment may have operator data shown in FIGS. 4 and 7. In the operator data, an operation that is permitted and an operation that is not permitted are set for each operator. In step S202 of FIG. 8, the device state setting unit 34 first refers to the operator data and determines whether or not the operation specified by the operation ID is permitted for the operator specified by the operator ID. Is identified. Thereafter, the operation restriction condition data is referred to, and it is specified whether or not the past operation is set as a prohibition condition or a permission condition for the operation specified by the operation ID. That is, it is determined whether or not the operation prohibition / permission setting on the operator data is changed in the past operation. By referring to the operator data and the operation restriction condition data, is the operation specified by the operation ID input to the employee finally specified by the employee ID input in step S100 permitted? Judge whether or not. According to the above processing, in this embodiment, the device management unit 30 can perform the same operation as when the operator data is changed based on the past operation history without changing the operator data.

Further, FIG. 8 showing a flowchart of the process of the present embodiment is the same as the flowchart of FIG. 3 of the process in the first embodiment except for step S201 and step S202. That is, also in the present embodiment, the first operation performed by the identified operator is accepted when the device state setting unit sets the device in a prohibited state with respect to the first operation performed by the identified operator. Whether or not an inquiry message may be presented to the identified operator. In that case, when the identified operator inputs an instruction to accept the first operation, the device state setting unit resets the device to a permitted state for the first operation. Furthermore, when the device state setting unit resets the device to the permitted state for the first operation, the operation specified by the employee ID input in step S100 and the operation ID input Is also preferably stored in the operation history storage unit.
Further, the operation restriction condition data may include data corresponding to the employee group data (see FIG. 6) in the first embodiment. In other words, the operation restriction condition data includes data for setting whether or not the first operation is prohibited for another specific operator when the specific operator performs the second operation. You may go out. In this case, similar to the first embodiment, in response to an operation performed by a specific operator, another operation associated with the specific operator is permitted or prohibited. Also good. That is, the device state setting unit refers to the operation history data, and detects that the specific operator has performed the second operation in the past, the second operation by the specific operator on the operation restriction condition data. Is set to a condition for permitting the first operation for the operator identified by the identification device, the device is set to the permitted state for the first operation, and the second by the specific operator is set. Is set to a condition for prohibiting the first operation for the operator identified by the identification device, the device may be set to a prohibited state for the first operation. Since the specific processing in this case is the same as that of the first embodiment, description thereof is omitted.

Hereinafter, modifications of the above embodiment will be described.
In the above embodiment, the device state setting unit 34, the operator data changing unit 36, and the message output unit 38 shown in FIG. 1 may be realized by using dedicated hardware, or may be realized by a computer program. Good.

In the above-described embodiment, the operator data changing unit 36 referred to when the operator data changing unit 36 changes the operator data is given in a table format as shown in FIG. The condition for changing the operator data is not limited to the table format. For example, when the function of the operator data changing unit 36 is realized by a program, the operator data changing condition may be programmed in an if-then format. Changing the operator data with reference to the change condition of the operator data by the operator data changing unit 36 is equivalent to the following expression as shown in the second embodiment. That is, the operator data changing unit 36 prohibits / permits a predetermined operation of a predetermined operator in the operator data on condition that an operation specified by the operation ID input to the device management unit 30 is performed. Change the setting.
In the second embodiment, the operation limiting condition data is stored in the storage unit. As described above, the operation limiting condition data can be stored in the program in an if-then format. In that case, the if-then program module including the operation limiting condition data corresponds to a storage unit (storage device) that stores the operation limiting condition data.

  In the above embodiment, in step S100 shown in FIG. 3, the device ID is input to the device management unit 30 together with the employee ID and the operation ID. When the device that is the target of the operation specified by the operation ID is uniquely associated by the operation ID, it is not necessary to input the device ID in step S100.

  In the above embodiment, a non-permission command is output in step S110 shown in FIG. If each device is set to a prohibited state in which no operation is accepted by default, the process of step S110 for outputting a non-permission command is not necessary. Even when each device is set to a prohibited state in which an operation is not accepted by default and the process of step S110 for outputting a disallowed command is not necessary, the device state setting unit 34 (see FIG. 1) indicates that “the identification device has identified. This is equivalent to “when the operator matches the non-permitted operator who does not permit the first operation on the operator data”, the device is set in a prohibited state with respect to the first operation ”.

Specific examples of the present invention have been described in detail above, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above.
Further, the technical elements described in the present specification or drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings can achieve a plurality of purposes at the same time, and has technical utility by achieving one of the purposes.

It is a block diagram of an amusement hall. It is a figure which shows an example of premium data. It is a flowchart figure of the process which an apparatus management part performs. It is a figure which shows the specific example of operator data (1). It is a figure which shows the content of the operator data change condition table. It is a figure which shows the content of operator group data. It is a figure which shows the specific example of operator data (2). It is a flowchart figure of the process which the apparatus management part of 2nd Example performs.

Explanation of symbols

10: Hall computer 12: Game table 14: Counting device 16: POS terminal 18: POS host 20: Card unit 24: Game data storage unit 26: Premium data storage unit 30: Device management unit 32: Input / output unit 34: Device state Setting unit 36: operator data changing unit 38: message output unit 40: operation history storage unit 42: operator data storage units 50a, 50b, 50c, 50d, 50e: identification devices 52a, 52b, 52c, 52d: operation panel 54a , 54b, 54c, 54d: display device 56: printer 58: reader 100: game hall

Claims (10)

A device management device that allows a device that can be set to either a permitted state for accepting a specific operation performed by an operator identified by the identification device and a prohibited state for not accepting a specific operation,
In response to past operations performed by the identified operator, a device state setting unit that causes the device to be set to either a permitted state or a prohibited state for a specific operation performed by the operator,
A device management apparatus comprising: An operator data storage device for storing operator data for setting whether to permit the first operation on the device for each operator;
An operator data changing unit that changes the setting on the operator data of the identified operator when the operator identified by the identification device performs a second operation;
The device state setting unit sets the device to a permitted state for the first operation when the operator identified by the identification device matches the permitted operator permitted for the first operation on the operator data. In addition, when the operator identified by the identification device matches the non-permitted operator who does not permit the first operation on the operator data, the device is set to be prohibited from the first operation. The device management apparatus according to claim 1, wherein the device management apparatus is a device. An operation history storage device for storing operation history data for specifying an operator and an operation performed by the operator;
An operation restriction condition data storage device for storing operation restriction condition data for setting whether or not the first operation is prohibited for the operator when the operator performs the second operation;
When the device state setting unit detects that the operator identified by the identification device has performed the second operation in the past by referring to the operation history data, the device state setting unit displays the second past in the operation restriction condition data. When the operation is set as a condition for permitting the first operation, the device is set in a permission state for the first operation, and the second operation in the past is set as a condition for prohibiting the first operation. The device management apparatus according to claim 1, wherein when set, the device is set to a prohibited state with respect to the first operation. An inquiry message as to whether or not to accept the first operation performed by the identified operator when the device state setting unit sets the device in a prohibited state with respect to the first operation performed by the identified operator. An output unit for presenting the identified operator;
The device state setting unit resets the device to a permitted state for the first operation when the identified operator inputs an instruction to accept the first operation. The device management apparatus according to 2 or 3.   The apparatus according to claim 4, further comprising a storage device that stores the identified operator in association with the first operation when the apparatus state setting unit resets the apparatus to a permitted state. Management device. The operator data storage device stores data of operator groups associated with a predetermined operator,
The operator data changing unit is an operation associated with the predetermined operator on the operator data when the identified operator is the predetermined operator and the operator performs the second operation. The device management apparatus according to claim 2, wherein settings of operators belonging to the operator group are changed. The operation restriction condition data includes data for setting whether or not the first operation is prohibited for other specific operators when the specific operator performs the second operation.
The device state setting unit refers to the operation history data, and when it is detected that a specific operator has performed the second operation in the past, the device state setting unit performs the second operation by the specific operator on the operation restriction condition data. However, when the condition for permitting the first operation for the operator identified by the identification device is set, the device is set to the permitted state for the first operation, and the second operation by the specific operator is performed. 4. The device management according to claim 3, wherein when the condition for prohibiting the first operation for the operator identified by the identification device is set, the device is set in a prohibited state for the first operation. apparatus.   The device management apparatus according to claim 1, wherein each of the device management apparatuses is connected to a plurality of devices each including an identification device via a network. A device management program for setting a state for a device that can be set to either a permitted state for accepting a specific operation performed by an operator identified by the identification device and a prohibited state for not accepting a specific operation,
For each operator, a computer that can access operator data for setting whether to permit the first operation on the device,
An operator data changing function for changing the setting on the operator data of the identified operator when the operator identified by the identification device performs the second operation;
When the operator identified by the identification device matches the permitted operator permitted for the first operation on the operator data, the device is set to the permitted state for the first operation, and the identification device A device state setting function for setting the device to a prohibited state for the first operation when the identified operator matches the disallowed operator who does not permit the first operation on the operator data;
Device management program for realizing. A device management program for setting a state for a device that can be set to either a permitted state for accepting a specific operation performed by an operator identified by the identification device and a prohibited state for not accepting a specific operation,
Operation history data for specifying the operator and the operation performed by the operator, and an operation for setting whether or not the first operation is prohibited for the operator when the operator performs the second operation To a computer that can access the restriction data,
By referring to the operation history data, when it is detected that the operator identified by the identification device has performed the second operation in the past, the past second operation is the first on the operation restriction condition data. When the condition for permitting the operation is set, the device is set to the permitted state for the first operation, and when the second operation in the past is set to the condition for prohibiting the first operation, A device management program for realizing a device state setting function for setting a device in a prohibited state for the first operation.

Images