JP2014078140A - Automatic transaction device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an automatic transaction device for facilitating the change of an operation schedule.SOLUTION: An automatic transaction device 1 which operates with operation content following an operation schedule includes: a storage part 14 for storing operation schedule data 30 for determining an operation schedule as a reference and change schedule data 32 for determining an operation schedule during a specific period; a registration part 40 for extracting the data the date or day of whose operation is coincident with the current day or date, and the time of whose operation is the same as the current time or the nearest future time from between the operation schedule data and the change schedule data, and for, when the data the time of whose operation is the same time are extracted from between the operation schedule data and the change schedule data, registering the data of the change schedule data; and a processing part 42 for instructing the execution of the action of the data at the time of the operation of the data on the basis of the data registered by the registration part.

Description

  The present invention relates to an automatic transaction apparatus and an operation schedule change technique for an automatic transaction apparatus.

  In an automatic transaction apparatus (ATM) widely used in financial institutions and the like, transactions (payment, payment, bookkeeping, transfer, etc.) according to the operation schedule are provided (for example, Patent Document 1). The operation schedule is tailored to the season, day of the week, or specific period (New Year, Obon).

  The need to change this operational schedule often arises. The change is generally performed by directly inputting from an automatic transaction apparatus and changing the operation schedule data, or by downloading the changed operation schedule data from a remote place.

  In these conventional methods, for example, in the case of “change only for a certain period” such as change only during the summer period or change only during the campaign period, the change is made from the existing operation schedule data to the new operation schedule data at the time of change, and the change period ends. Later, it was often necessary to perform two operations of returning to the conventional operation schedule data again. Further, when there are a plurality of change periods and they are overlapped, the number of switching operations is further increased, and the switching operation is complicated.

JP-A-8-161593

In order to realize flexible operation according to regional characteristics and demands, an automatic transaction apparatus that can easily change the operation schedule is required.
In view of the above problems, an object of the present invention is to provide an automatic transaction apparatus that can easily change an operation schedule.

  In order to achieve the above object, the operation schedule data that defines the operation schedule as a reference, the storage unit that stores the change schedule data that defines the operation schedule for a specific period, and the operation schedule data and the change schedule data, The operation day of the week or day coincides with the current day of the week or day, and the operation time is the same as the current time or the latest data in the future time is extracted, and the operation schedule data and the change schedule data are extracted from the operation schedule data and the change schedule data. When data having the same time is extracted, a registration unit that registers the data of the change schedule data, and based on the data registered by the registration unit, the data And a processing unit that instructs execution of the action.

  ADVANTAGE OF THE INVENTION According to this invention, the automatic transaction apparatus which can change an operation schedule easily can be provided.

It is a block diagram which shows the main structures of the automatic transaction apparatus 1 of this embodiment. 3 is a diagram illustrating a configuration example of operation schedule data 30. FIG. A part of the definition information of the operation schedule data 30 is shown. It is a figure which shows the structural example of change schedule data. It is the time chart which compared the application period of the operation schedule data 30 and change schedule data. It is a figure explaining the example which inputs a change content directly from the automatic transaction apparatus 1, and changes an operation schedule. It is a figure explaining the example which changes operation schedule data from a remote place. It is a figure which shows the outline of the automatic driving | operation process by the operation schedule data 30 and the change schedule data 32. FIG. 4 is a flowchart illustrating a procedure of timer registration processing by a timer registration unit 40. It is a subroutine 1 for explaining the procedure of the schedule data search. It is subroutine 2 explaining the procedure of schedule data search.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a main configuration of an automatic transaction apparatus (ATM) 1 of the present embodiment.
The automatic transaction apparatus 1 includes a CPU 10, a RAM 12, a storage unit 14, a display / touch panel 16, a banknote processing unit 18, a card / passbook processing unit 20, a coin processing unit 22, and a communication I / F 24.

  CPU10 is a control part which controls the whole automatic transaction apparatus 1 according to various programs. In particular, in the present embodiment, the CPU 10 controls the operation contents of the automatic transaction apparatus 1 according to the operation schedule data.

  The operation content refers to the operation content of the automatic transaction device 1 and the transaction content (payment, payment, bookkeeping, transfer, etc.) that can be performed by the automatic transaction device 1. The operation schedule data defines the schedule of the daily operation contents, that is, what kind of action (for example, execution of transaction start) is performed every day of the week or on a specific day (for example, a public holiday). Data.

  The RAM 12 is a temporary storage memory. For example, it is used as a temporary storage of data transmitted from the outside or a working memory of the CPU 10. The storage unit 14 is a memory for storing data, for example, a hard disk. The storage unit 14 stores various control programs of the automatic transaction apparatus 1, operation schedule data, and the like.

  The display / touch panel 16 displays the menu and operation guide of the automatic transaction apparatus 1, and correspondingly selects the menu from the customer and inputs the amount / password. It is composed of a thin display unit such as an LCD and a touch panel laminated thereon.

  The display / touch panel 16 also serves as an input unit and a display unit for directly inputting the change schedule data from the automatic transaction apparatus 1 when changing the operation schedule data.

  When there is a payment instruction or deposit operation from the customer, the banknote processing unit 18 counts the banknote of the amount according to the content of the instruction from the internal banknote unit and conveys it to the banknote payment slot, or the banknote that has been deposited Is conveyed to the banknote unit and stored.

  The card / passbook processing unit 20 takes in / returns a medium such as a card or a passbook. At the time of taking in the medium, information attached to the medium is read, personal information and account number are specified, and a transaction history and the like are written / printed.

As with the banknote processing unit 18, the coin processing unit 22 pays coins and stores coins.
The communication I / F 24 is installed in a remote place, and manages the automatic transaction apparatuses 1 collectively, or a customer database in which customer information is stored and the automatic transaction apparatus 1 to transmit and receive data. It controls execution.

  The CPU 10 reads a predetermined program from the storage unit 14 and controls the display / touch panel 16, the banknote processing unit 18, the card / passbook processing unit 20, the coin processing unit 22, the communication I / F 24, and the like.

  FIG. 2 is a diagram illustrating a configuration example of the operation schedule data 30. As described above, the operation schedule data is data that defines an operation schedule for one day, that is, an action (for example, execution of transaction start) for each day of the week or a specific day (for example, a holiday). It is. The operation schedule data 30 usually defines one year. However, some are defined for 10 years.

  The operation schedule data 30 is largely divided into a specific day schedule and a day of the week schedule. The specific day schedule is a schedule defined for each day. The specific day schedule is, for example, a schedule defined for each special day of holidays such as New Year (January 1, January 2, January 3). This specific day schedule is prioritized over the Happy Monday schedule and the day of the week schedule described below.

  The day of the week schedule is a schedule defined for each day of the week. Since the operation of the automatic transaction apparatus 1 varies greatly depending on the day of the week, it is generally possible to reduce the load of definition work by defining for each day of the week compared to the case of defining for each day.

  The Happy Monday schedule is an operation schedule when Monday is Happy Monday. In the automatic transaction apparatus 1, in the case of Monday, it is determined whether or not it is Happy Monday, and is handled as a day of the week that is distinguished from a normal Monday.

  In addition to the Happy Monday schedule, the day of the week schedule is divided into a Monday schedule, a Tuesday schedule,... A Sunday schedule.

  FIG. 3 shows a part of definition information of the operation schedule data 30, and shows definition information of Monday schedule data as an example. Since the format of the definition information is the same for the day of the week schedule and the specific day schedule, the day of the week schedule is shown as a representative.

  The operation schedule data 30 includes each operation data. The operation schedule data 30 for Monday is assumed to be composed of four pieces of operation data (hereinafter also abbreviated as data) of data p1 to p4. Each piece of operational data is composed of information on the applicable day of the week or specific date, “schedule time” that is the start time of the action of the operational data, and “actions to be performed at the schedule time” that is the content of the action type.

  For example, the data p1 is a content that instructs the automatic transaction apparatus 1 to “start all transactions” at “8:00” on “Monday”. The start of all transactions refers to starting all transactions that can be made by the automatic transaction apparatus 1 such as deposit / withdrawal / transfer / bookkeeping.

  The data p2 is a content for instructing the automatic transaction apparatus 1 to “stop transfer transaction” at “15:00” on “Monday”. After 15:00, only transfer transactions are stopped, and other transactions are allowed.

  The data p3 is a content for instructing the automatic transaction apparatus 1 to “stop all transactions” at “20:00” on “Monday”. The data p4 is a content for instructing the automatic transaction apparatus 1 to “automatic transaction apparatus shutdown” at “20:30” of “Monday”. The main power source of the automatic transaction apparatus 1 is turned off at 20:30.

  Since the operation schedule data 30 is a basic schedule determined throughout the year, it is necessary to change the operation schedule data 30 in order to operate according to different event schedules depending on the region, such as this year's Golden Week alone. become.

  Conventionally, the entire operation schedule data 30 is updated according to the contents of the change even if the change is only for one period. On the other hand, in the present embodiment, the operation schedule data 30 itself is not changed, but the change schedule data that is data of only the principle change contents is created, and the change schedule data and the operation schedule data 30 are contrasted. The action was decided and operated. Hereinafter, the operation schedule data serving as a reference is referred to as operation schedule data, and the operation schedule data for a specific period is referred to as change schedule data.

  FIG. 4 is a diagram illustrating a configuration example of change schedule data. FIG. 5 is a time chart comparing the operation schedule data 30 and the application periods of the two change schedule data in FIG.

  As shown in FIG. 5, the operation schedule data 30 is a schedule that is applied to the entire period, the change schedule data A is a schedule that is applied to the Golden Week period and the summer period, and the change schedule data B is in the summer period. The schedule applied during the Bon Festival period. The overlap information K will be described later.

  FIG. 4A is a diagram illustrating the day of the week / time / action of the change schedule data A. FIG. The change content is to change the schedule for starting all transactions at 8:00 on Monday to the content starting all transactions at 7:30. Two pieces of operational data corresponding to this are data q1 and data q2.

  The data q1 is a content instructing the automatic transaction apparatus 1 to perform an action of “start all transactions” at “7:30” on “Monday”. The data q2 is a content instructing the automatic transaction apparatus 1 to “none” as an action at “8:00” on “Monday”. The data q2 is for invalidating the instruction of the data p1 (FIG. 3) existing in the operation schedule data 30. This is because if there is no instruction for the data q2, the automatic transaction apparatus 1 will be instructed to start the transaction again at 8:00.

  FIG. 4B is a diagram illustrating data obtained by adding valid period data to the data q1 and q2 of the change schedule data A described with reference to FIG. The content of the change is to make the change shown in FIG. 4A effective during the summer season (7/1 to 8/31).

  FIG. 4C is a diagram showing data when the change schedule data B is added to the change schedule data A. The change schedule data B is for making the automatic transaction apparatus 1 a transaction only for withdrawal from 7:30 only on Monday during the Bon Festival period.

  When there are a plurality of change schedule data and overlapping periods occur, overlap information K is added to each data in order to clarify the priority among the change schedule data. The overlap information K is assigned as 0, 1, 2,...

  The overlap information K of the operation schedule data 30 is 0. Here, it is assumed that the change schedule data B has priority over the change schedule data A, the overlap information K = 1 for the data q1 and data q2 of the change schedule data A, and the overlap information for the data r1 of the change schedule data B Let K = 2.

6 and 7 are diagrams for comparing the conventional method and the method of the present embodiment when changing the operation schedule.
FIG. 6 is a diagram for explaining an example of changing the operation schedule by directly inputting the change contents from the automatic transaction apparatus 1. FIG. 6A shows an example of a conventional method. When changing, the operation schedule data 30 is displayed on the display / touch panel 16 and necessary change schedule data 32 is input from the display / touch panel 16.

  The change processing unit 34 rewrites the operation schedule data 30 in the storage unit 14 based on the input change schedule data 32 and causes the storage unit 14 to store the changed operation schedule data 30a. The change processing unit 34 is a function realized by the CPU 10 that has read a predetermined operation schedule data change program.

  FIG. 6B is based on the system of this embodiment. When changing, the operation schedule data 30 is displayed on the display / touch panel 16 and necessary change schedule data 32 is input from the display / touch panel 16. An effective period or overlap information K is also input as the change schedule data 32.

  The change processing unit 34 stores the input change schedule data 32 in the storage unit 14. In the storage unit 14, change schedule data 32 is stored separately from the operation schedule data 30. The change processing unit 34 is a function realized by the CPU 10 that has read a predetermined operation schedule data change program. The change schedule data 32 is stored in the storage unit 14 until the end date of the validity period, and is deleted by the change processing unit 34 after the end date.

  FIG. 7 is a diagram illustrating an example of changing operation schedule data from a remote location. FIG. 7A is based on the conventional method. When the change is made, the changed operation schedule data 30a is downloaded to the automatic transaction apparatus 1 from the center server via the communication I / F 24 of the automatic transaction apparatus 1 via a network such as the Internet. The downloaded operation schedule data 30 a is stored in the storage unit 14 in place of the old operation schedule data 30.

  FIG. 7B is based on the system of this embodiment. At the time of change, the change schedule data 32 is downloaded to the automatic transaction apparatus 1 and stored in the storage unit 14 together with the operation schedule data 30.

  FIG. 8 is a diagram showing an outline of the automatic driving process using the operation schedule data 30 and the change schedule data 32. The automatic driving process is a function realized by the CPU 10 that has read the automatic driving process program, and includes a timer registration unit 40 (also referred to as a registration unit), a timer processing unit 42 (also referred to as a processing unit), and an action execution unit 44. , Mainly executed.

  The timer registration unit 40 reads the operation schedule data 30 and the change schedule data 32 from the storage unit 14, and the operation day of the week or day matches the current day of the week or day and the operation time is the same as the current time. When the most recent data at the future time is extracted, and data having the same operation time is extracted from the operation schedule data 30 and the change schedule data 32, the data of the change schedule data 32 is processed by the timer process. Register with the department.

  In addition, when there are a plurality of types of change schedule data 32 and the data having the same operation time is extracted from the plurality of change schedule data 32, the timer registration unit 40 prioritizes the change schedule data 32. According to the above, one data is registered. The priority order depends on the size of overlap information. The timer registration unit 40 is activated by the timer processing unit 42.

  The timer processing unit 42 instructs the action execution unit 44 to start the requested action when the time (timed out) of the data registered from the timer registration unit 40 comes. In addition, the timer processing unit 42 activates the timer registration unit 40.

Then, the action execution unit 44 executes the action started from the timer processing unit 42.
As described above, in the automatic driving process, the time action closest to the current time is read from the operation schedule data 30 and the change schedule data 32 including the start-up of the power supply of the automatic transaction apparatus 1, and the time is reached. Then, the corresponding action is executed, and after execution, the closest time action is read again.

  Thereby, when the change period ends, it is possible to automatically return to the operation schedule data 30 which is the schedule before the change. It is not necessary to delete the change schedule data 32 immediately.

The timer registration process performed by the timer registration unit 40 will be described below. FIG. 9 is a flowchart illustrating the procedure of timer registration processing by the timer registration unit 40.
In the following, it is currently set at 7:00 on Monday, August 11 (bon festival period). The current date and time and day of the week are acquired (step S10). Here, the specific day schedule process is performed first (step S12), and then the day of the week schedule process (step S20) is performed. As described above, this is because priority is given to the specific day over the day of the week.

A schedule data search for a specific date on the same date as the current date is performed (step S12). The schedule data search procedure will be described with reference to the subroutines of FIGS. 10A and 10B.
To briefly describe the following procedure, in the schedule data search, a search that is the same as or closest to the current date and time in the order of the operation schedule data 30 → the change schedule data A → the change schedule data B from the data with a small overlap information K is performed. Obtain the result data. Then, the obtained search result data is exchanged in the order of the overlapping data, and finally one search result data is obtained.

  First, the process is initialized (step S30). For initialization, the overlap information K to be searched is set to K = −1, and the search result data is set to “none”.

  K + 1 → K (step S32). Initially, K = −1, so that K = 0 at this step.

  It is determined whether K exceeds Max (step S34). The overlap information Max is the maximum value of the overlap information in the change schedule data 32. In the example of FIG. 4, Max = 2.

  If it is determined that K does not exceed Max (No in step S34), data including the current date in the effective period is extracted from the data having overlapping information to be searched (step S36). Initially, since the overlap information K = 0 as the search target, data including the current date in the effective period is extracted from the operation schedule data 30 where K = 0.

It is determined whether there is extracted data (step S38). In the operation schedule data 30, since the valid period is the entire period, data including the current date (August 11) is always extracted.
If it is determined that there is no extracted data (No in step S38), the process returns to step S32.

  When it is determined that there is extracted data (step S38 Yes), data that matches the day of the week or a specific day is extracted from the extracted data (step S40). Here, since the process is related to the specific day schedule in step S12, data with a specific day is extracted (step S40).

  It is determined whether there is extracted data that matches the specific date (step S42). If it is determined that there is no extracted data that matches the specific date (No in step S42), the process returns to step S32. In the example of the operation schedule data 30 in FIG. 3, there is no specific date that coincides with August 11, so step S42 is determined as No.

  If it is determined that there is extracted data that matches the specific date (Yes in step S42), data that is the same as the current time or closest in the future time is further obtained from the extracted data (step S44).

It is determined whether there is data to be obtained (step S46). If it is determined that there is no data to be obtained (No in step S46), the process returns to step S32.
If it is determined that there is data to be obtained (step S46 Yes), it is determined whether the search result data = none (step S48). This is because the search result data is replaced.

  Since the search result data is set to “none” in step S30, it is determined that the search result data = none in the first loop of this subroutine (step S48 Yes). Step S50 is jumped and the obtained data is set as search result data (step S52). Thereafter, the process returns to step S32.

  If there is search result data (No in step S48), it is determined whether the calculated data schedule time> search result data schedule time (step S50). Determine whether the schedule time of the obtained data is closer to the current time than the schedule time of the search result data that has already been registered. This is for registration.

  For example, when the schedule time of the obtained data is 7:15 and the schedule time of the registered search result data is 7:30, the obtained data closer to the current time (7:00) This is to make it effective.

  If it is determined that the schedule time of the obtained data> the schedule time of the search result data (No in step S50), the obtained data is set as the search result data (step S52). The search result data is replaced. Thereafter, the process returns to step S32.

  If it is determined that the schedule time of the obtained data> the schedule time of the search result data (Yes in step S52), the search result data is not replaced and the process returns to step S32.

  Returning to step S32, next to the operation schedule data 30 with K = 0, the change schedule data A with K = 1 is searched in the same procedure as described above. After searching for the change schedule data A, the process returns to step S32, and the change schedule data B with K = 2 is searched.

  After searching for the change schedule data B, the process returns to step S32, where K = 3, and it is determined that K has exceeded Max (step S34 Yes), the subroutine is terminated, and the process proceeds to step S14 in FIG.

In the data examples shown in FIGS. 2 to 4, there is no specific date corresponding to the current date (August 11), so the process proceeds to step S14 without any search result data.
In step S14, it is determined whether there is search result data. If it is determined that there is a search result (step S14 Yes), the time and action of the corresponding data are registered in the timer processing unit 42 (step S16).

  If it is determined that there is no search result data (No in step S14), the process jumps to step S16 and proceeds to step S18. In step S18, it is determined whether the timer has been registered (step S18). If it is determined that the timer has been registered (step S18 Yes), this flowchart is terminated. Therefore, if search result data is found on a specific day, the timer registration process is terminated without performing the day of the week schedule process (steps S20 to S24).

  In the data examples as shown in FIGS. 2 to 4, since there is no data registered in the timer process as the specific date, it is determined that the timer has not been registered (No in step S14, step S18), and the process proceeds to step S20.

  In step S20, the day of the week schedule process is performed. Search the schedule data from the corresponding day of the week data. Similar to step S12, the process proceeds to the subroutine of FIGS. 10A and 10B.

  About the subroutine of FIG. 10A and B, the part already demonstrated by the above-mentioned specific day schedule search is abbreviate | omitted, and it demonstrates along the operation schedule data 30, the change schedule data A, and the change schedule data B shown in FIGS. To do. Also, as described above, the current time is 7:00 on Monday, August 11 (bon festival period).

  After the initialization in step S30, the operation schedule data 30 is searched. Since K = 1, the process proceeds to step S36. In the operation schedule data 30, since the valid period is the entire period, data including the current date is extracted (step S36). When it is determined whether there is extracted data (step S38), it is determined that there is extracted data (Yes in step S38). .

  Further, data that matches the day of the week is extracted from the extracted data (step S40). Data p1 to p4 are extracted. In determining whether there is extracted data (step S42), it is determined that there is extracted data (step S42 Yes).

  Further, from the extracted data, data that is the same as the current time or closest to the future time is obtained (step S44). Here, the data p1 of the operation schedule data 30 is obtained. In determining whether there is data to be obtained (step S46), it is determined that there is data to be obtained (Yes in step S46).

  Search result data = none? Is determined (step S48). Since the search result data = none at the beginning of the loop, it is determined that there is none (step S48 Yes), and the process proceeds to step S52. Then, the data p1 is set as search result data (step S52), and the process returns to step S32.

  Returning to step S32, the change schedule data A with K = 1 is searched. Since the current date is August 11, the change schedule data A is extracted in step S36. In step S40, data q1 and q2 are extracted. In step S44, since the current time is 7 o'clock, data q1 is extracted. It is determined whether or not the obtained data schedule time> search result data schedule time (step S50).

  Since the time of the data q1 is 7:30 and the time of the data p1 is 8:00, since q1> p1 is not satisfied in step S50, step S50 is No and the process proceeds to step S52. Data q1 is set as search result data instead of data p1 (step S52), and the process returns to step S32.

  If the current time is 7:31, the data p1 of the operation schedule data 30 is once registered as search result data, and then the data q2 of the change schedule data A is registered instead.

  Returning to step S32, the change schedule data B with K = 2 is searched. Since the current date is August 11, change schedule data B is extracted in step S36. In step S40, data r1 is extracted. Also in step S44, the data r1 is extracted. Since the time of the data r1 is 7:30 and the time of the data q1 is 7:30, r1> q1 is not satisfied in step S50, so step S50 is No and the process proceeds to step S52. Instead of data q1, data r1 is set as search result data (step 52), and the process returns to step S32.

Returning to step S32, K = 3, and in step S34, the subroutine is terminated, and the process proceeds to step S22 in FIG.
In step S22, it is determined whether there is search result data. If it is determined that there is a search result based on the data r1 (step S22 Yes), the time and action of the corresponding data are registered in the timer process (step S24). Here, the data r1 of the change schedule data B set as the search result data is registered. If it is determined that there is no search result (step S22 No), this flowchart is terminated.

At least the effects achieved by the above-described embodiment will be described below.
1) When the operation schedule data is changed, the operation schedule data is not directly changed, but is held as the change schedule data, and the change schedule data is provided with a valid period.
2) Since the change schedule data is provided with overlap information (priority), it becomes easy to cope with a plurality of changes.
3) The change of the fixed period can be performed by designating the day of the week, and the operation of returning after the period is not required.
4) Since no changes are made to the basic operation schedule data at the time of the change, there is no possibility that a big trouble will occur due to a change mistake or the like.
5) Further, even when the operation schedule is changed from a remote location, only the change schedule data with a small data amount needs to be transferred, so that the transfer amount can be reduced.

  In the above embodiment, the timer registration process is described as being executed by software processing by the CPU. However, part or all of the timer registration process may be executed by hardware. The same applies to the timer processing unit and the action execution unit.

  Note that the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the components without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, all the constituent elements shown in the embodiments may be appropriately combined. Furthermore, constituent elements over different embodiments may be appropriately combined. It goes without saying that various modifications and applications are possible without departing from the spirit of the invention.

1 Automatic transaction device 10 CPU
12 RAM
14 Storage Unit 16 Display / Touch Panel 18 Bill Processing Unit 20 Card / Passbook Processing Unit 22 Coin Processing Unit 24 Communication I / F
30 operation schedule data 32 change schedule data 34 change processing unit 40 timer registration unit 42 timer processing unit 44 action execution unit

Claims (6)

In the automatic transaction device that operates with the operation contents according to the operation schedule,
A storage unit for storing operation schedule data for determining a reference operation schedule and change schedule data for determining an operation schedule for a specific period;
From the operation schedule data and the change schedule data, extract data in which the operation day of the week or day matches the current day of the week or day and the operation time is the same as the current time or the closest in the future time In the case where data whose operation time is the same time is extracted from the operation schedule data and the change schedule data, a registration unit for registering the data of the change schedule data;
An automatic transaction apparatus comprising: a processing unit that instructs execution of an action of the data based on data registered by the registration unit at a time of operation of the data. When the registration unit extracts a plurality of types of the change schedule data and extracts data whose operation time is the same time from the plurality of change schedule data, the registration unit 1 according to the priority of the change schedule data. The automatic transaction apparatus according to claim 1, wherein two pieces of data are registered. The automatic transaction apparatus according to claim 2, wherein information indicating a priority order among the change schedule data is attached to the change schedule data. When the registration unit searches for data that matches the current day of the week or day from the operation schedule data and the change schedule data, the registration unit searches for the day with priority.
The automatic transaction apparatus according to claim 1. An automatic transaction apparatus having a storage unit for storing operation schedule data for determining a reference operation schedule and change schedule data for determining an operation schedule corresponding to a specific day of the week or a specific day, according to the operation schedule In operation method to operate,
From the operation schedule data and the change schedule data, extract data in which the operation day of the week or day matches the current day of the week or day and the operation time is the same as the current time or the closest in the future time ,
When extracting data whose operation time is the same time from the operation schedule data and the change schedule data, register the data of the change schedule data,
An operation method for an automatic transaction apparatus, comprising: instructing execution of an action of the data at a time of operation of the data based on the registered data. According to the operation schedule data, the operation schedule data for setting the reference operation schedule and the change schedule data for determining the operation schedule corresponding to a specific day of the week or a specific day are stored in the computer of the automatic transaction apparatus. In a program that performs an action,
From the operation schedule data and the change schedule data, extract data in which the operation day of the week or day coincides with the current day of the week or day and the operation time is the same as the current time or the closest in the future time Steps,
In the case where data whose operation time is the same time is extracted from the operation schedule data and the change schedule data, the step of registering the data of the change schedule data,
And a step of instructing execution of an action of the data at a time of operation of the data based on the registered data.