JP6790379B2 - Holiday work plan creation system, holiday work plan creation device, holiday work plan creation method and holiday work plan creation program - Google Patents

Description

The present invention relates to a holiday work plan creation system, a holiday work plan creation device, a holiday work plan creation method, and a holiday work plan creation program.

Some branches of financial institutions such as banks carry out low counter operations on holidays. Holidays here refer to Saturdays, Sundays, and holidays on the calendar. In addition, the low counter business has a lot of necessary documents such as opening a new account, various change procedures, investment consultation and time deposit, and it takes a long time to work. Branches that perform low counter operations on holidays (hereinafter referred to as "holiday business branches") are limited to major branches with a large number of visits. For this reason, the holiday business at the holiday business branch is handled by convening employees from nearby branches that do not operate on holidays.

Conventionally, regarding the schedule reception system, a schedule reception system has been developed that accepts a customer's request for a scheduled visit date using the Internet and changes the visit date according to the request (see Patent Document 1).

Japanese Unexamined Patent Publication No. 2004-127320

If the technique described in Patent Document 1 is applied to the holiday low counter business in a financial institution, the employee in charge of the customer (hereinafter referred to as "person in charge") can be assigned to the designated holiday.
However, simply applying the technique described in Patent Document 1 was not sufficient to promote over-the-counter financial transactions at holiday business branches. In other words, if the customer comes to the store without making a reservation, the person in charge of the customer may be at work because the financial institution decides to carry out the holiday work on a rotating basis as explained above. There was a problem that it was low and missed sales opportunities.

The present invention has been made in view of the above problems, and can create a more desirable holiday work plan for employees who go to work on holidays, a holiday work plan creation system, a holiday work plan creation device, and a holiday work plan creation method. And it provides a holiday work planning program.

In order to solve the above problems, the holiday work plan creation system according to the present invention relates to the customer's past visits, and includes a customer information storage unit that stores store visit information including past visit dates on holidays, and the past. It is equipped with a store visit time management department that predicts the next store visit time on the customer's holiday from the result of totaling the store visit dates, and a holiday work plan creation department that creates a holiday work plan for the person in charge of the customer. The attendance planning department is characterized in that the person in charge assigns the next visit time on the customer's holiday as the day when the person in charge goes to work on a holiday .

According to the present invention, it is possible to create a more desirable holiday work plan for employees who go to work on holidays.

It is a schematic block diagram of the holiday work plan making system which concerns on embodiment. It is a block diagram of a customer terminal, a bank employee rotation calculation server, and a reception terminal which constitute a holiday work plan creation system which concerns on embodiment. This is an example of the data structure of holiday work availability information. This is an example of the data structure of the customer information in charge. This is an example of the data structure of store visit history information. This is an example of the data structure of employee rotation information. This is an example of the data structure of the person in charge necessity judgment information. It is a functional block diagram of a bank employee rotation calculation server. This is an example of a sequence diagram showing a store visit history recording process. This is an example of a passbook / card insertion guidance screen displayed on the reception terminal. This is an example of a store visit purpose selection screen displayed on the reception terminal. This is an example of a sequence diagram showing a bank employee rotation calculation process. This is an example of a holiday work notification screen of the person in charge displayed on the customer terminal. This is an example of a flowchart of a process for determining the necessity of a person in charge. This is an example of a flowchart of the prediction process of the next visit date and time. This is an example of a flowchart of the forecast processing of a branch office. This is an example of a flowchart of a process for determining a holiday work plan.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings as appropriate.
Each figure is only schematically shown to the extent that the present invention can be fully understood. Therefore, the present invention is not limited to the illustrated examples. Further, in each figure, common components and similar components are designated by the same reference numerals, and duplicate description thereof will be omitted.

<< Configuration of holiday work planning system for the embodiment >>
The configuration of the holiday work plan creation system 1 will be described with reference to FIG. FIG. 1 is a schematic configuration diagram of the holiday work plan creation system 1 according to the embodiment.
The holiday work plan creation system 1 creates a holiday work plan at a holiday business branch of a financial institution. In particular, here, employees are convened on a rotating basis from a neighboring branch office that is not open on holidays to respond. The explanation will be made assuming a case. Therefore, in the holiday work plan created by the holiday work plan creation system 1, in addition to the employees who perform low counter work at the holiday business branch on weekdays, neighboring branches that do not perform low counter work at the holiday business branch on weekdays. Employees will be included. In the following, the cycle in which employees are convened may be referred to as "employee rotation".

As shown in FIG. 1, the holiday work plan creation system 1 includes a customer terminal 101, a bank employee rotation calculation server 102, a reception terminal 103, a store visit history DB 111, a holiday work availability DB 112, a customer information DB 113 in charge, and a bank employee. It is configured to include a rotation DB 114 and a person in charge necessity determination DB 115.

The customer terminal 101 is a terminal owned by a customer of a financial institution, and may be a generally used general-purpose terminal. The customer terminal 101 is, for example, a multifunctional mobile phone (smartphone: Smartphone) or a PC (Personal Computer), and is equipped with a screen display program or the like. The customer terminal 101 is connected to the employee rotation calculation server 102 via a wireless communication network. A dedicated service application is installed in the customer terminal 101, and by activating this service application, it is possible to acquire the holiday work schedule of the employee in charge via the employee rotation calculation server 102. The acquired holiday work schedule of the employee is displayed on the touch display of the customer terminal 101.

The employee rotation calculation server 102 is a device equipped with a function of calculating the employee rotation for holiday work at a holiday business branch. In addition to the customer terminal 101, the bank employee rotation calculation server 102 is connected to the store visit history DB 111, holiday work availability DB 112, customer information DB 113 in charge, employee rotation DB 114, and person in charge necessity determination DB 115 via a communication cable. The communication cable may be, for example, a dedicated line of a financial institution.

The store visit history DB 111 stores information (store visit history information) regarding the history of visits to the customer's branch offices.
The holiday work availability DB 112 stores information regarding whether or not the employee can work on holidays (holiday work availability information).
The customer in charge information DB 113 stores information (customer in charge information) about the customer in charge of the bank employee.
The employee rotation DB 114 stores information (employee rotation information) regarding the employee rotation for holiday work at the holiday business branch.
The person in charge necessity determination DB 115 stores information (information on whether or not the person in charge is required to respond) for each purpose of visiting the store.

The reception terminal 103 is a terminal installed at the entrance of a branch office (also called a branch office) and accepts customers' visits. The reception terminal 103 has a general-purpose display and is equipped with a function of displaying a screen related to reception work. The reception terminal 103 is connected to the store visit history DB 111 via a communication cable. The communication cable may be, for example, a dedicated line of a financial institution. When a customer visits a branch office, he / she inserts a passbook or a card into the reception terminal 103, and then operates the screen to select the purpose of visiting the store. The reception terminal 103 outputs a reception card on which the reception number is printed according to the selected purpose of visiting the store.

With reference to FIG. 2, the configuration of each device constituting the holiday work plan creation system 1 will be described. FIG. 2 is a block diagram of the customer terminal 101, the employee rotation calculation server 102, and the reception terminal 103.

The customer terminal 101 includes an input display unit 201, a control unit 202, and a communication control unit 203.
The input display unit 201 is, for example, a touch display, which accepts input of various information by the customer and displays the information notified from the bank employee rotation server 102.
The control unit 202 includes, for example, a CPU (Central Processing Unit), a RAM (Random Access Memory), and a ROM (Read Only Memory). The CPU is a central control unit and performs program execution processing. RAM is a temporary storage means used by the CPU. The ROM is a non-volatile storage means, and stores a program or the like executed by the CPU.
The communication control unit 203 is, for example, a communication module and performs data communication with the employee rotation server 102.

The reception terminal 103 includes an input display unit 401, a passbook / card reading unit 402, a control unit 403, a communication control unit 404, and a reception card ticketing unit 405.
The input display unit 401 is a touch display, displays a reception screen or the like to the customer, and receives input of various information by the customer.
The passbook / card reading unit 402 accepts passbooks and cards used by financial institutions and reads information (for example, account numbers) stored in them as magnetic data or the like.
The control unit 403 includes, for example, a CPU (Central Processing Unit), a RAM (Random Access Memory), and a ROM (Read Only Memory).
The communication control unit 404 is, for example, a communication module, and performs data communication with the store visit history DB 111.
The reception card issuing unit 405 outputs a reception card printed with a reception number according to the purpose of the visit selected by the customer who visited the financial institution.

The employee rotation calculation server 102 includes a control unit 301 and a communication control unit 302.
The control unit 301 includes, for example, a CPU (Central Processing Unit), a RAM (Random Access Memory), and a ROM (Read Only Memory).
The communication control unit 302 is, for example, a communication module, and performs data communication between the customer terminal 101, the store visit history DB 111, the holiday work availability DB 112, the customer information DB 113 in charge, the employee rotation DB 114, and the person in charge necessity determination DB 115.

Next, with reference to FIGS. 3 to 7, the customer terminal 101 connected to the employee rotation calculation server 102, the store visit history DB 111, the holiday work availability DB 112, the customer information DB 113 in charge, the employee rotation DB 114, and the person in charge necessity determination DB 115 The configuration of is described.

With reference to FIG. 3, the information stored in the holiday work availability DB 112 will be described. FIG. 3 is an example of a data structure of holiday work availability information stored in the holiday work availability DB 112. The holiday work availability information consists of the employee name, the branch office to which the employee belongs, and the holiday work availability identification information. Holiday work availability information is, for example, updated by the employee before the holiday work plan is created.
The employee name is the employee's name. Information such as an employee number may be used instead of the employee's name. The affiliated branch is the name of the branch to which the employee belongs. The holiday work availability identification information is composed of information indicating whether or not each holiday work is possible in the next month. Here, as for the holiday work availability identification information, "○" is shown on days when holiday work is possible, and "x" is shown on days when holiday work is not possible.

With reference to FIG. 4, the data structure of the responsible customer information stored in the responsible customer information DB 113 will be described. FIG. 4 is an example of the data structure of the customer information in charge. The customer information in charge consists of the name of the employee, the name of the customer in charge, the amount of assets, and remarks information. The customer information in charge is updated by the bank employee, for example, when the customer receives the low counter business for the first time or when the customer information is changed.
The employee name is the employee's name. The name of the customer in charge is the name of the customer in charge of the bank employee. The amount of assets is the total amount of assets that the customer in charge entrusts to the financial institution. The remarks information is reference information about the customer in charge.

The data structure of the store visit history information stored in the store visit history DB 111 will be described with reference to FIG. FIG. 5 is an example of the data structure of the store visit history information. The store visit history information consists of an account number, a customer name, a store visit date and time, a store visit purpose, and a store visit branch office. The store visit history information is updated every time a customer visits a branch office and issues a reception card from the reception terminal 103.
The account number is the number of the account opened at the financial institution. The customer name is the name of the customer who opened the account number. The store visit date and time is information indicating the date, time (not shown), and day of the week when the customer visited the store. The purpose of visiting a store is information indicating the purpose of a customer visiting a branch office. The visiting branch is information indicating the branch where the customer visited.

The data structure of the employee rotation information stored in the employee rotation DB 114 will be described with reference to FIG. FIG. 6 is an example of the data structure of the employee rotation information. The employee rotation information consists of the holiday sales branch and the names of the holiday workers. The employee rotation information is updated by the employee rotation calculation server 102 at a predetermined time (for example, the end of the month).
Holiday business branch is the name of a branch that operates on holidays. The name of the employee who goes to work on holiday is the name of the employee who goes to work on holiday on each holiday.

With reference to FIG. 7, the data structure of the person in charge necessity determination information stored in the person in charge necessity determination DB 115 will be described. FIG. 7 is an example of the data structure of the person in charge necessity determination information. The person in charge necessity determination information includes the purpose of visiting the store and the person in charge necessity identification information. The purpose of visiting a store is information indicating the purpose of a customer visiting a branch office. The person in charge necessity identification information is information indicating whether or not a person in charge is necessary as a response to a customer. Here, a person in charge is required when the purpose of visiting the store is "insurance," "inheritance," "asset management," and "mortgage," while the purpose of visiting the store is "fixed deposit," "notifications," and ". In the case of "foreign currency deposit", the person in charge is not required.

Next, with reference to FIG. 8, the function of the control unit 301 included in the employee rotation calculation server 102 will be described. FIG. 8 is a functional configuration diagram of the employee rotation calculation server 102. In addition, here, only the outline will be explained, and the details will be described later.
The control unit 301 includes a customer visit management unit 501, a holiday work plan creation unit 505, and a holiday work plan notification unit 506. The customer visit management unit 501, the holiday work plan creation unit 505, and the holiday work plan notification unit 506 are realized, for example, by a program execution process by the CPU.

The customer visit management unit 501 manages the customer's visit to the branch office, and is composed of a store visit purpose management unit 502, a store visit time management unit 503, and a store visit location management unit 504.
The store visit purpose management unit 502 manages the customer's store visit purpose. The store visit purpose management unit 502 predicts the next customer's store visit purpose from, for example, the customer's store visit history.
The store visit time management unit 503 manages the customer's store visit time. The store visit time management unit 503 predicts, for example, the next customer's store visit time from the customer's store visit history.
The store visit location management unit 504 manages the customer's store visit location. The store visit location management unit 504 predicts the next customer visit location, for example, from the customer visit history.

The holiday work plan creation unit 505 prepares a holiday work plan for the next month's employees. The holiday attendance planning unit 505 may use, for example, the purpose of the next customer's visit predicted by the store visit purpose management department 502, the next customer's visit time predicted by the store visit time management department 503, and the next time predicted by the store visit location management department 504. The optimum employee rotation is calculated based on the place where the customer visits the store.
The holiday work plan notification unit 506 notifies the customer terminal 101 and the like of the holiday work plan created by the holiday work plan creation unit 505.

<< Processing of the holiday work planning system according to the embodiment >>
The processing of the holiday work plan creation system 1 according to the embodiment will be described. The process of the holiday work plan creation system 1 according to the embodiment mainly includes "store visit history record process" and "bank employee rotation calculation process".

<Store visit history record processing>
The store visit history recording process will be described with reference to FIG. 9 (see FIGS. 2 and 8 as appropriate). FIG. 9 is an example of a sequence diagram showing the store visit history recording process. The store visit history storage process is a process of accumulating the information that the customer has visited the branch office as a history in the store visit history DB 111. The store visit history recording process is started when the customer visits the branch office and starts the operation of the reception terminal 103.

Customer C inserts a passbook or cash card into the reception terminal 103 (step S11). Here, the passbook / card insertion guidance screen 600 (see FIG. 10) is displayed on the input display unit 401 of the reception terminal 103 as an initial state. On the passbook / card insertion guidance screen 600, a message 601 to the customer, a card insertion position notification symbol 602, and a passbook insertion position notification symbol 603 are displayed. A card insertion slot (not shown) is installed in the direction indicated by the arrow of the card insertion position notification symbol 602, and a passbook insertion slot (not shown) is provided in the direction indicated by the arrow of the passbook insertion position notification symbol 603. Is installed. The customer inserts the passbook or cash card into the card slot or the passbook slot according to the message 601.

Subsequently, the reception terminal 103 acquires an account number from the inserted passbook or card (step S12). The account number shall be temporarily held in the reception terminal 103. After acquiring the account number, the reception terminal 103 ejects the passbook or the card (step S13), and displays the store visit purpose selection screen 700 (see FIG. 11) on the input display unit 401. On the store visit purpose selection screen 700, a message 701 to the customer and eight store visit purpose selection buttons 702, ... Are displayed.

The customer C inputs the store visit purpose by selecting one of the store visit purpose selection buttons 702, ... According to the message 701 of the store visit purpose selection screen 700 (step S14). The reception terminal 103 writes the account number acquired in step S12 and the store visit purpose selected in step S14 in the store visit history DB 111, and receives the response result (step S15). At this time, the store visit history DB 111 also stores information about the store visit date and time and the store visit branch. The information about the store visit branch is set in advance in the reception terminal 103, for example, and the information is sent to the store visit history DB 111. After writing the store visit history, the reception card issuing unit 405 of the reception terminal 103 issues a reception card printed with the reception number according to the selected store visit purpose (step S16).

<Employee rotation calculation process>
The employee rotation calculation process will be described with reference to FIG. 12 (see FIGS. 2 and 8 as appropriate). FIG. 12 is an example of a sequence diagram showing the employee rotation calculation process. In the employee rotation calculation process, the employee rotation is mainly calculated on the holiday of the next month, and the person in charge is notified to the customer terminal 101 scheduled to go to work. The employee rotation calculation process is scheduled to be automatically executed, for example, on a fixed day of each month (for example, the last day of each month), and is started when that day is reached.

On the scheduled day, the customer visit management unit 501 of the employee rotation calculation server 102 requests the holiday work availability DB 112 to acquire the holiday work availability information (see FIG. 3) for the next month, and the holiday attendance availability DB 112 The next month's holiday work availability information is acquired from (step S21). In the subsequent processing of steps S22 to S30, the employee name is referred to from above from the holiday work availability information, and the processing is performed one by one in order. As a result, the subsequent processes of steps S22 to S30 are repeated as many times as the number of employees.

Subsequently, the customer visit management unit 501 requests the customer information DB 113 in charge to acquire the customer information in charge (see FIG. 4) based on the employee name included in the holiday work availability information acquired in step S21. The customer in charge information is acquired from the customer in charge information DB 113 (step S22).

Subsequently, the customer visit management unit 501 determines whether or not there is a customer in charge of the bank employee from the customer information in charge acquired in step S22 (step S23). If there is a customer in charge of the bank employee, the process proceeds to step S24. On the other hand, when there is no customer in charge of the bank employee, the process by the bank employee proceeds to step S29.

Subsequently, the customer visit management unit 501 requests the store visit history DB 111 to acquire the store visit history information (see FIG. 5) based on the name of the customer in charge of the bank employee in step S23, and visits the store from the store visit history DB 111. Acquire history information (step S24). It is preferable to acquire the store visit history information for several months (for example, three months) from the latest.

Subsequently, the customer visit management unit 501 calculates the holiday visit rate and the weekday visit rate for each customer in charge of the bank employee from the store visit history information acquired in step S24. Then, after the calculation, the holiday store visit rate and the weekday store visit rate are compared. When the result of the comparison is "holiday visit rate> weekday visit rate", it is determined that the customer in charge visits the store on a holiday, and the process for the customer proceeds to step S26 (step S25). On the other hand, when the result of the comparison is "holiday visit rate ≤ weekday visit rate", it is determined that the customer in charge does not visit the store on a holiday, and the processing for the customer is terminated. If the comparison result of all the customers in charge of the bank employee is "holiday visit rate ≤ weekday visit rate", the process by the bank employee proceeds to step S29.

Subsequently, the store visit purpose management unit 502 of the employee rotation calculation server 102 determines whether or not the employee in charge (person in charge) needs to respond when the customer who is determined to visit the store on a holiday in step S25 visits the store. (Step S26). Details of the method for determining whether or not a person in charge is required will be described later. The process for the customer determined to be necessary by the person in charge proceeds to step S27. On the other hand, the process for the customer determined that the person in charge is not necessary is terminated. If the judgment results of all the customers in charge of the bank employee do not require the person in charge, the process in the bank employee proceeds to step S29.

Subsequently, the store visit time management unit 503 of the bank employee rotation calculation server 102 predicts the next store visit date and time of the customer in charge from the store visit history information acquired in step S24 (step S27). The details of the method of predicting the visit date and time will be described later.
In addition, the store visit location management unit 504 of the bank employee rotation calculation server 102 predicts the branch office to which the customer in charge will visit next time based on the next store visit date and time predicted in step S27 (step S28). The details of the method of predicting the visiting branch will be described later.

Subsequently, the holiday attendance plan creation unit 505 of the employee rotation calculation server 102 is based on the holiday attendance availability information acquired in step S21 and the information regarding the next visit predicted in steps S26 to S28, and the employee holidays. The attendance plan is determined (step S29). Details of the method for determining the scheduled holiday work date will be described later. Then, the holiday work plan creation unit 505 writes the holiday work plan determined in step S29 into the employee rotation DB 114, and receives the response result (step S30).

Subsequently, the holiday work plan notification unit 506 of the employee rotation calculation server 102 notifies the customer terminal 101 of the name of the employee in charge and the holiday work plan (scheduled work date and branch office) of the employee. (Step S31). The customer terminal 101 displays a notification screen 800 (see FIG. 13) including the name of the person in charge notified from the employee rotation calculation server 102 and the holiday work plan of the employee on the input display unit 201 (step S32).

(Determining the necessity of the person in charge)
The details of the process in step S26 will be described with reference to FIG. First, the store visit purpose management unit 502 of the bank employee rotation calculation server 102 aggregates the store visit purposes for holidays from the store visit history information (see FIG. 5), and sets the most frequent store visit purpose as the "high frequency store visit purpose" of the customer. (Step S41). Subsequently, the store visit purpose management unit 502 determines whether or not there are a plurality of “high-frequency store visit purposes” (step S42). Here, the existence of a plurality of "high-frequency store visit purposes" is, for example, a case where the number of store visit purposes such as "insurance" and "asset management" is the same as a result of totaling the store visit history for the last three months.

When there are a plurality of "high-frequency visit purposes" ("Yes" in step S42), the store visit purpose management unit 502 sets the latest store visit purpose (closer to the latest store visit purpose) as the "high-frequency visit purpose". (Step S43). Then, the process proceeds to step S44. On the other hand, when there are no plurality of "high-frequency visit purposes" (“No” in step S42) or following step S43, the store visit purpose management unit 502 sets the “high-frequency visit purpose” as the next store visit purpose. , It is determined whether or not the person in charge is necessary based on the person in charge necessity determination information (see FIG. 7) (step S44). Then, the store visit purpose management unit 502 sets the determination result as the "person in charge necessity determination result" (step S45).

(Prediction processing of next visit date and time)
The details of the process in step S27 will be described with reference to FIG. First, the store visit time management unit 503 of the employee rotation calculation server 102 aggregates the number of store visits of the customer on holidays on a weekly basis, such as the first to fourth weeks, from the store visit history information (see FIG. 5). The week of visiting the store is defined as the "high-frequency visit week" (step S51). Subsequently, the store visit time management unit 503 determines whether or not there are a plurality of “high frequency store visit weeks” (step S52). Here, the existence of a plurality of "high-frequency visit weeks" is, for example, a case where the number of visit dates in the first week and the second week is the same in the store visit history of the last three months.

When there are a plurality of "high-frequency visit weeks" ("Yes" in step S52), the store visit time management unit 503 sets the week in which the most recent store visit history exists as the "high-frequency visit week" (step S53). ). Then, the process proceeds to step S54. On the other hand, if there are no more than one "high-frequency visit week" (“No” in step S52) or following step S53, the store visit time management department 503 determines the day of the week during the “high-frequency visit week”. The days of the week that are the most visited are set as "high-frequency visit days" (step S54). Subsequently, the store visit time management unit 503 determines whether or not there are a plurality of "high-frequency visit days" (step S55).

When there are a plurality of "high-frequency visit days" ("Yes" in step S55), the store visit time management unit 503 sets the day of the latest visit history as the "high-frequency visit day" (step S56). Then, the employee rotation calculation server 102 sets the "high-frequency visit day of the week" of the "high-frequency visit week" as the "next store visit date and time" (step S57).

(Forecast processing of visiting branches)
The details of the process in step S28 will be described with reference to FIG.
First, the store visit location management unit 504 of the bank employee rotation calculation server 102 extracts a store visit date that matches the predicted “next store visit date and time” from the store visit history information of the previous month (see FIG. 5) (step S61). Then, the store visit location management department 504 sets the extracted branch office on the store visit date as the “next store visit branch” (step S62). For example, if the "next store visit date and time" is predicted to be the second Saturday, the branch that visited the store on the second Saturday of the previous month will be the "next store visit branch". If you did not come to the store in the previous month, go back to the month before last.

(Decision processing of holiday work plan)
The details of the process in step S29 will be described with reference to FIG.
First, the holiday attendance plan creation unit 505 of the employee rotation calculation server 102 determines whether or not there is a customer (customer in charge) in charge of the employee (step S71). If the bank employee has a customer in charge (“Yes” in step S71), the process proceeds to step S72, while if the employee does not have a customer in charge (“No” in step S71), the process proceeds to step S77.

Subsequently, the holiday work plan creation unit 505 determines whether or not there is a customer in charge with a high store visit rate on holidays (step S72). The process proceeds to step S73 when there is a customer in charge with a high store visit rate on holidays (“Yes” in step S72), while the process is stepped when there is no customer in charge in the bank employee (“No” in step S72). Proceed to S77.

Subsequently, the holiday work plan creation unit 505 determines whether or not a person in charge is required at the next visit (step S73). If a person in charge is required at the next store visit (“Yes” in step S73), the process proceeds to step S74, while if a person in charge is not required at the next store visit (“No” in step S73), the process is performed in step S77. Proceed to.

Subsequently, the holiday work plan creation unit 505 determines whether or not it is possible to go to work at the "next visit date and time" of the customer in charge (step S74). If it is possible to go to work on the next store visit date and time (“Yes” in step S74), the process proceeds to step S75, while if it is not possible to go to work on the next store visit date and time (“No” in step S74), the process proceeds to step S77. ..

Subsequently, the holiday work plan creation unit 505 determines whether or not the customer in charge can go to the “next branch” (step S75). The process proceeds to step S76 when it is within the range where the next branch can be reached (“Yes” in step S75), while the process proceeds to step S77 when it is not within the range where the next branch can be visited (“No” in step S75). ..

If it can be determined as "Yes" in steps S71 to S75, the holiday work planning department 505 determines the scheduled work date as the "next visit date and time" and the work location as the "next visit branch" ( Step S76). On the other hand, when it is determined as "No" in any of steps S71 to S74, the scheduled work day is determined based on the contents acquired from the holiday work availability DB 112 (step S77). As for the work place, for example, select a place close to the branch office to which the employee belongs.

As described above, the holiday work plan creation system 1 according to the embodiment predicts the customer's visit date and time and the store visit branch by using the customer's visit history, and calculates the employee rotation. Therefore, even if the customer visits the store without making a reservation, the person in charge can handle it. Therefore, the effect of promoting over-the-counter financial transactions at the holiday sales branch can be obtained.

[Modification example]
Although the embodiments of the present invention have been described above, the present invention is not limited to this, and can be carried out within a range that does not change the gist of the claims. A modified example of the embodiment is shown below.

In the embodiment, the next customer's store visit purpose, store visit time, and store visit location are predicted from the customer's store visit history information, but the customer may be asked to enter the next store visit purpose, store visit time, and store visit location in advance. For example, the customer is asked to directly input the purpose of the next visit, the time of the visit, and the place of visit by using the customer terminal 101 or the reception terminal 103, and the information is stored in the store visit history DB 111. As a result, the store visit history DB 111 stores the store visit information obtained by adding the information regarding the future customer's visit to the information regarding the past customer's visit.

When the bank employee rotation calculation server 102 creates a holiday work plan, the store visit purpose management unit 502 acquires the customer's next store visit purpose stored in the store visit history DB 111 without predicting the next store visit purpose. .. Further, the store visit time management unit 503 acquires the next store visit time of the customer stored in the store visit history DB 111 without predicting the next store visit time. Further, the store visit location management unit 504 acquires the customer's next store visit location stored in the store visit history DB 111 without predicting the next store visit location. Then, the holiday work plan creation unit 505 creates a holiday work plan using the customer's next store visit purpose, store visit time, and store visit location input by the customer. In this case, since the customer's next visit date and time can be known accurately, it is possible to create a more appropriate holiday work plan.

Further, in the embodiment, it is assumed that a bank employee is convened from a nearby branch office that is not open on holidays to take measures. However, the scope to which the present invention can be applied is not limited to this business form, and for example, a plan for employees working on holidays within the same branch may be created.
Further, in the embodiment, a plan for holiday work of a financial institution was created. However, the scope to which the present invention can be applied is not limited to this industry, and it is possible to create a holiday work plan for various business forms (for example, a beauty salon) that are predetermined by the person in charge of the customer. .. Therefore, the person in charge includes a clerk and the like in addition to the employee shown in the embodiment.

1 Holiday work plan creation system 101 Customer terminal 102 Employee rotation calculation server (holiday work plan creation device)
103 Reception terminal 111 Store visit history DB (customer information storage unit)
112 Holiday work availability DB
113 Customer information DB in charge
114 Employee Rotation DB
115 Person in charge necessity judgment DB
501 Customer visit management department 502 Store visit purpose management department 503 Store visit time management department 504 Store visit location management department 505 Holiday work plan creation department 506 Holiday work plan notification department

Claims (6)

A customer information storage unit that stores visit information including past visit dates on holidays, which is related to the customer's past visits.
The store visit time management department that predicts the next store visit time on the customer's holiday from the result of totaling the past visit dates, and
It is equipped with a holiday work plan creation department that creates a holiday work plan for the person in charge of the customer.
The holiday work planning department allocates the next visit time on the customer's holiday as the day when the person in charge goes to work on a holiday.
A holiday work planning system that features this. The store visit information includes past visit locations on holidays.
It is further equipped with a store visit location management department that predicts the store visit location of the past visit date that matches the conditions of the next store visit time as the customer's next store visit location.
The holiday work planning unit, when the next visit location of the customer is in the range that does not commute from belonging to the location of the person in charge, do not assign a holiday work before Symbol person in charge,
The holiday work planning system according to claim 1, wherein the system is characterized by the above. The store visit information includes past store visit purposes on holidays.
The purpose of visiting the store includes a purpose that requires the response of the person in charge and a purpose that does not require the response.
It is further equipped with a store visit purpose management department that predicts the next store visit purpose on the customer's holiday from the result of totaling the past store visit purposes .
The holiday work plan creating section, when the next visit purpose of the customer does not require the correspondence of the person in charge, do not assign a holiday work before Symbol person in charge,
The holiday work planning system according to claim 1 or 2, characterized in that. The store visit time management department, which predicts the next store visit time on the customer's holiday from the result of totaling the customer's past visit dates ,
It is equipped with a holiday work plan creation department that creates a holiday work plan for the person in charge of the customer.
The holiday work planning department allocates the next visit time on the customer's holiday as the day when the person in charge goes to work on a holiday.
A holiday work planning device that is characterized by this. The computer
A store visit time management step that predicts the next store visit time on the customer's holiday from the result of totaling the customer's past store visit dates, and
The holiday work plan creation step of creating the holiday work plan of the person in charge of the customer is executed.
In the holiday work plan creation step , the next visit time on the customer's holiday is assigned as the day when the person in charge goes to work on a holiday.
A method of creating a holiday work plan, which is characterized by this. Computer,
The store visit time management department, which predicts the next store visit time on the customer's holiday from the result of totaling the customer's past visit dates ,
It functions as a holiday work plan creation department that creates a holiday work plan for the person in charge of the customer.
The holiday work planning department allocates the next visit time on the customer's holiday as the day when the person in charge goes to work on a holiday.
A holiday work planning program that features this.

Images