JP6370731B2 - Deposit / withdrawal system - Google Patents

Description

  The present invention relates to a deposit / withdrawal system.

  In recent years, improvement in customer satisfaction and optimization of device operation have been regarded as important at sales outlets of financial institutions such as banks. In particular, a recycling cashier that is a cash handling machine (hereinafter simply referred to as “cash machine”) capable of depositing / withdrawing cash at a business store has proposed a technique for improving the efficiency of deposit / withdrawal operations. For example, if there is a small bundle withdrawal request from the terminal, it is determined whether the withdrawal that satisfies the request is possible and whether the cash handling device is located adjacent to the terminal that transmitted the request. In this case, there is a control device that instructs the cash handling device to withdraw a small bundle. In addition, when the second business process is executed while one branch terminal is executing the first business process, the transaction manager switches the client manager to the client manager corresponding to the second business process. There is a store server.

JP 2007-188254 A JP 2003-208521 A

  However, in the above-described recycling cashier, because of mechanical limitations, it is not possible to simultaneously perform deposit processing on the lobby side in the sales store and withdrawal processing on the office side, so the employee gives priority to any processing. And priorities were determined manually. For this reason, it has been difficult for the recycle cashier to appropriately switch (optimize) the deposit processing and the withdrawal processing in consideration of the usage situation that changes with time. For example, all of the above-described techniques are intended to improve the efficiency of business processing, but do not consider the past usage status of the recycle cashier in real time. This has been a factor that hinders the efficiency of cash management at sales offices.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a deposit / withdrawal system capable of improving the efficiency of cash management at a business store.

  In order to solve the above-described problems and achieve the object, the deposit / withdrawal system disclosed in the present application is, in one aspect, a cash machine and a server device that stores business information related to business processing performed by the cash machine, And an information processing apparatus. The information processing apparatus includes: an extraction unit that extracts business information related to past operations of the cash machine operator from the business information acquired from the server device; and the business information extracted by the extraction unit And determining a process to be prioritized out of a deposit process and a withdrawal process by the cash machine based on a result of the estimation. .

  According to one aspect of the deposit / withdrawal system disclosed in the present application, it is possible to improve the efficiency of cash management at a business store.

FIG. 1 is a diagram showing a configuration of a deposit / withdrawal system. FIG. 2 is a diagram illustrating an example of business information storage in the simulation DB. FIG. 3A is a diagram illustrating an example of storing resource information in the simulation DB. FIG. 3B is a diagram illustrating an example of storing resource information of another apparatus in the simulation DB. FIG. 4 is a flowchart for explaining a processing flow until calculation results of business evaluation are accumulated in the DB. FIG. 5A is a diagram illustrating a configuration example of resource usage information. FIG. 5B is a diagram illustrating a configuration example of usage information for business evaluation. FIG. 6 is a flowchart for explaining the priority order determination process. FIG. 7 is a flowchart for explaining the operation simulation process. FIG. 8 is a diagram illustrating an example of the congestion situation displayed as a result of the operation simulation process execution. FIG. 9 is a flowchart for explaining processing for displaying the skill map of the operator. FIG. 10A is a diagram illustrating a data storage example of the evaluation DB. FIG. 10B is a diagram illustrating a data storage example of the reading range DB. FIG. 11 is a diagram illustrating a data storage example of the definition file. FIG. 12 is a flowchart for explaining a process executed when a task is completed.

  Hereinafter, embodiments of the deposit / withdrawal system disclosed in the present application will be described in detail with reference to the drawings. The deposit / withdrawal system disclosed in the present application is not limited by the following embodiments.

  First, the configuration of a deposit / withdrawal system according to an embodiment disclosed in the present application will be described. FIG. 1 is a diagram showing a configuration of the deposit / withdrawal system 1. As shown in FIG. 1, in the deposit / withdrawal system 1, a store information DB (DataBase) 10, a ranking operation machine 20, a recycle cashier 30, cash machines IO (Input Output) 40 and 50, and an extraction PC (Personal Computer) 60. Are connected via the network N. The store information DB 10 collects various types of store information. The ranking controller 20 determines the order of customers. The recycle cashier 30 and the cash machine IOs 40 and 50 are devices used by bankers and customers for depositing and withdrawing cash and the like.

  The extraction PC 60 is an apparatus that extracts an operation simulation, and includes a simulation definition file 61, a data mining unit 62, a simulation unit 63, and a result display unit 64. Each of these components is connected so that signals and data can be input and output in one direction or in both directions. The simulation definition file 61 has a simulation DB 611 described later. The data mining unit 62 searches for desired data from the business DB in accordance with the simulation definition file 61. The simulation unit 63 executes a calculation according to the simulation definition file 61 from the data searched from the business DB. The result display unit 64 displays the calculation result.

  Each cash machine of the recycle cashier 30 and the cash machine IO 40, 50 is executed based on the employee ID or customer ID. When a bank clerk or customer selects a business, each cash machine executes business processing. When the employee or customer completes the business, for example, the information shown in FIGS. 2 to 3B is added to the simulation DB 611.

  FIG. 2 is a diagram illustrating an example of business information storage in the simulation DB 611. As shown in FIG. 2, in the simulation DB 611a, operator cooperation (worker name, resource name, device ID, start time, completion time, operation response time, Various information such as device processing time, recovery response ID, recovery response time and the like are stored in an updatable manner. For example, “business A” and “business B” are stored as business names, and “name of receipt”, “number of withdrawals”, “customer receipt”, “receipt receipt”, “packaging” as resource names, for example. “Paper” and “sealed paper” are stored.

  In FIG. 2, the most significant bit of the operator ID represents “0 = bank” and “1 = customer”. Moreover, since the record of item number 2 records “3” in the operator cooperation, the customer with the customer ID “10000002” requests the employee with the employee ID “00000002” for the job B. Indicates. In the device ID, of the 7 digits, the upper 3 digits represent the device type, and the lower 4 digits represent the device number. For example, although item number 1 and item number 6 have the same device type, but the device number is different, there are at least two identical devices (cash machines) in the business store. In addition, “20150110151005” recorded at the start time and “20150110151325” recorded at the completion time have a start time of 15: 10: 5 on January 10, 2015 and a completion time of 2015 It indicates that it is 15:13:25 on January 10, 2010.

  FIG. 3A is a diagram illustrating an example of resource information storage in the simulation DB 611. FIG. 3B is a diagram illustrating an example of storing resource information of another apparatus in the simulation DB 611. As shown in FIGS. 3A and 3B, in the simulation DBs 611b and 611c, as the resource information of each device, for example, the maximum capacity, the current capacity, and the usage information include resource names (for example, a thousand-ticket cassette, a ten thousand-ticket cassette,.・ ・) Is accumulated every time. The resource information is stored in the simulation DB 611 separately for each device (cash machine) in the order of operation.

  Next, the operation will be described.

  FIG. 4 is a flowchart for explaining a processing flow until calculation results of business evaluation are accumulated in the DB. When the business is completed, the store information DB 10 on the store server side returns the storage result to each cash machine, and then sends a storage request to the extraction PC 60. In S1, the extracting PC 60 extracts information stored in the store information DB 10 from the store server and stores it in the business DB. In S <b> 2, the extraction PC 60 reads the simulation definition file 61. In S3, the extraction PC 60 searches for (mines) desired data from the business DB in accordance with the simulation definition file 61. In S4, the extraction PC 60 executes (simulates) the calculation in accordance with the simulation definition file 61 from the data searched from the business DB.

  Here, the simulation definition file 61 will be described. The simulation definition file 61 includes, for example, priority, area definition, average transaction time, average number of resources, resource usage information, and various types of business evaluation information. In the simulation definition file 61, the priority is set higher in the order of year> month> day. The area definition is set for each year, month, day, and in the case of a year, the unit areas are from January to March, from April to June, from July to September, and from October to December. In the case of a month, 1 to 10 days, 11 to 20 days, and 21 to the last day are unit areas. In the case of a day, 9 to 12 o'clock, 12 to 15 o'clock, 15 o'clock to business end time are units. It becomes an area.

  FIG. 5A is a diagram illustrating a configuration example of the resource usage information F1. As shown in FIG. 5A, a calculation formula is set for each resource usage information “1a”, “1b”, “1c”, “1d”, “2a”, and “2b”. In the calculation formula for the usage information “1a”, the number of deposits [1a] = presence / non-receipt of 1 yen × 10 + 5 yen / presence / non-existence × 10 +. × 10 + thousand-ticket presence × 10 +... + 10,000-ticket presence × 10. For example, in the case of a customer having a customer ID “10000001” of item number 1, with reference to FIG. 2, the number of deposits is 1000 of “55,000,000”. There are no other deposits and withdrawals, and in the above-mentioned number of deposits [1a], the presence / absence of 1,000 tickets is present and the presence / absence of 10,000 tickets is present. Therefore, when the above formula is applied, (10 + 10) × 1 constant + 10 constant = 30, and the number of consumed resources is calculated as “30”.

  In S5, the extraction PC 60 stores the calculation result in the resource DB.

  FIG. 5B is a diagram illustrating a configuration example of the business evaluation use information F2. As shown in FIG. 5B, a calculation formula is set for each of the usage information “business A” and “business B” for business evaluation. In FIG. 5B, the business evaluation is a five-step evaluation. When the number of business operations is a predetermined threshold (for example, 10 times) or more, the number of business operations is corrected by a predetermined correction value (for example, 5 times). Further, in the usage information for business evaluation, a ratio with respect to the average value when there is a sudden speed reduction in the business is set as a sudden change amount. Furthermore, information indicating whether the change priority is the simulation definition file 61 or the averaging is set.

  In S6, the extraction PC 60 calculates the business evaluation and accumulates the calculation result in the evaluation DB. At this time, the extraction PC 60 adds the post-change time to the reading range DB when the average speed of the operator ID and the work evaluation change and the work frequency is equal to or greater than the set value of the simulation definition file 61.

  Next, the flow up to the priority determination of the recycle cashier 30 will be described. First, the extracting PC 60 stores the customer ID and order in the simulation DB 611 in cooperation with the bank employee. Next, the extraction PC 60 assumes the business content of the customer ID from the sales office information DB 10, and when the business content of the operator ID depends on the staff work, 1 is added to the staff work of the simulation DB 611. On the other hand, when the business content of the operator ID depends on the customer business, 1 is added to the customer business in the simulation DB 611. Next, the extraction PC 60 determines the priority of the recycle cashier 30 according to the result of the addition. Specifically, the extraction PC 60 transmits a clerk priority job order to the recycle cashier 30 if the clerk job> customer job, and sends a customer priority job command to the recycle cashier 30 if the clerk job <customer job. Send to. Note that, when the banking duties = customer duties, the extraction PC 60 transmits a first-come-first-served command to the recycle cashier 30.

  Hereinafter, the priority determination process will be described in more detail with reference to FIG. FIG. 6 is a flowchart for explaining the priority order determination process.

  In S <b> 11, the completion information of the device (the ranking controller 20 or the cash machine) is notified to the extraction PC 60 via the network N. The completion information includes, for example, an operator ID, a completion notification, and device information. The simulation unit 63 of the extraction PC 60 determines whether or not the rank controller 20 has been completed (S12). When the completion of the rank controller 20 is detected (S12; Yes), the operator ID is acquired (S13). In S14, the simulation unit 63 acquires a data mining result (current simulation result data) under the usage conditions in the year region and the month region. Next, based on the data mining result, the simulation unit 63 determines whether or not there are more employee duties than customer duties (S15). If there are more employee duties (S15; Yes), 1 is assigned to the employee duties in the simulation DB 611. Are added (S16).

  In S <b> 17, the simulation unit 63 determines the magnitude relationship between the staff service and the customer service in the recycle cashier 30 from the simulation DB 611. As a result of the determination, if the employee service> the customer service is established (S17; Yes), the simulation unit 63 gives priority to the rear service, and instructs the recycle cashier 30 to give priority to the rear (S18).

  If the simulation unit 63 of the extracting PC 60 does not detect completion of the cash machine in S12 (S12; No), it acquires an operator ID (S19). In S <b> 20, the simulation unit 63 determines whether each of the tasks linked to the acquired operator ID is a clerk task or a customer task, and then whether or not the clerk task is more than the customer task. Determine whether. When there are many (S20; Yes), the simulation unit 63 subtracts 1 from the bureau work of the simulation DB 611 (S21), but when there are more customer affairs than the clerk work (S22; Yes), the simulation DB 611 1 is subtracted from the customer service (S23).

  It should be noted that after the process of S21 or S23 is completed, or when the number of customer duties is the same as the employee duties (S22; No), the process proceeds to the above-described processes after S17.

  As a result of the determination in S15, when the employee service is not more than the customer service (S15; No), the simulation unit 63 further determines whether or not the customer service is more than the customer service. ; Yes), 1 is added to the customer service of the simulation DB 611 (S25).

  It should be noted that after the process of S25 is completed, or when the number of customer duties is the same as the number of employee duties (S24; No), the process proceeds to the above-described processes after S17.

  If the employee service> customer service is not established in S17 (S17; No), the simulation unit 63 further determines whether the employee service <customer service is established (S26), and if it is established (S26; Yes) gives priority to the front work, and instructs the recycle cashier 30 to give priority to the front (S27). On the other hand, if not established (S26; No), the simulation unit 63 instructs the recycle cashier 30 to win first (S28).

  Next, the operation simulation process will be described in more detail with reference to FIG. FIG. 7 is a flowchart for explaining the operation simulation process.

  When there is a request for an operation simulation result (S31), the simulation unit 63 of the extraction PC 60 reads the above-described simulation definition file 61 (S32).

  In S33, the simulation unit 63 determines whether or not the search request specifies a date. When the search request specifies the day (S33; Yes), the simulation unit 63 calculates the average value of the operator IDs under the usage conditions in the year region and the month region (S34).

  Regarding the average value calculation method, the simulation unit 63 performs averaging in the start time, completion time, and year / month / day regions of the apparatus ID of the simulation DB 611. The average transaction time is calculated by Σ [each ID (completion time-start time)] / Σ [each ID], and the average resource number is calculated by Σ [ID (number of resources)] / Σ [ID]. For example, in the case of a customer with customer ID “10000001”, the start time is “2015 1:10 15: 10: 5” and the completion time is “2015 1:10 15:13:25” Therefore, the transaction time is calculated as 3 minutes 20 seconds based on the completion time-start time. As the number of resources, “30” (see FIG. 5A) that has already been calculated is used. Furthermore, the year / month / day area is divided into four for the year, three for the month, and three for the day in the simulation definition file 61. Therefore, in the case of the day, 4 × 3 × 3 = 36. The timing of things is assumed. Also in the case of the month, 4 × 3 = 12 timings are assumed.

  In addition, when the customer with the customer ID “10000001” makes a transaction a plurality of times at the timing of year: 1 to 3 month, month: 1 to 10 days, day: 12 to 15 o'clock, the simulation unit 63 The average value is calculated. For example, the average transaction time of the customer with customer ID “10000001” is calculated as “3 minutes and 25 seconds” when the first time is “3 minutes and 20 seconds” and the second time is “3 minutes and 30 seconds”. The number is calculated as “35” when the first time is “30” and the second time is “40”. In S34, the simulation unit 63 similarly calculates the average value of each operator other than the customer at the timing.

  Next, the simulation unit 63 calculates the total average transaction time of the average transaction time between the customer ID “10000001” and each operator ID, and the total average resource number of the average resource number. Thereafter, the simulation unit 63 calculates the number of usable devices, and divides the total average transaction time and the total average resource number by the number of devices. For example, at the above timing, the total average transaction time is “5 minutes and 10 seconds”, the total average number of resources is “40”, the total number of uses is “30 times”, and there are two devices that can execute the job A. Assume a case. In this case, the total average transaction time is reduced to “2 minutes 35 seconds” and the total average resource count is reduced to “20” by using two devices. As a result, the simulation unit 63 can obtain, as a simulation result, information indicating that the transaction time decreases by “2 minutes 35 seconds” and the resource number decreases by “20” at intervals of the total use count “20”. it can.

  In next S35, the data mining unit 62 performs data mining on the history of the current operator, and estimates the number of transactions executed by each operator from the simulation DB 611. First, the data mining unit 62 calculates how many transactions are performed per month with the operator ID. Next, the data mining unit 62 specifies in which region of the month the transaction is performed, and calculates an average value of how many times the transaction is performed on the same day. Further, the data mining unit 62 confirms the presence / absence of a transaction executed on the same day based on the past history of the operator.

  In S36, the simulation unit 63 calculates an average value of values obtained by subtracting the number of times B calculated in S35 from the average value A calculated in S34. At this time, if there is an operator whose number of transactions exceeds the average value of how many times the transaction is performed on the same day, the simulation unit 63 calculates only the operator ID of the operator in S34. The average value calculated in S36 is subtracted from the average value. As a result, only the ID of the operator (for example, customer ID “10000001”) is omitted from the defined area, and the simulation is executed.

  In S37, the result display unit 64 displays the average value of the AB calculated in S36.

  In S33, when the search request does not specify a day (S33; No), the simulation unit 63 calculates an average value of the operator IDs under the usage conditions in the year region ( S38). In S39, the result display unit 64 displays the average value calculated in S38.

  By executing the operation simulation process described above, the operation side can check the congestion status. FIG. 8 is a diagram illustrating an example of the congestion situation displayed as a result of the operation simulation process execution. As shown in FIG. 8, the screen that can be visually recognized by the operator is divided into four stages (waiting for one person, waiting for 2-3 persons, waiting for 4-5 persons, 6 or more persons) in each time zone. Identification is displayed. In FIG. 8, the filled portion represents the occupied time zone of each device (recycle cashier 30, cash machine IO 40, 50).

  Regarding the resources, since there is a possibility of being used 30 times in the area shown in FIG. 8, as a whole, the number of resources “20” × 30 times = 600 may be used. However, since there are only 500 customer receipts, replacement is required. Since the number of resources used is accumulated in the simulation DB 611 at the completion of the job, it is calculated by the operation simulation process.

  Next, processing for displaying the skill map of the operator will be described. In the bank, the deposit / withdrawal system 1 can evaluate the operation skill of each operator based on the speed at which the business is performed. FIG. 9 is a flowchart for explaining processing for displaying the skill map of the operator.

  When the skill map is requested (S41), the simulation unit 63 acquires the operation ID input by the operator (S42). The request is an averaging request or a request in a definition file. Next, the simulation unit 63 reads the simulation definition file 61 (S43), and reads the date and time that is the reading range of the operator ID based on the evaluation DB (S44). FIG. 10A is a diagram illustrating a data storage example of the evaluation DBG1. As shown in FIG. 10A, the evaluation DBG1 stores the evaluation and number of times for each business (for example, business A and B) for each operator ID. The evaluation is, for example, a five-level evaluation, but is not limited to this. Similarly, FIG. 10B is a diagram illustrating a data storage example of the reading range DBG2. As shown in FIG. 10B, the reading range DBG2 stores the evaluation change date and time and average speed for each operation (for example, operations A and B) for each operator ID.

  In S <b> 45, the simulation unit 63 averages the tasks that occurred within the reading range of the operator ID. For example, when the number of operations is less than 10, the simulation unit 63 performs averaging for the number of operations. On the other hand, when the number of operations is 10 or more and the number of operations within the reading range is 5 or less, the simulation unit 63 adds the operation response time of the operator and is sufficient for 5 times. The current average value is added as many times as possible, and divided by the number of corrections. For example, assuming that the operator with ID 10000001 performs work twice from the evaluation change date and time, the first operation response time is “65 seconds” and the second operation response time is “70 seconds”. Since there are no subsequent times, 60 seconds, which is the average value of the reading range DBG2, is added three times for the remaining three times. Therefore, the average speed is calculated as (65 + 70 + 60 × 3) / 5 = 63 seconds.

  On the other hand, if the number of operations is 10 or more and the number of operations in the reading range exceeds 5, the simulation unit 63 sets the operation response time for the current number of operations to the average speed of the evaluation change date and time. And divide by the current number of operations +1. For example, assuming that the operator with ID 10000001 performs six tasks from the evaluation change date and time, the first to sixth operation response times are “65 seconds”, “70 seconds”, “70 seconds”, and “40 seconds”, respectively. “30 seconds”, “50 seconds”. Therefore, the average speed is calculated as (evaluation change date and time 60 + 65 + 70 + 70 + 40 + 30 + 50) / (6 + 1) = 55 seconds.

  In S46, the simulation unit 63 determines whether the evaluation result having the averaging request is an evaluation result from the whole average or an evaluation result defined in a definition file described later. As a result of the determination, if the evaluation result having the averaging request is an evaluation result from the overall average (S46; Yes), the simulation unit 63 averages the operations of each operator ID, for example, an average value The sudden change is excluded by not reading the speed which has increased by 70% or more. And the simulation part 63 averages the operation | work of each operator ID from which this sudden change was excluded (S47).

  Thereafter, the simulation unit 63 compares the average speed of the operator with the overall average speed (S48), and determines the stage evaluation (S49). For example, if the overall average speed is “60” and a five-stage evaluation is performed, 120 or more is one stage, 120 to 90 is two stages, 90 to 60 is three stages, 60 to 30 is four stages, and 30 or less is five. It becomes a stage. Therefore, the evaluation of the operator whose average speed is “68” is determined as “3”. In S50, the result display unit 64 displays the result of the stage evaluation determined in S49 in association with the operator, average speed, and business. Thereby, the operator can grasp | ascertain easily and quickly how much skill each operator has in order to perform each operation | work.

  As a result of the determination in S46, if the evaluation result having the averaging request is the evaluation result defined in the definition file (S46; No), the simulation unit 63 sets the average speed of the operator in the definition file. Compared with the set value (S51), the stage evaluation is determined (S52). FIG. 11 is a diagram illustrating a data storage example of the definition file G3. As shown in FIG. 11, the definition file G3 stores the evaluation and the number of times for each job (for example, jobs A and B) for each operator ID. The evaluation is, for example, a five-level evaluation, but is not limited to this.

  For example, in the definition file G3, a five-level evaluation is set such that 130 or more is one stage, 130 to 100 is two stages, 100 to 70 is three stages, 70 to 20 is four stages, and 20 or less is five stages. The evaluation of the operator whose average speed is “68” is determined as “4”. After the evaluation is determined, the process proceeds to S50.

  FIG. 12 is a flowchart for explaining a process executed when a task is completed. First, the simulation unit 63 reads the date and time that is within the reading range of the operator ID (S61), and averages the tasks that occurred within the reading range of the operator ID (S62). In S63, the simulation unit 63 determines whether or not to prioritize averaging when determining whether or not there is an evaluation change. As a result of the determination, when priority is given to averaging (S63; Yes), the simulation unit 63 averages the operations of the operator IDs, and suddenly, for example, does not read a speed increasing by 70% or more of the average value. Excluding changes. And the simulation part 63 averages the operation | work of each operator ID from which this sudden change was excluded (S64). Thereafter, the simulation unit 63 compares the average speed of the operator with the overall average speed (S65), and determines the stage evaluation E1 (S66). In S67, the simulation unit 63 acquires the operator's evaluation E2 from the evaluation DBG1.

  In S68, the simulation unit 63 compares the stage evaluation E1 determined in S66 with the evaluation E2 acquired in S67, and determines whether there is a change. If there is a change as a result of the determination (S68; Yes), a change has occurred in the evaluation for the operator, so the simulation unit 63 sets the corresponding job (for example, job A) in the read range DBG2 as an item. The evaluation change date and time and the average speed are written (S69). When there is no change (S68; No), the process of S69 is omitted.

  If the result of determination in S63 is that priority is not given to averaging (S63; No), the simulation unit 63 compares the average speed of the operator with the setting value in the definition file (S70), and determines the stage evaluation E1. (S71). In S72, the simulation unit 63 acquires the operator's evaluation E2 from the evaluation DBG1. Thereafter, the process proceeds to the above-described processing after S68.

  As described above, the deposit / withdrawal system 1 includes the recycle cashier 30, the cash machine IOs 40, 50, the store information DB 10 that stores business information (original data) related to the business processing performed by these cash machines, and the extraction PC60. The extraction PC 60 includes a data mining unit 62 and a simulation unit 63. The data mining unit 62 extracts (mines) business information regarding the past business of the current operator of the cash machine from the business information acquired from the store information DB 10. The simulation unit 63 estimates the transaction time (cash machine occupation time) of the operator using the business information extracted by the data mining unit 62, and based on the result of the estimation, the lobby side of the cash machine Of the deposit process and the withdrawal process on the office side, the process to be prioritized is automatically determined. As a result, among the lobby side where the deposit process is performed and the office side where the withdrawal process is performed, the transaction with the longer transaction time or waiting time, that is, the crowded transaction is always given priority. As a result, it is possible to switch appropriately according to the usage status of the cash machine that changes with time, and it is possible to improve the efficiency of cash management at the business store.

  In the deposit / withdrawal system 1, the transaction time may be a time obtained by adding an operation time required for the operation of the cash machine by the operator and a processing time required for a business process by the cash machine. The operation time is the time obtained by subtracting the work start time (ID card stamping time) from the operation completion time, and the processing time is the operation completion time subtracted from the work completion time (standby screen transition time). It is good also as what is obtained time.

  In the deposit / withdrawal system 1, the data mining unit 62 extracts business information related to the business of the past year and month corresponding to the date and time of the current operation by the operator of the cash machine, and the simulation unit 63 The transaction time of the operator may be estimated using the business information extracted by the mining unit 62. Furthermore, the simulation unit 63 calculates an average value of the operator's past transaction time using the business information extracted by the data mining unit 62, and based on the result of the calculation, the operator's transaction time It is good also as what estimates (cash machine occupation time). Alternatively, the simulation unit 63 uses the business information extracted by the data mining unit 62 to estimate the waiting time until the operator's transaction together with the operator's transaction time (cash machine occupation time). Based on the result of the estimation, it may be determined which process is given priority among the deposit process and the withdrawal process by the cash machine.

  In the above-described embodiment, a recycle cashier is exemplified as a cash machine. However, the present invention is not limited thereto, and a cashier, a cash dispenser, an ATM (Automated Teller Machine), or the like may be used. Moreover, in the said Example, although typical deposit processing and withdrawal processing in the bank transaction business were illustrated as business processing which a cash machine handles, it is not restricted to these, Re-examination processing etc. may be sufficient. Further, in the above embodiment, customer receipts, employee receipts, wrapping paper such as bar metal, and sealing paper such as bill bundles are exemplified as resources, but not limited thereto, sealing tape, receipt printing ink, etc. It may be a consumable item.

  In addition, the average value of the operator's past transaction time does not necessarily have to be an average value in units of one year, and an average value in units of 2 to 5 years, or in half, quarter, month, and week units is simulated. The unit 63 may calculate the value. In addition, as the area definition of the simulation definition file, 3 to 4 unit areas are set for each year, month, and day, but the present invention is not limited to this, and an arbitrary unit area may be set. Furthermore, with regard to deposit processing and withdrawal processing, in the above embodiment, cash deposited by the customer on the lobby side is withdrawn by the bank employee on the office side. However, the customer performs the withdrawal processing or deposits. The employee may perform the process.

  Each component of the deposit / withdrawal system 1 does not necessarily have to be physically configured as illustrated. That is, the specific mode of distribution / integration of each device is not limited to the illustrated one, and all or a part thereof is functionally or physically distributed in an arbitrary unit according to various loads or usage conditions. -It can also be integrated and configured. For example, the data mining unit 62 and the simulation unit 63, or the simulation unit 63 and the result display unit 64 may be integrated as one component. On the contrary, the simulation unit 63 may be divided into a part for executing the priority order determination process, a part for executing the operation simulation process, and a part for executing the skill map display process of the operator. Further, the simulation DB 611 may be connected as an external device of the extraction PC 60 via a cable or a network.

1 Deposit / withdrawal system 10 Store information DB
20 rank operation machine 30 Recycle cashier 40, 50 Cash machine IO
60 PC for extraction
61 simulation definition file 62 data mining unit 63 simulation unit 64 result display unit 611, 611a, 611b, 611c simulation DB
F1 Resource usage information F2 Business evaluation usage information G1 Evaluation DB
G2 Reading range DB
G3 definition file

Claims (1)

A recycling cashier having a front surface and a rear surface ;
A server device that stores business information related to business processing executed by the recycle cashier ;
Possess and an information processing apparatus, the,
The information processing apparatus includes:
From among the operational information acquired from the server device, it extracts the business information about past operations of the operator of the recycling cashier,
By using the extracted out to the business information, business in which the operator performs it is determined whether the employees work or is the customer business,
Based on the comparison result between the number of customer operations and the number of employee operations, it is determined which of the operations on the front and the operations on the rear of the recycling cashier should be given priority .
Deposit / withdrawal system.

Images