JP2002032569A - Method for deciding cash delivery schedule, cash delivery schedule generating device using the method, and recording medium for generating cash delivery schedule - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make out a highly effective schedule in regard to both cash delivery work and fund management. SOLUTION: A host computer 2 fetches the data showing the money receiving/dispensing state of every device by communicating the ATMs 3 which are installed at the outside of general stores and preserves these data in a floppy (registered trademark) disk 4 as the inference data. A cash delivery schedule production device 1 has the delivery conditions set previously about the installed position, delivery capability, etc., of every ATM 3, infers the money receiving/ dispensing state of every ATM 3 in a prescribed future period by means of the inference data and then produces a cash delivery schedule of every ATM 3 from the inference results and delivery conditions.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of determining a delivery schedule for delivering cash to a plurality of automatic transaction devices scattered within a predetermined area, and each automatic transaction device using this method. And a recording medium on which a program for creating a delivery schedule is recorded.

[0002]

2. Description of the Related Art In recent years, banks have installed automatic transaction equipment (hereinafter abbreviated as "ATM") at appropriate places such as unmanned stores (branches) in the market, department stores, supermarkets, and convenience stores. For convenience.

[0003] The replenishment of cash to ATMs installed outside these ordinary stores is usually performed by a management company entrusted by a bank. The bank sets a cash delivery schedule according to the ATM installation position and the like, and entrusts the management device to execute the delivery operation according to the schedule.

[0004]

According to the present delivery schedule, delivery dates are allocated in such a manner that each branch office is divided into groups according to the installation location and the like, and delivery is performed to each group in order. Only the amount of cash to be delivered on each delivery day is set based on. Therefore, there are cases in which the funds become surplus and, conversely, cases in which the funds become insufficient, and it is difficult to efficiently manage the funds. Further, in the above-described schedule creation method, there is a strong tendency that the delivery schedule is patterned, so that a security problem also occurs.

[0005] By the way, ATM installed in the same store
With regard to, for the purpose of improving the efficiency of fund management, proposals have been made for each device to predict the future deposit and withdrawal state from the past deposit and withdrawal state and determine the timing and amount of cash replenishment (for example, JP-A-8-315217). However, when targeting a large number of ATMs scattered in a wide area, it is necessary to aim at not only the efficiency of fund management but also the efficiency of delivery business. For example, ATMs installed in the vicinity are delivered on the same day, or the schedule is adjusted so that the number of devices to be delivered does not exceed the processing capacity of the management company. You need to make a plan. Furthermore, for ATMs installed in department stores and supermarkets, it is necessary to determine the delivery date in consideration of conditions that do not occur in ordinary ATMs, such as holidays at the installation location. Thus, simply applying the cash replenishment method in a store does not lead to setting an appropriate delivery schedule to an ATM outside the store.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and has as its object to set a schedule so that cash can be efficiently delivered to each ATM in both the delivery business and the fund management. .

[0007]

In order to achieve the above object, according to the present invention, in a computer system, a future transaction state is inferred from data indicating a transaction state in an automatic transaction apparatus installed at each of a plurality of points. A delivery schedule to each device is determined based on the result and data indicating conditions for delivering cash to each device.

[0008] The "transaction status in the automatic transaction device"
A state of deposits and withdrawals in a past predetermined period, for example, data in which deposits and withdrawals during the period are accumulated for each day, or a difference value between a deposit and a deposit every sunrise (hereinafter, referred to as
This is called "consumption." ). Note that the data indicating the transaction state may include data at the present time. The "future transaction status" is obtained by an inference operation using the data indicating the transaction status. For example, a predicted value of a deposit / withdrawal amount or a consumption amount of each device in a predetermined future period is calculated in units of one business day. I do.

[0009] The "data indicating the conditions for distributing cash to each device" includes information on the installation location of each automatic transaction device, information on the delivery capacity, information on the amount of cash loaded in each automatic transaction device, and other information. The operating status of the installation location of the device (such as a holiday at a retail store) and conditions related to scrutiny can be raised. It is desirable that the delivery condition is set as a combination of a plurality of pieces of such information.

[0010] "Information on installation location of each automatic transaction apparatus" is indicated, for example, by dividing a delivery target area into a plurality of areas and allocating each automatic transaction apparatus to an area corresponding to the installation location. However, the data configuration is not limited to this, and any data configuration may be used as long as a geographical relationship among the devices can be derived, such as grouping the devices according to the distance between the devices.

[0011] The "information on delivery capability" is represented as delivery capability in one day and within a predetermined period (preferably, within a schedule creation target period). The delivery capacity is specifically indicated by the number of devices that can be delivered, the amount of cash that can be loaded on a delivery vehicle, and the like. The above-mentioned delivery capacity is generally specified by the number of business days of the department in charge of delivery or the management company to be entrusted, the number of persons in charge, the number of delivery vehicles, and the like. Further, instead of the number of business days, the number of delivery times determined by the contents of a contract with a bank may be applied.

The "cash loaded amount" is represented by the amount of cash loaded in the apparatus or the denomination and the number of loaded money. The “information on the amount of cash loaded in each device” includes the upper limit value or the lower limit value of the loaded amount in the device, or the reference loaded amount determined to load approximately the same amount of cash in each device.

[0013] In the "delivery schedule to each device", it is preferable to set a delivery schedule to each automatic transaction device and the amount of cash to be loaded to the device to be delivered. It is desirable that the delivery schedule be set in units of one month, but it is also possible to set a short-term schedule such as in units of two weeks or in units of ten days as needed.

According to the present invention, it is possible to determine a delivery schedule such that cash can be efficiently replenished in each automatic transaction device while considering various conditions such as an installation location of each automatic transaction device and delivery capacity. Become. In particular, if the delivery conditions always include information on the location of the automated teller machine and information on the delivery capacity, an efficient delivery route can be set, and the amount of work corresponding to the delivery capacity can be set for each delivery date. It is possible to make settings, and the work efficiency can be greatly improved.

Further, the cash delivery schedule creation device according to the present invention is a first input means for receiving input of data indicating a transaction state in each of the automatic transaction devices installed at a plurality of points, and a cash transfer to each device. Second input means for receiving input of data indicating delivery conditions, inference means for inferring a future transaction state using the data indicating the transaction state for each of the automatic transaction devices, each of which is based on the inference result and the delivery conditions. It is provided with a determination unit for determining a cash delivery schedule to the device, and an output unit for outputting electronic data of the determined cash delivery schedule.

[0016] The first input means stores data indicating a transaction state in each automatic transaction apparatus in a recording medium (FD, MO,
CD-R, etc.) to read the recorded information. That is, this means includes a drive device corresponding to the recording medium, an input interface, and the like. Further, the first input means may be configured as means for taking in data by communication from a computer that collects data indicating a transaction state in each automatic transaction apparatus. That is, the first input means includes a transmission / reception circuit (communication may be wired or wireless) for communicating with the computer and an input / output interface.

The second input means includes a user interface, a keyboard, and an input screen for inputting various delivery conditions.
It is composed of a mouse and the like. This allows the user to freely set the delivery conditions and set a delivery schedule according to the conditions. Note that the second input means can also be configured as a means for receiving a predetermined recording medium and reading data, similarly to the first input means. When this system is incorporated in a network system, the second input means can be configured as means for inputting data transmitted by communication from a predetermined device in the network.

In the apparatus having the above configuration, the inference means applies the data indicating the transaction status in each apparatus obtained by the first input means to a predetermined inference rule, for example, in a period for which a delivery schedule is created. The deposit and withdrawal amount and consumption amount of each device are calculated in one business day unit. The determining means sets a delivery schedule indicating a delivery date and a cash delivery amount for each device based on the inference result and the delivery conditions. This schedule is digitized by the output means and output to the outside. Output means, means for outputting the electronic data of the delivery schedule to a monitor, means for outputting to a printer for printing out,
It takes any form such as a means for recording on a recording medium or a means for outputting to another device by communication. The output unit may be configured by combining a plurality of these units, or may be configured so that any output format can be selected by an external setting.

Further, according to the present invention, as a recording medium for realizing the above-described system, a result of inferring a future transaction state based on data indicating a transaction state in each of the automatic transaction apparatuses installed at a plurality of points. Obtaining the data, receiving the input of data indicating the cash delivery conditions to each device, and determining the cash delivery schedule to each device based on the inference result about the future transaction state and the cash delivery conditions. And a step of outputting electronic data of the determined cash delivery schedule. The present invention provides a recording medium on which a program for executing each step is recorded.

The step of obtaining the result of inferring the transaction state is set, for example, to capture the inference result obtained by executing a separate program. If this step is set so as to be linked with the program for inference, it is possible to transfer data inside the computer, but this is not a limitation, and the inference can be performed from outside via a recording medium or a network line. It is also possible to capture the results. If the above steps are set so as to be linked to a program for inference calculation, a computer having a function of inferring the transaction state of the automatic transaction apparatus is provided with a function of creating a cash delivery schedule to the automatic transaction apparatus outside the store. This makes it possible to create a cash delivery schedule with improved efficiency in fund management and delivery operations using the existing hardware resources.

On the other hand, the step of obtaining the inference result includes the steps of accepting input of data indicating a transaction state in each device, and inferring the future transaction state of each device using the input data indicating the transaction state. It is also possible to configure so as to include In other words, in the recording medium in this case, a program for executing a series of processes from inference to creation of a schedule is recorded, and a new computer can be provided with a cash delivery schedule creation function immediately. Become.

[0022]

FIG. 1 shows an example of the configuration of a cash delivery schedule creation system according to the present invention. In the figure, reference numeral 2 denotes a bank host computer, which is connected to a plurality of ATMs 3 installed inside and outside a general store, and manages transaction processing in each device. Among the ATMs 3, those installed in branch offices outside general stores (including those installed in retail stores such as department stores and supermarkets).
Are grouped into regions of a predetermined size defined by boundaries such as cities and towns, and a management company in charge of replenishing cash is assigned to each region.

The cash delivery schedule creation device 1 (hereinafter simply referred to as "schedule creation device 1") according to this embodiment is constituted by a personal computer.
The inference data created by the host computer 2 and the setting of delivery conditions by the user are accepted, and a cash delivery schedule for each area is automatically created.

The inference data is a summary of deposits and withdrawals (or consumptions) of each ATM 3 in a past predetermined period (for example, one month last month) in units of devices and business days. The schedule creation device 1 receives the inference data created by the host computer in a form stored in the floppy disk 4, and performs an operation of reading the saved data, thereby performing a predetermined period in the future (for example, one month in the next month). ), An inference operation is performed on the state of the available money of each ATM 3, and a cash delivery schedule to each ATM 3 is created based on the inference result and delivery conditions set in advance (details will be described later).

The created cash delivery schedule is output to the printer 5 in an electronic data format and printed on a paper medium as a schedule table in a format described later. Further, the electronic data of the cash delivery schedule (hereinafter, referred to as “schedule data”) can be stored on a floppy disk or transmitted to a computer on the management company side by communication as necessary.

Instead of the configuration shown in FIG. 1, it is also possible to connect the schedule creation device 1 and the host computer 2 via a line, and take in the inference data by communication.
Alternatively, each ATM 3 may be directly connected to the schedule creation device 1 via a line to transmit inference data.
After performing the inference calculation by another device, the result is transmitted to a schedule creation device 1 by a floppy disk or communication.
May be taken in.

FIG. 2 shows a hardware configuration of the schedule creation device 1. This device includes a CPU 6 which is a control subject.
In addition to the ROM 7 and the RAM 8, a hard disk drive 9, a floppy disk drive 10, and a CD-ROM
It has a configuration in which a ROM drive 11, an input unit 12, an output unit 13, and the like are connected. The input unit 12 includes a keyboard,
The output unit 13 includes a mouse, a printer, and an interface to them. However, when this device is connected to another computer via a network line, the network line and the transmission / reception circuit are included in the input unit and the output unit.

The hard disk device 9 stores an inference value database 16, a setting condition database 17, a delivery schedule database 18, and the like, in addition to the inference calculation program 14 and the schedule creation program 15. Each database is empty at the initial stage. These programs and databases are
It is installed in the hard disk device 9 by an installation operation from a recording medium such as a D-ROM. However, as for the inference calculation program 14 and the inference value database 16, existing software is used, and the schedule creation program 15, the setting condition database 17, and the delivery schedule database 18 are added by using a new installation recording medium. You may do so.

The inference calculation program 14 includes inference rules (such as fuzzy inference membership functions) for calculating future deposits and withdrawals of each ATM 3 from the inference data. The CPU 6 infers the future deposit and withdrawal amount of each ATM 3 for each business day based on the program and the inference rules, and stores the inference result in the inference value database 16. Note that this type of inference operation is described in
Since it is known as described in JP-A-315217, detailed description is omitted here.

The schedule creating program 15 includes a program for setting the various delivery conditions, a program for creating a cash delivery schedule, and a program for selecting one of these two processes. And a program for setting a startup screen.

The delivery conditions are set via a user interface set on the monitor screen, and the set conditions are stored in the set condition database 17. In this embodiment, as the delivery conditions, in addition to the geographical conditions, the conditions relating to the processing capacity of the management company, the special holidays, information relating to the scrutiny of each ATM 3, information relating to the amount charged to each ATM 3, etc. I have.

The above-mentioned geographical condition is a relationship between installation locations between branch offices, and more specifically, a region for which a schedule is created is subdivided into a plurality of areas, and the positional relationship between the areas is stored. At the same time, data is created by grouping each branch office by area.

The conditions regarding the processing capacity of the management company are as follows: the number of ATMs that can be delivered per day (hereinafter referred to as “the number of deliverables”).
That. ) Or the number of delivery days per month. 1
The number of deliverable vehicles per day is determined by the number of delivery staff on the management company side, the number of vehicles for delivery, and the like. Further, the number of days of the delivery date is usually determined by the business day of the management company, but may be set to “day in month” depending on the contract with the bank.

The “special holiday” is a condition relating to a branch office installed in a retail store such as a department store or a supermarket, and refers to a unique holiday of the retail store at the installation location.
"Scrutiny" is a process of counting the amount of money remaining in the ATM 3 and collating the amount of money paid in and out, and generally employs a method of extracting each cartridge and replacing it with a new cash cartridge. The conditions related to the scrutiny include information on the number of scrutinys per month and intervals between scrutinys (how many days a scrutiny is performed). At the time of close inspection, more cash than usual is loaded to prevent running out of funds, so the extra cash amount (margin) is also set as a delivery condition.

The "load amount" indicates the amount or number of cash that can be loaded into the body of the ATM 3 for each denomination, and the delivery condition includes an upper limit value or a lower limit value of the load amount for each model. (The lower limit in this case is a minimum cash amount that does not hinder the operation of the ATM 3.) or a standard loading amount derived from past deposits and withdrawals. In this embodiment, among the above delivery conditions, the special holiday is likely to be changed every month, so that the setting is made before the creation of the cash delivery schedule.

FIG. 3 shows a specific example of the start screen.
A selection button 19 for moving to a delivery condition setting screen,
Selection button 2 for proceeding with schedule creation
0, a selection button 21 for terminating the application is formed. Further, in the center of the screen, an input box 22 for inputting a target month for schedule creation, an input box 23 for specifying a storage location of the created schedule data, a selection button 24, and a result of selecting the storage location are determined. Button 25 for performing the operation.

FIG. 4 shows a processing procedure (ST1 to ST6) when the process proceeds from the start screen to creation of a cash delivery schedule. First, when the start screen is displayed in ST1, the user sets the floppy disk 4 on which the inference data is recorded, specifies the storage location of schedule data, and further presses the selection button 20 for the schedule creation processing. Manipulate. By this operation, ST2 becomes "YES" and the process proceeds to ST3, and the above-described specific holiday setting processing is performed.

FIG. 5 shows an example of a special holiday setting screen. This screen is called by operating the selection button 20 for creating a schedule on the start screen, and displays a list of the branch offices installed in the retail store among the branch offices belonging to the processing target area. , A calendar 26 for the month to be processed is displayed. The user selects a branch office that requires setting from the list display,
A closed day of the selected branch office is set using the calendar 26. In this screen, a registration button 27 for confirming the setting of the special holiday, a switching button 2 for moving to a setting screen for adding a branch office requiring the setting of the special holiday,
8, a confirm button 29 for proceeding to the next processing, a delete button 30 for deleting any branch office in the list display,
A cancel button 31 for clearing the setting screen and returning to the start screen is set.

Returning to FIG. 4, when the setting of the special holiday is completed, in the next ST4, the arithmetic processing using the inference rule is performed while the inference data of the floppy disk 4 is read out, and the processing in the processing target month is performed. The deposit / withdrawal state of each ATM 3 is determined. In this inference calculation, an adjustment is made on the ATM 3 in the branch office on which the special holiday is set so that the special holiday is not set as the calculation target.

When the inference process is completed, the process proceeds to ST5, where schedule data is created based on the inferred values of deposits and withdrawals accumulated in the inferred value database 16 by the inference and the delivery conditions in the setting condition database 17. The created schedule data is output to the storage location specified on the startup screen (the delivery schedule database 18 if the initial state is maintained). Further ST6
The schedule data is edited into a tabular form as shown in FIG. 14 by a user's output instruction operation, and is output to a monitor or a printer.

FIG. 6 shows a processing flow (ST11 to ST18) in the schedule creation processing in ST5. In the following description, first, a rough flow of the schedule creation processing will be described with reference to FIG. 6, and then, with reference to FIG.
Details of each process will be described. In the flowcharts shown in FIG. 7 and subsequent figures, each step is indicated as “st” and is sequentially numbered. In the following description, ATM3
Is called an “apparatus”.

In FIG. 6, first, in the first ST11, the first delivery date to each branch office is provisionally determined, and then the next ST1 is executed.
In step 2, the provisionally determined delivery date is adjusted to make the final decision. This adjustment is performed based on the geographical conditions and the number of deliverable vehicles per day, which will be described later in detail.

In the next ST13, the number of deliverable units for one month is calculated based on the number of deliverable units in one day and the number of delivery days in one month. In ST14, the number of deliverable units in one month is calculated according to the number of deliverable units. The delivery date for the second and subsequent delivery is temporarily determined. Further, in the next ST15, the provisionally determined result is adjusted based on the geographical conditions and the number of deliverable vehicles per day, and the delivery date to each branch office is finally determined.

Next, in ST16, a scrutiny date is determined from the determined delivery dates, and in the subsequent ST17, a loading amount for each device is set according to the settings of the delivery date and the scrutiny date. Finally, schedule data that summarizes the delivery date and cash delivery amount for each branch is created and output to the delivery schedule database 18 or a designated storage location (ST18).

FIG. 7 shows a detailed procedure of ST11 in FIG. 6, that is, the first provisional date determining process. In this process, the processes of st1 to st7 are executed for each branch office.
First, at st1, the date of the last delivery date in the previously created schedule and the amount of cash loaded into the device on that delivery date (hereinafter referred to as the "load amount") are read. As shown in FIG. 14, the actual loaded amount is represented as the face value or the number of loaded bills for each bill type (10,000-yen bill, 1,000-yen bill, etc.). To indicate the amount of all cash loaded.

In the next st2, the inference value of the consumption amount on the last delivery date of the previous schedule is read from the inference value database 16. And in st3,4,
The amount charged to the apparatus is set to the initial value of the remaining amount P, and the remaining amount after the cash corresponding to the inferred value Q is subtracted from the remaining amount P is obtained. Hereinafter, in the loop of st4 to st6, the remaining amount P is updated by sequentially reading the inferred values from the last delivery date of the previous schedule and updating the remaining amount P.
Is determined to be zero, and that day is provisionally determined as a delivery date in the next st7. When a plurality of devices are installed in the branch office, the inferred values of the loading amount and the consumption amount are each a cumulative value of the amounts obtained for each device.

When the first delivery date of one branch office is determined in this way, the processing target is moved to the next branch office in st9, and the processing is performed in the same procedure. When the delivery dates are provisionally determined for all the branch offices, st8 becomes "YES" and the process ends.

FIG. 8 is a detailed procedure of the delivery date determination process shown in ST12 of FIG. In this procedure, devices to be delivered are determined every day in order from the first day of the month for which a schedule is to be created (for example, July 1). First, in st10, it is checked whether or not there is a branch office whose current day is set as a delivery date. I do. If this day is a day on which no delivery is scheduled, such as a holiday, st10 is “NO”, the process returns to st10 via st23 and st24, and the next day is processed.

If there is a scheduled delivery on the day, the process proceeds from st10 to st11, where the number of deliverable units per day is read from the setting condition database 17, and this is read as the number of devices scheduled for delivery on the day (hereinafter referred to as the "number of scheduled deliveries"). ").)

In the processing after st12, the delivery schedule is adjusted so that the scheduled delivery number becomes the same value as the deliverable number.
In this embodiment, the delivery date of each branch is adjusted based on the above-mentioned geographical conditions so that the delivery is made to the branch office in the same area or a nearby area on the same day as possible.

First, when the number of scheduled deliveries exceeds the number of deliverables, the process proceeds from st12 to st13, where the weight of each of the branch offices to be delivered is reflected by reflecting the geographical relationship with the other branch office to be delivered. wear. And the next st
At 14, the devices whose number exceeds the deliverable number are extracted in order from the one with the lightest weight, and the delivery date of these extracted devices is further advanced at st15.

Here, the weighting process and the delivery date deferring process will be described in detail with reference to FIGS. FIG. 9A is a schematic diagram showing a specific example of geographical conditions, in which a processing target area is divided into a plurality of areas (in the example shown, nine areas A to I). The user assigns each branch office to an area corresponding to the installation location during the setting process of the delivery condition, and the setting condition database 17 stores the positional relationship of each area shown in FIG. Is stored.

When weighting the devices to be delivered at st13 in FIG. 8, first, as shown in FIG. 9 (2), the branch offices to be delivered are extracted for each area. (In the figure, each branch is indicated by an ID number.)

In FIG. 9 (3), for each of the branch offices scheduled for delivery, the number of branch offices scheduled for delivery on the same day is counted separately for the same area and the neighboring area, and each count value is set as "weight". are doing. That is, if the count value in the same area is a and the count value in the neighboring area is b,
The weight of the data configuration (a, b) is set. For example, in the area A in the illustrated example, delivery is scheduled to three places, and one place in the neighboring area B and two places in the area D. Therefore, the weight data for each branch in area A is (3, 3). Similarly, when the weight data of the areas B, D, G, and H where the branch offices to be delivered exist are calculated, (1,5) in the area B, (2,5) in the area D, and (1,2) in the area G. , Area H, (1, 3).

In this embodiment, the number of units to be delivered in one day does not exceed the number of units that can be delivered, and the devices in the same branch office are always delivered on the same day, and priority is given to the area where delivery is concentrated. As a condition, a device that advances the delivery date is determined. FIG. 10 shows a detailed procedure for extracting a device to be deferred, that is, st14 in FIG. First, in st25, which is the first procedure, the difference between the planned number of deliveries and the number of deliverables is determined, and set as the number M to be deferred.

Next, at st26, the branch offices scheduled to be delivered are sorted in ascending order of weight. In st26, for example, after sorting using the weight a for the belonging area of the branch office as the primary key, the secondary sorting is executed by the weight b for the neighboring area. However, not limited to this,
Weights a and b may be added, and sorting may be performed in ascending order of the added value.

At the next st27, paying attention to the branch office having the smallest weight, the number of installations in the branch office is compared with the number M of departures. If the number of installations is equal to or less than M, st27 becomes "YES" and the process proceeds to st28, and the delivery date of the branch office of interest is moved forward. In this deferral, in principle, the next day after the delivery date is set as a new delivery date. However, if this day is a Saturday, Sunday, or a holiday, or if it is a special holiday as described above, the delivery date is further reduced by one day.

In the next st29, the number M of units to be advanced is rewritten based on the number of devices whose delivery date has been advanced. Thereafter, the branch offices having smaller weights are sequentially checked until M becomes 0, and a device for shortening the delivery date is extracted. That is, the branch offices in the same area and neighboring areas which have less delivery schedules are sequentially extracted as the delivery date reduction targets. However, even if the weight is small,
If the number of devices exceeding the number M of deferred vehicles is installed in the branch office, st27 becomes “NO” and st2
Steps 8 to 30 are skipped and the processing target is changed to the next branch office. Therefore, the delivery is not set to be performed twice at the same branch office, and the delivery conditions described above can be observed.

9 (2) and 9 (3), assuming that the number of deliverable vehicles per day is five, each branch is processed according to the procedure of FIG. The branch offices (0011, 0068, 0082) in the areas B, G, and H, which do not have the scheduled delivery points, are extracted as the objects to be reduced in delivery date.

Returning to FIG. 8, when the scheduled delivery number is less than the deliverable number, st16 becomes "YES", and the next day's delivery schedule is checked in next st17 and st18.
If delivery is scheduled the next day, s from st18
Proceeding to t19, the respective branch offices scheduled for delivery are weighted in the same manner as in st13. Further, in the next st20, according to the same procedure as in FIG. 10, each branch office is checked in ascending order of weight, and branch offices whose delivery date is advanced are extracted. If the number of deliverables still does not reach the number of deliverables even after adding the number extracted here, the delivery schedule for the next day is checked again at st17, and the process is continued until the planned number of deliveries becomes equal to the number of deliverables. I do.

In this way, the processing is performed in order from the first day of the month to the last day of the month (st23, 24), and adjustment is made so that delivery to the number of deliverable devices is performed on each delivery day. When the processing up to the last day ends, st23 becomes "YES" and the processing ends. In particular, it is desirable to set the delivery date to be preferentially assigned to a branch office whose delivery date has been advanced, when processing the delayed delivery date.

In FIG. 8, for the sake of simplicity, adjustment is made so that the number of scheduled deliveries and the number of deliverables match, but in actual processing, the two do not always match easily. Absent. Therefore, when the scheduled number of deliveries is less than the number of deliverable units, a predetermined allowable value may be set, for example, when the date shifts to a day when no delivery is scheduled, the extraction of the advance target of the delivery date is stopped.

FIG. 11 shows details of the tentatively determining the second and subsequent delivery dates shown in ST14 of FIG. The processing of st32 to st39 in the figure is for temporarily setting the delivery date for one month for each branch office. Assuming that the delivery amount for each delivery day is the same, the number of delivery times for one month is reduced. The delivery date is adjusted so that it falls within a predetermined upper limit.

In the first st32, the amount loaded to each device of the branch office to be processed is initialized. Note that the initial value of the loading amount is calculated from, for example, the loading amount set on the last delivery day of the previous month's schedule, and the first set value is the same in any device.

In the next st33, it is assumed that each device in the branch office has been loaded with the cash of the initially set loading amount on the first delivery day, and the cash is loaded from the inferred value of the consumption amount in each device. The day when the cash becomes zero is determined, and that day is provisionally set as the second delivery date. Hereinafter, st34-3
In the same way, the delivery date is provisionally set up to the end of the month in the same manner.

When the delivery date up to the end of the month is set, st36
Check the number of deliveries in one month. If the number exceeds the predetermined upper limit, the process proceeds to st37, where the result of setting the delivery date is cleared, the amount charged to each device is increased by a fixed amount, and the processes of st33 to 35 are executed again. .

When a delivery date is set for each branch office so that the number of deliveries does not exceed the upper limit value, the process proceeds from st38 to st40, and the number of deliveries per month for each device is accumulated. I do. In the next st41, the total value is compared with the number of deliverable vehicles for one month obtained in ST13 of FIG. If the total value is less than the number of deliverable units, the amount of the one-time loading is reduced by a fixed amount, and the process is repeated from st33. If the total value exceeds the number of deliverables, increase the loading amount by a certain amount,
Similarly, the processing is repeated from st33.

By repeating the above processing, the total number of deliveries of each device finally coincides with the number of deliverables in one month, and the number of deliveries at each branch is within the upper limit. A delivery date is set for each branch. After this process is completed, the daily delivery is adjusted in ST15 of FIG. 6 to determine the delivery date of each branch office, but here, the same process as shown in FIGS. Since the processing is performed, detailed description is omitted.

FIG. 12 shows details of the scrutiny date determination process in ST16 of FIG. In this embodiment, the scrutiny date is twice a month, and a predetermined period (for example, 10
It is assumed that the delivery date that has passed over the day) is included in the delivery conditions.

The process of FIG. 12 is also performed for each branch office. In the first st43, the dates set as the delivery dates are searched sequentially from the first day of the target month. When the delivery date is retrieved, the number of days between the delivery date and the previous scrutiny date is checked in the next st44, and if this is equal to or greater than the set value, the delivery date is set as the scrutiny date (st45). . st4
When two scrutiny dates are set for one branch office according to the steps 3 to 46, the target is changed to the next branch office at st48, and thereafter, two scrutiny dates are set for each branch office in the same manner.

FIG. 13 shows the procedure of the loading amount determination process in ST17 of FIG. This processing is also performed for each branch office.
In the next st50, the second delivery date is searched for, respectively.

Next, in st51, for each device in the branch office, the inferred value of the amount of consumption in each of the above-mentioned two delivery dates and the period between them is read out every day, and is accumulated for each device. Further, in st52, a loading amount corresponding to the consumption amount expected from the cumulative value is set for each device. If the delivery date falls on the scrutiny date, the amount obtained by adding a predetermined margin to the calculated amount of loading is used as the amount of loading. Hereinafter, similarly, for each delivery date, a loading amount corresponding to the estimated consumption amount by the next delivery date is set for each device. However, since the next delivery date is not determined for the last delivery date of the target month, the initial value of the loading amount determined at the time of provisionally determining the delivery date is set (s
t54).

When the loading amount of each delivery day is determined by the processing of st49 to 54 for each branch office, st55 becomes "YES" and the processing ends. In addition, for a branch office where a plurality of devices are installed, there may be a case where the total of the loading amount of each device is separately calculated in order to output the schedule data.

According to the above-described processing, a cash delivery schedule can be delivered on any day to a number corresponding to the processing capacity of the management company, and can be delivered together to a branch office in the same area or a nearby area. Is set, troubles such as a variation in the number of objects to be delivered depending on the delivery date and a long time required to move between branch offices can be solved, and business efficiency can be greatly improved. In addition, since each device is loaded with cash in an amount corresponding to a deposit / withdrawal state predicted from past data or the like, the efficiency of fund management can be improved.

FIG. 14 shows an example in which the cash delivery schedule is output in the form of a table.
The breakdown of the loading amount for each branch office is shown. In the illustrated example, the delivery date is adjusted with a predetermined allowable value. In the example of FIG. 14, when a plurality of devices are installed, the loading amount is represented in each branch office, but the detailed loading amount in each device may be indicated. Separately, detailed schedule data for each branch office and each delivery date may be output.

By the way, in the above embodiment, the delivery schedule and the loading amount are adjusted according to the number of deliverable units for one month. However, the present invention is not limited to this, and it is assumed that each device is loaded with cash up to the upper limit of the loading amount. It is also possible to determine the delivery schedule. In this case, since the number of deliveries to each device is reduced, the number of deliveries per month is reduced, and the cost of consignment to the management company can be reduced.

FIG. 15 shows a procedure for temporarily determining the delivery date of each branch office by the above method. In this case, since the loaded amount differs depending on the model, the upper limit value of the loaded amount of the device in the target store is extracted in the first st57.

Next, in st58, an initial value of the loading amount is set based on the upper limit value of the loading amount. In this case, when a plurality of devices are installed in the branch office, a value obtained by accumulating the upper limit of the loading amount for each device is set as the initial value.

When the initial value of the loading amount is set in this manner, the same procedure as in steps 33 to 35 in FIG.
Set a delivery date up to the end of the month based on the loading amount (st
59-61). In this process, as shown in FIG. 11, there is no need to adjust the number of deliveries in one month by comparing it with the upper limit, and the process target can be changed to the next branch immediately after the process by the end of the month. Processing speeds up.
Once the delivery date is provisionally determined in this manner, the first
The delivery date and the amount of charge are adjusted for each branch office in the same procedure as in the embodiment, and the cash delivery schedule for one month is completed.

[0080]

As described above, according to the present invention, the creation of a delivery schedule of cash to the automatic transaction devices installed at a plurality of points, respectively, is performed by inferring the future transaction status from data indicating the transaction status of each device. Based on the results and the data indicating the conditions for cash delivery to each device, it is possible to set up an efficient schedule for both delivery work and fund management, reducing the burden on the company that undertakes delivery and In addition, the outsourcing costs of banks can be significantly reduced. Further, the schedule creation work can be made more efficient than the automatic schedule creation. Further, since different schedules are set depending on the target period, security at the time of delivery can be ensured.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram showing a configuration example of a cash delivery schedule creation system according to the present invention.

FIG. 2 is a block diagram illustrating a hardware configuration of a cash delivery schedule creation device.

FIG. 3 is an explanatory diagram showing a setting example of a start screen.

FIG. 4 is a flowchart illustrating a procedure for creating a cash delivery schedule.

FIG. 5 is an explanatory diagram showing an example of a setting screen for a specific holiday.

FIG. 6 is a flowchart illustrating a procedure of a schedule creation process.

FIG. 7 is a flowchart illustrating a procedure of a provisional determination process of a first delivery date.

FIG. 8 is a flowchart illustrating a procedure of a delivery date determination process.

FIG. 9 is an explanatory diagram showing the principle of a process of weighting a branch office and extracting a device to be deferred for a delivery date.

FIG. 10 is a flowchart illustrating a procedure of a process of extracting a device to be deferred.

FIG. 11 is a flowchart illustrating a procedure of provisionally determining a delivery date.

FIG. 12 is a flowchart illustrating a procedure of a scrutiny date determination process.

FIG. 13 is a flowchart illustrating a procedure of a loading amount determination process.

FIG. 14 is an explanatory diagram showing an output example of a cash delivery schedule.

FIG. 15 is a flowchart illustrating a processing procedure when a delivery date is provisionally determined by setting an upper limit of the loading amount.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Cash distribution schedule preparation apparatus 2 Host computer 3 ATM 6 CPU 12 Input part 13 Output part

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G07F 19/00 G07D 9/00 476

Claims (9)

[Claims] 1. A method for determining, by a computer system, a schedule for delivering cash to an automatic transaction device installed at each of a plurality of points, wherein a future transaction status is inferred from data indicating a transaction status of each automatic transaction device. A method for determining a cash delivery schedule, comprising determining a delivery schedule to each device based on the result of the calculation and data indicating conditions for delivering cash to each device. 2. The method for determining a cash delivery schedule according to claim 1, wherein the cash delivery conditions include information on an installation location of each automatic transaction apparatus. 3. The method for determining a cash delivery schedule according to claim 1, wherein the cash delivery conditions include information relating to delivery capacity. 4. The method for determining a cash delivery schedule according to claim 1, wherein the cash delivery conditions include information on the amount of cash loaded in each automatic transaction device. 5. The method for determining a cash delivery schedule according to claim 1, wherein the delivery schedule includes a delivery schedule to each automatic transaction device and a cash loading amount to the automatic transaction device to be delivered. . 6. An automatic transaction device installed at each of a plurality of points, a first input means for receiving an input of data indicating a transaction state of each device, and an input of data indicating conditions for delivering cash to each device. A second input unit to be accepted; an inference unit for inferring a future transaction state using the data indicating the transaction state for each automatic transaction device; and a device for each automatic transaction device based on an inference result by the inference unit and the delivery condition. A cash delivery schedule creation device, comprising: a deciding means for deciding a cash delivery schedule to a customer; and an output means for outputting electronic data of the cash delivery schedule decided by the deciding means. 7. The cash delivery device according to claim 6, wherein said first input means is means for receiving a recording medium on which data indicating a transaction state in each of said automatic transaction apparatuses is recorded and reading said recording information. Schedule creation device. 8. The cash delivery schedule creation device according to claim 6, wherein said first input means is means for taking in said data from a computer which collects data indicating a transaction state in each of said automatic transaction apparatuses by communication. . 9. A step of obtaining a result of inferring a future transaction state based on data indicating a transaction state in each of the automatic transaction apparatuses installed at a plurality of points, data indicating conditions for delivering cash to each apparatus. Receiving the input of the following; determining the cash delivery schedule to each device based on the inference result about the future transaction state and the cash delivery condition; outputting electronic data of the determined cash delivery schedule A recording medium on which a program for executing each of the steps is recorded.