JP5733193B2 - Business management server, business management method, and business management program - Google Patents

Description

  The present invention relates to a business management server, a business management method, and a business management program.

  Conventionally, when a window of a financial institution or a post office is congested, a part of the business originally performed by the operator of the window is delegated to another operator. For example, the business corresponds to the opening of a new account for ordinary savings, cash transfer, and the like. In addition, in the case of opening a new account for an ordinary deposit, this business includes a plurality of transactions in a predetermined order, such as name identification, cash set, account opening, seal registration, and so on. In other words, congestion is alleviated by having other operators act on behalf of a transaction performed by a congested window operator. This transaction order is also called a business flow.

JP 2010-218324 A

  By the way, when a certain operator's transaction is delegated to another operator, it is considered desirable for the other operator to perform the substitution in a form that suppresses the load. This is because, for example, by substituting a transaction that is not originally included in the business originally performed by another operator, there is a possibility that the execution of the business originally performed by the other operator may be hindered.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a business management server, a business management method, and a business management program capable of creating a business flow that can be easily substituted.

  In one aspect, the business management server disclosed in the present application includes a specifying unit, an updating unit, and an output unit. The specifying unit specifies, from the storage unit, a first transaction that may be executed by an operator other than the first operator among a plurality of transactions executed by the first operator. Here, the storage unit stores the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator. When the second transaction of the same type as the first transaction specified by the specifying unit is included in a plurality of transactions executed by the second operator, the update unit performs the following in the execution order of the second operator: Execute the process. That is, the update unit changes the execution order of the second transaction based on the timing at which the first transaction is executed in the execution order of the first operator, and immediately before or immediately after the changed second transaction. One transaction is added, and the execution order of the second operator stored in the storage unit is updated. The output unit outputs the execution order of the second operator updated by the update unit.

  According to one aspect of the technology disclosed in the present application, it is possible to create a business flow that is easy to substitute.

FIG. 1 is a diagram illustrating a configuration of a system according to the first embodiment. FIG. 2 is a functional block diagram illustrating the configuration of the business management server according to the first embodiment. FIG. 3 is a diagram illustrating an example of the data structure of the busy rate table. FIG. 4 is a diagram illustrating an example of the data structure of the transaction table. FIG. 5 is a diagram illustrating an example of the data structure of the business table. FIG. 6 is a diagram illustrating an example of the data structure of the history table. FIG. 7A is a diagram for explaining processing in the updating unit. FIG. 7B is a diagram for explaining processing in the updating unit. FIG. 8A is a diagram for explaining an example of a display screen displayed on the operator terminal by the output unit. FIG. 8B is a diagram for explaining an example of a display screen displayed on the operator terminal by the output unit. FIG. 8C is a diagram for explaining an example of a display screen displayed on the operator terminal by the output unit. FIG. 8D is a diagram for explaining an example of a display screen displayed on the operator terminal by the output unit. FIG. 9 is a flowchart illustrating the processing procedure of the business management server according to the first embodiment. FIG. 10 is a flowchart showing a processing procedure of processing for substituting a transaction. FIG. 11 is a diagram illustrating a computer that executes a business management program.

  Embodiments of a business management server, a business management method, and a business management program disclosed in the present application will be described below in detail with reference to the drawings. In the following embodiment, a case where various operations are executed in a financial institution is taken as an example. However, the present invention is not limited to this. For example, the present invention can be applied to cases where a plurality of operators perform business at a window such as a post office. Note that the present invention is not limited to the embodiments. Each embodiment can be appropriately combined within a range in which processing contents do not contradict each other.

  A configuration of the system according to the first embodiment will be described. FIG. 1 is a diagram illustrating a configuration of a system according to the first embodiment. As shown in FIG. 1, this system includes a business management server 100, operator terminals 10 a, 10 b, 10 c, 10 d, and a reception terminal 20. The business management server 100, the operator terminals 10a to 10d, and the reception terminal 20 are connected via the network 5. The network 5 may be any type of communication network such as the Internet (Internet), LAN (Local Area Network), or VPN (Virtual Private Network), regardless of whether it is wired or wireless. In the example illustrated in FIG. 1, the case where four operator terminals 10 a to 10 d are connected to the business management server 100 is illustrated, but the configuration is not limited to the illustrated configuration. That is, an arbitrary number of operator terminals 10 a to 10 d may be connected to the business management server 100. Hereinafter, the operator terminals 10a, 10b, 10c, and 10d are collectively referred to as the operator terminal 10 when collectively referred to without distinction.

  The operator terminal 10 is a terminal that displays various types of information related to work. For example, the business corresponds to business such as opening a new account for ordinary deposits and cash transfer. Further, if the business is to open a new account for ordinary deposits, a series of transactions included in this business includes name identification, cash set, account opening, seal registration, and the like.

  When the operator terminal 10 receives a business type from the operator, the operator terminal 10 inquires the business management server 100 about information related to the transaction included in the received business type, and sequentially displays the acquired information related to the transaction. The operator refers to the content of the displayed transaction information and inputs data items corresponding to the transaction. The operator terminal 10 transmits a data item corresponding to the transaction to the business management server 100.

  The reception terminal 20 is a terminal that assigns an operator to a customer. For example, the reception terminal 20 automatically issues reception number cards sequentially to customers, and assigns operators to the customers in the order in which the reception number cards are issued.

  The business management server 100 supports the execution of the business performed by the operator on the operator terminal 10. For example, the business management server 100 receives from the operator terminal 10 a business type input to the operator terminal 10 by an operator who has received a slip from a customer. The business management server 100 causes the operator terminal 10 to display a series of transactions related to the accepted type of business.

  Next, the configuration of the business management server 100 according to the first embodiment will be described. FIG. 2 is a functional block diagram illustrating the configuration of the business management server according to the first embodiment. As illustrated in FIG. 2, the business management server 100 includes a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

  The communication unit 110 performs data communication with the operator terminal 10 via the network 5. For example, the communication unit 110 receives the business data selected by the operator and the data input in the transaction data item from the operator terminal 10, and outputs the received information to the control unit 150. In addition, when the communication unit 110 receives data addressed to the operator terminal 10 from the control unit 150, the communication unit 110 transmits the data to the operator terminal 10. The control unit 150 described later exchanges data with the operator terminal 10 via the communication unit 110. The communication unit 110 corresponds to a communication device such as a communication module.

  The input unit 120 is an input device that inputs various types of information. For example, the input unit 120 corresponds to a keyboard, a mouse, and a touch panel. For example, the input unit 120 outputs various types of input information to the control unit 150. The display unit 130 is a display device that displays various types of information. For example, the display unit 130 corresponds to a display or a display with a touch panel. For example, the display unit 130 displays various information output by the control unit 150.

  The storage unit 140 stores a busy rate table 141, a transaction table 142, a business table 143, and a history table 144. The storage unit 140 corresponds to, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk device or an optical disk device.

  The busy rate table 141 stores, for example, the attribute status of the operator and the transaction in progress in association with each other. FIG. 3 is a diagram illustrating an example of the data structure of the busy rate table. As shown in FIG. 3, the busy rate table 141 associates ID, name, store number, store name, and busy rate as the attribute status of the operator, and stores business and transaction in association with each other as in-progress transactions. Among these, ID shows ID (Identification) which identifies an operator. The name indicates the name of the operator. The store number indicates a number for identifying a store where the operator is registered. The store name indicates the name of the store that identifies the store in which the operator is registered. The busy rate is a value corresponding to the busyness of the operator, and is calculated by the execution unit 151 described later. The operation indicates an operation that is currently in progress by the operator. The transaction indicates a transaction that is currently in progress by the operator.

  As shown in FIG. 3, the busy rate table 141 includes, for example, an ID “10011”, a name “Fina Mina”, a store number “101”, a store name “main store”, a busy rate “100%”, and a business “create a new ordinary deposit”. The transaction “name identification” is stored in association with each other. In other words, in the busy rate table 141, the operator “Mina Fuji” with the ID “10011” is enrolled in the head office with the store number “101”, and is currently collating a new savings account, and the busy rate is 100%. Remember. The busy rate table 141 stores the busy rate and the like for other operators as well.

  For example, the transaction table 142 stores a business and a transaction included in the business in association with each other. FIG. 4 is a diagram illustrating an example of the data structure of the transaction table. As shown in FIG. 4, the transaction table 142 stores business and transactions in association with each other. Further, the transaction table 142 stores (1), (2), (3),... This number corresponds to the order in which each transaction is executed in the business. Further, the transaction table 142 stores three flags in association with each transaction. These three flags correspond to the takeover data section, the change section, and the proxy section from the left in the figure. The takeover data category indicates whether there is data to be taken over from the immediately preceding transaction. For example, in the takeover data section, “1” is stored when there is data to be taken over from the immediately preceding transaction, and “0” is stored when there is no data. The variation category indicates whether or not the order of the corresponding transaction can be changed. For example, in the change category, “1” is stored when the order can be changed, and “0” is stored when the order cannot be changed. The proxy classification indicates whether an operator other than the operator who originally performs the transaction can perform the proxy. For example, “1” is stored in the substitution section when substitution is possible, and “0” is stored when substitution is impossible. The execution order of a plurality of transactions included in a business is also referred to as a business flow.

  As shown in FIG. 4, the transaction table 142 includes business “new savings deposit”, transaction (1) “name identification”, transaction (2) “passbook set”, transaction (3) “seal verification”, transaction (4). Store “Title Approval” in association. In other words, the transaction table 142 indicates that in the business “new savings creation”, each transaction is executed in the order of (1) name identification, (2) passbook set, (3) seal verification, and (4) office approval. Record. Further, the transaction table 142 stores (3) seal verification, the takeover data category “0”, the variation category “1”, and the proxy category “1” in association with each other. That is, the transaction table 142 stores that there is no data that the seal collation should take over from the immediately preceding transaction, the order can be changed, and an operator other than the operator who originally performs the seal collation can act. Since the transaction “name identification” is the first transaction in the business flow, it does not have data to be transferred. However, since the transaction is performed by receiving a slip from the customer, “1” is included in the name identification transfer data classification. Stored. The transaction table 142 stores each transaction included in the business in the same manner for other business.

  The business table 143 stores, for example, an operator, a business executed by the operator, and a transaction included in the business in association with each other. FIG. 5 is a diagram illustrating an example of the data structure of the business table. As illustrated in FIG. 5, the business table 143 stores IDs, businesses, and transactions in association with each other. In addition, the business table 143 stores a start time and an end time in association with each transaction. As the start time and the end time, for example, an estimated time is stored when the corresponding transaction is not processed, and the actual time is stored every time the transaction is actually started or ended. Note that the estimated time of each transaction is calculated from, for example, the average of the time required for each transaction processed in the past.

  As shown in FIG. 5, the business table 143 includes an ID “10011”, a business “create a new ordinary deposit”, a transaction (1) “name identification”, a transaction (2) “passbook set”, and a transaction (3) “seal verification”. Transaction (4) “Title approval” is stored in association. In other words, in the business table 143, the operator with the ID “10011” is currently referred to as “1) name identification, (2) passbook set, (3) seal verification, and (4) office approval. Record that they are running in order. The business table 143 stores business and each transaction included in the business in association with each other similarly.

  The history table 144 stores, for example, an operator and a job processed by the operator in association with each other. FIG. 6 is a diagram illustrating an example of the data structure of the history table. As illustrated in FIG. 6, the history table 144 stores the attribute status of the operator and the history record in association with each other. The attribute status of the operator includes ID, name, store number, store name, and other information. Of these, information such as the skill of the operator is stored in the other information. The history record includes a completion category, a business, and a transaction. Among these, the completion classification is a flag indicating whether or not the corresponding record is completed. For example, the completion classification “1” indicates that the corresponding record is completed, and “0” indicates that the record is not completed, that is, a record to be executed.

  As shown in FIG. 6, the history table 144 stores ID “10011”, name “Fuji Mina”, store number “101”, store name “main store”, and other information “skills” as the operator's attribute status. To do. In addition, the history table 144 includes, as the first history record, a completion category “1”, a business “create a new ordinary deposit”, a transaction (1) “name identification”, a transaction (2) “passbook set”, a transaction (3) “Seal verification”, transaction (4) “approval approval” are stored in association with each other. That is, the history table 144 stores that the operator “Mina Fuji” with the ID “10011” is enrolled in the head office with the store number “101” and has skills and the like. In addition, the history table 144 shows that the operator “Mina Fuji” with ID “10011” indicates that the business “creates a new ordinary deposit” (1) name identification, (2) passbook set, (3) seal verification, (4) office position It memorizes what was executed in the order of approval. Also, the history table 144 stores “1327/1330” in association with (3) seal verification of the first history record, for example. That is, the history table 144 stores that (3) seal collation of the first history record started at 13:27 and ended at 13:30. The history table 144 similarly stores other history records. In this example, the history table 144 stores the history record of the operator with ID “10011”, but the history table 144 similarly stores the history records for the operators with other IDs.

  The control unit 150 includes an execution unit 151, a specification unit 152, an update unit 153, and an output unit 154. The function of the control unit 150 can be realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Further, the function of the control unit 150 can be realized by, for example, a CPU (Central Processing Unit) executing a predetermined program.

  The execution unit 151 receives the type of work executed by the operator from the operator terminal 10. The execution unit 151 acquires information related to transactions included in the received type of business from the transaction table 142. The execution unit 151 expands information about the acquired transaction in the business table 143.

  For example, the execution unit 151 receives the business “create a new ordinary deposit” from the operator terminal 10 operated by the operator with the ID “10011”. The execution unit 151 obtains (1) name identification, (2) passbook set, (3) seal verification, and (4) office approval as transactions included in the business “create new ordinary deposit”. To do. The execution unit 151 associates the operator ID, the business, and the transaction with each other and expands it in the business table 143 of FIG.

  Further, every time a transaction is executed on the operator terminal 10, the execution unit 151 stores the start time and the end time of the executed transaction in the business table 143, and the device of the busy rate table 141 in FIG. Update medium transactions. If the transaction executed on the operator terminal 10 is the final transaction in the business flow, the execution unit 151 writes the transaction developed in the business table 143 in the history table 144.

  Further, the execution unit 151 calculates a busy rate and stores the calculated busy rate in the busy rate table 141. For example, the execution unit 151 acquires a transaction in progress from the busy rate table 141. The execution unit 151 is required for the transaction that was executed 30 minutes before the current time and the transaction that is scheduled to be completed 30 minutes after the current time, based on the acquired transaction in progress. Time is acquired from the history table 144. The execution unit 151 adds the time required for the transaction executed up to 30 minutes before and the time required for the transaction scheduled up to 30 minutes later, and the ratio of the added value in 60 minutes is the busy rate. Calculate as The busy rate calculated here corresponds to the degree of busyness for each operator. Further, the busy rate calculation method described here is an example, and may be obtained by another calculation method. For example, the execution unit 151 refers to the history table 144 and calculates the time difference between the transaction end time and the transaction start time of the acquired transaction in progress. When the time difference is 60 minutes or more, the execution unit 151 sets the busy rate to 100%, and when the time difference is less than 60 minutes, the execution unit 151 uses the value obtained by dividing the time difference by 60 minutes multiplied by 100 as the busy rate. Good.

  The identifying unit 152 identifies a transaction that may be executed by another operator other than the operator, out of operations performed by a certain operator. For example, the specifying unit 152 refers to the business table 143 and detects an operator A having a busy rate equal to or higher than a threshold. The identifying unit 152 determines whether or not there is a transaction that can be substituted and changed in the detected business flow of the operator A. The operator A is an example of a “first operator”. Further, a transaction that can be substituted and can be changed is also referred to as a “proxy transaction”. The agency transaction is an example of a “first transaction”.

  For example, the identifying unit 152 refers to the busy rate table 141 in FIG. 3 and detects an operator with ID “10011” as an operator whose busy rate is equal to or greater than the threshold “100%”. The identifying unit 152 refers to the busy rate table 141 and identifies that the task being processed by the operator with the ID “10011” is “create new ordinary deposit”. The identifying unit 152 refers to the transaction table 142 of FIG. 4 and identifies the transaction “seal verification” corresponding to the agency category “1” and the variation category “1” from the business flow of “create new ordinary deposit”. The identification unit 152 outputs information related to the identified transaction to the update unit 153. The threshold value is a value for detecting an operator with a high degree of busyness, and may be set to an arbitrary value by a person who manages the business management server 100.

  For example, the update unit 153 determines whether there is an operator B who has a busy rate less than the threshold and plans to execute the same type of transaction as the agency transaction specified by the specifying unit 152. Here, the same type of transaction as the proxy transaction is also referred to as “same transaction”. When there is an operator B who is scheduled to execute the same transaction, the update unit 153 determines whether or not the execution of the same transaction can be started at the timing of starting the execution of the agency transaction in the business flow of the operator B. When the execution of the same transaction can be started at the timing of starting the execution of the agency transaction, the update unit 153 continuously executes the business flow of the operator B with the same transaction as the agency transaction at the timing of starting the execution of the agency transaction. Change to do. The update unit 153 deletes the agency transaction from the business flow of the operator A. The operator B is an example of a “second operator”. The same transaction is an example of a “second transaction”.

  Processing in the updating unit will be described with reference to FIGS. 7A and 7B. 7A and 7B are diagrams for explaining processing in the updating unit. 7A shows an example of the business table 143 before being updated by the update unit 153, and FIG. 7B shows an example of the business table 143 after being updated by the update unit 153. In the example illustrated in FIGS. 7A and 7B, a case where the transaction (3) “seal verification 7a” of the operator with ID “10011” is specified as a proxy transaction will be described. In FIGS. 7A and 7B, it is assumed that the update unit 153 is executing processing at 14:00.

  For example, the update unit 153 refers to the busy rate table 141 in FIG. 3 and detects an operator with ID “10021” as an operator whose busy rate is less than the threshold “70%”. As illustrated in FIG. 7A, the update unit 153 refers to the business table 143 and identifies the same transaction “seal verification 7b” in the business flow of the operator with the ID “10021”. The update unit 153 determines whether the execution start of the seal collation 7b can be changed to the execution start timing of the seal collation 7a in the business flow of the operator of ID “10021”. For example, the update unit 153 identifies the transaction “cash set 7c” and “data input 7d” that are started before the start time “14: 5” of the seal collation 7a from the business flow of the operator with ID “10021”. The update unit 153 can refer to the transaction table 142 of FIG. 4 and change the timing of starting the seal verification 7b immediately before the transaction “cash set 7c” in which the transfer data classification is “0” among the specified transactions. It is determined that The update unit 153 changes the workflow of the operator with ID “10021” so that the seal verification 7a and the seal verification 7b are continuously performed at the timing of the seal verification 7a. For example, the update unit 153 changes the seal collation 7b immediately before the cash set 7c, and adds the seal collation 7a immediately before that. That is, as shown in FIG. 7B, the update unit 153 changes the business flow of the operator with ID “10021” to (1) name identification, (2) form reading, (3) seal verification 7a, (4) seal verification 7b, (5) Change to the order of cash set 7c, (6) data input 7d. The update unit 153 deletes the seal verification 7a from the business flow of the operator with ID “10011”. In this way, the update unit 153 changes the business flow of the operator with ID “10011” and the operator with ID “10021”, and updates the business table 143. Here, the start time of the proxy transaction is used when changing the same transaction to the timing of the proxy transaction, but the present invention is not limited to this method. For example, the update unit 153 may use the end time of the agency transaction. Here, the seal stamp collation 7a is added immediately before the seal stamp collation 7b. However, the update unit 153 may add the seal stamp collation 7a immediately after the seal stamp collation 7b.

  The output unit 154 outputs the transaction developed in the business table 143 to the operator terminal 10 for display. For example, the output unit 154 outputs the business flow developed in the business table 143 by the execution unit 151 to the operator terminal 10 and displays the business flow on the progress bar of the operator terminal 10.

  An example of a display screen displayed on the operator terminal 10 by the output unit 154 will be described with reference to FIGS. 8A to 8D. 8A to 8D are diagrams for explaining an example of a display screen displayed on the operator terminal by the output unit. Here, the operator with ID “10011” operates the operator terminal 10a, and the operator with ID “10021” operates the operator terminal 10b. FIG. 8A corresponds to the display screen displayed on the operator terminal 10a based on the business flow of the operator with ID “10011” shown in FIG. 7A. FIG. 8B corresponds to the display screen displayed on the operator terminal 10b based on the business flow of the operator with ID “10021” shown in FIG. 7A. FIG. 8C corresponds to the display screen displayed on the operator terminal 10a based on the business flow of the operator with ID “10011” shown in FIG. 7B. FIG. 8D corresponds to the display screen displayed on the operator terminal 10b based on the business flow of the operator with ID “10021” shown in FIG. 7B.

  As shown in FIGS. 8A and 8C, when the business table 143 is updated by the update unit 153, the output unit 154 displays the progress bar 8a from which the seal verification 7a has been deleted on the display screen of the operator terminal 10a. As shown in FIGS. 8B and 8D, when the business table 143 is updated, the output unit 154 is changed so that the seal collation 7a and the seal collation 7b are continuously executed at the timing of the seal collation 7a. The progress bar 8b is displayed on the display screen of the operator terminal 10b. The progress bars 8a and 8b display an indicator indicating a transaction that is currently in progress.

  Next, a processing procedure of the business management server 100 according to the first embodiment will be described. FIG. 9 is a flowchart illustrating the processing procedure of the business management server according to the first embodiment. The process shown in FIG. 9 is executed each time a reception number card is issued by the reception terminal 20, for example.

  As shown in FIG. 9, for example, the business management server 100 causes the reception terminal 20 to issue a reception number card (step S101), and assigns operators to customers in the order in which the reception number cards are issued (step S102).

  The business management server 100 acquires, from the transaction table 142, information related to the transaction included in the type of business input to the operator terminal 10 by the operator (step S103). The business management server 100 expands information about the acquired transaction in the business table 143 (step S104). The business management server 100 outputs information related to the transaction developed in the business table 143 to the operator terminal 10 and displays it on the progress bar of the operator terminal 10 (step S105).

  When a transaction is executed at the operator terminal 10 (step S106), the business management server 100 stores the start time and end time of the executed transaction in the business table 143 (step S107). The business management server 100 updates the transaction in progress in the busy rate table 141 (step S108).

  If it is not the final transaction (step S109, No), the business management server 100 proceeds to the process of step S106. On the other hand, when the transaction is the final transaction (step S109, Yes), the transaction management server 100 writes the transaction expanded in the transaction table 143 to the history table 144 (step S110), and ends the process.

  Next, the process procedure of the process of substituting a transaction will be described. FIG. 10 is a flowchart showing a processing procedure of processing for substituting a transaction. The process illustrated in FIG. 10 is executed at a predetermined cycle, for example.

  When the business management server 100 refers to the busy rate table 141 and detects an operator A whose busy rate is equal to or greater than a threshold (Yes in step S201), the business flow of the operator A includes a proxy transaction that can be delegated and can be changed. It is determined whether or not there is (step S202). In addition, the business management server 100 complete | finishes a process, when the operator A whose busy rate is more than a threshold value is not detected (step S201, No).

  If there is an agency transaction (Yes in step S202), the business management server 100 refers to the business table 143, and is there an operator B who is busy and has a busy rate less than a threshold and is scheduled to execute the same transaction as the agency transaction? It is determined whether or not (step S203). In addition, the business management server 100 complete | finishes a process, when there is no agency transaction (step S202, No).

  If there is an operator B who is scheduled to execute the same transaction (Yes in step S203), the business management server 100 determines whether or not the same transaction can be changed to a proxy transaction timing in the business flow of the operator B ( Step S204). In addition, the business management server 100 complete | finishes a process, when the operator B who is going to perform the same transaction does not exist (step S203, No).

  When the business management server 100 can change the same transaction to the timing of the agency transaction (step S204, Yes), the business flow of the operator B is continuously processed as the agency transaction and the same transaction at the timing of the agency transaction. It changes so that it may perform (step S205). The business management server 100 deletes the agency transaction from the business flow of the operator A (step S206). In addition, the business management server 100 complete | finishes a process, when the same transaction cannot be changed to the timing of a substitute transaction (step S204, No).

  Of the processing procedures described above, the process of step S204, which is a process for determining whether or not the same transaction can be changed to the timing of the proxy transaction, is not necessarily executed. That is, the process of step S205 may be executed after the process of step S203 is executed.

  Further, the above-described processing procedures do not necessarily have to be executed in the above order. For example, after the process of step S204 is executed, the process of step S206 may be executed, and finally the process of step S205 may be executed.

  Next, a processing procedure of the business management server 100 according to the first embodiment will be described. The business management server 100 identifies, from the storage unit, a first transaction that may be executed by an operator other than the first operator among a plurality of transactions executed by the first operator. Here, the storage unit stores the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator. When the second transaction of the same type as the identified first transaction is included in a plurality of transactions executed by the second operator, the business management server 100 performs the following processing in the execution order of the second operator. Run. The business management server 100 changes the execution order of the second transaction based on the timing at which the first transaction is executed in the execution order of the first operator, and immediately before or immediately after the second transaction. The transaction is added, and the execution order of the second operator stored in the storage unit is updated. The business management server 100 outputs the updated execution order of the second operator. Therefore, the business management server 100 can create a business flow that is easy to substitute. For example, since the business management server 100 changes the business flow of the second operator so that the first transaction and the second transaction are executed continuously, a business flow that is easy for the second operator to create is created. can do.

  Further, for example, the business management server 100 changes the execution order of the first transaction and the second transaction based on the timing at which the first transaction is executed in the execution order of the first operator. It is possible to create a business flow that does not delay the work of the operator.

  Further, the business management server 100 changes the execution order of the second transaction immediately before the transaction that does not require taking over data from the transaction immediately before each transaction among the plurality of transactions of the second operator. For this reason, since the business management server 100 does not change the second transaction immediately before the transaction that requires data to be taken over from the transaction immediately before each transaction, the business management server 100 creates a business flow that is easy to substitute for the second operator. be able to.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in other embodiments besides the above-described embodiments. Therefore, other embodiments will be described below.

  For example, in the first embodiment, a case has been described in which the business management server 100 substitutes a transaction that can be substituted and can be changed as a substitution transaction, but the present invention is not limited to this. For example, the business management server 100 may proxy a transaction that can be performed, that is, the transaction classification is “1” as a proxy transaction.

  Further, for example, in the present invention, it is not necessary that the operator terminals 10a to 10d are arranged in the same store. In other words, for example, the business management server 100 may assign the transaction of the operator A to the operator B at another sales office.

  Further, for example, among the processes described in the first embodiment, all or part of the processes described as being automatically performed can be manually performed, or have been described as being manually performed. All or a part of the processing can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified. For example, the busy rate table 141 does not necessarily have to store a name, a store number, a store name, and the like.

  Further, each component of the business management server 100 shown in FIG. 2 is functionally conceptual and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of the business management server 100 is not limited to the illustrated one, and all or a part thereof can be functionally or physically functioned in arbitrary units according to various loads and usage conditions. It can be configured to be distributed and integrated. For example, the functions of the specifying unit 152 and the updating unit 153 illustrated in FIG. 2 can be integrated and configured.

  The business management server 100 can also be realized by installing each function of the business management server 100 in a known information processing apparatus. Known information processing apparatuses correspond to apparatuses such as personal computers and workstations, for example.

  FIG. 11 is a diagram illustrating a computer that executes a business management program. As illustrated in FIG. 11, the computer 300 includes a CPU 301 that executes various arithmetic processes, an input device 302 that receives data input from a user, and a monitor 303. The computer 300 also includes a medium reading device 304 that reads a program or the like from a storage medium, an interface device 305 for connecting to another device, and a wireless communication device 306 for connecting to another device wirelessly. The computer 300 also includes a RAM (Random Access Memory) 307 that temporarily stores various types of information and a hard disk device 308. Each device 301 to 308 is connected to a bus 309.

  The hard disk device 308 stores a business management program having the same functions as the processing units of the specifying unit 152, the updating unit 153, and the output unit 154 shown in FIG. The hard disk device 308 stores various data for realizing a business management program.

  The CPU 301 reads out each program stored in the hard disk device 308, develops it in the RAM 307, and executes it to perform various processes. In addition, these programs can cause the computer to function as the specifying unit 152, the updating unit 153, and the output unit 154 illustrated in FIG.

  Note that the above-described business management program is not necessarily stored in the hard disk device 308. For example, the computer 300 may read and execute a program stored in a computer-readable recording medium. The computer-readable recording medium corresponds to, for example, a portable recording medium such as a CD-ROM, a DVD disk, a USB (Universal Serial Bus) memory, a semiconductor memory such as a flash memory, a hard disk drive, and the like. Further, the program may be stored in a device connected to a public line, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), etc., and the computer 300 may read and execute the program therefrom. good.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Supplementary Note 1) From the storage unit that stores the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, A specifying unit that identifies a first transaction that an operator other than the first operator may execute among a plurality of transactions executed by one operator;
When a second transaction of the same type as the first transaction specified by the specifying unit is included in a plurality of transactions executed by the second operator, the first operator executes the first transaction in the execution order of the second operator. The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of the operator, and the first transaction is executed immediately before or immediately after the changed second transaction. An update unit that updates the execution order of the second operator stored in the storage unit,
An output unit that outputs the execution order of the second operator updated by the updating unit.

(Additional remark 2) The said update part changes the execution order of said 2nd transaction just before the transaction which does not require taking over data from the transaction immediately before the said transaction among a plurality of transactions of said 2nd operator The business management server according to appendix 1, wherein:

(Appendix 3) A business management method executed by a computer,
From the storage unit for storing the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, the first operator Identify a first transaction that an operator other than the first operator may execute among a plurality of transactions to be executed,
When a second transaction of the same type as the first transaction specified by the specifying process is included in a plurality of transactions executed by the second operator, in the execution order of the second operator, the second transaction The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of one operator, and the first transaction is executed immediately before or immediately after the changed second transaction. Add a transaction, update the execution order of the second operator stored in the storage unit,
The business management method, wherein the execution order of the second operator updated by the updating process is output.

(Additional remark 4) The said process to update is immediately before the transaction which does not require taking over data from the transaction immediately before this transaction among a plurality of transactions of said 2nd operator in the execution order of said 2nd transaction. The business management method according to attachment 3, wherein the business management method is changed.

(Appendix 5)
From the storage unit for storing the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, the first operator Identify a first transaction that an operator other than the first operator may execute among a plurality of transactions to be executed,
When a second transaction of the same type as the first transaction specified by the specifying process is included in a plurality of transactions executed by the second operator, in the execution order of the second operator, the second transaction The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of one operator, and the first transaction is executed immediately before or immediately after the changed second transaction. Add a transaction, update the execution order of the second operator stored in the storage unit,
A business management program for executing each process for outputting the execution order of the second operator updated by the updating process.

(Additional remark 6) The process to update is the execution order of said 2nd transaction immediately before the transaction which does not require taking over data from the transaction immediately before this transaction among a plurality of transactions of said 2nd operator. The business management program according to appendix 5, wherein the business management program is changed.

5 Network 10, 10a, 10b, 10c, 10d Operator terminal 20 Reception terminal 100 Business management server 110 Communication unit 120 Input unit 130 Display unit 140 Storage unit 141 Busy rate table 142 Transaction table 143 Business table 144 History table 150 Control unit 151 Execution Unit 152 Identification unit 153 Update unit 154 Output unit 300 Computer 301 CPU
302 Input Device 303 Monitor 304 Medium Reading Device 305 Interface Device 306 Wireless Communication Device 307 RAM
308 Hard disk device 309 Bus

Claims (4)

From the storage unit for storing the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, the first operator A specifying unit that identifies a first transaction that an operator other than the first operator may execute among a plurality of transactions to be executed;
When a second transaction of the same type as the first transaction specified by the specifying unit is included in a plurality of transactions executed by the second operator, the first operator executes the first transaction in the execution order of the second operator. The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of the operator, and the first transaction is executed immediately before or immediately after the changed second transaction. An update unit that updates the execution order of the second operator stored in the storage unit,
An operation management server comprising: an output unit that outputs the execution order of the second operator updated by the update unit.   The update unit changes the execution order of the second transaction immediately before a transaction that does not require taking over data from a transaction immediately before the transaction among the plurality of transactions of the second operator. The business management server according to claim 1. A business management method executed by a computer,
From the storage unit for storing the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, the first operator Identify a first transaction that an operator other than the first operator may execute among a plurality of transactions to be executed,
When a second transaction of the same type as the first transaction specified by the specifying process is included in a plurality of transactions executed by the second operator, in the execution order of the second operator, the second transaction The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of one operator, and the first transaction is executed immediately before or immediately after the changed second transaction. Add a transaction, update the execution order of the second operator stored in the storage unit,
The business management method, wherein the execution order of the second operator updated by the updating process is output. On the computer,
From the storage unit for storing the execution order of a plurality of transactions included in the business executed by the first operator and the execution order of the plurality of transactions included in the business executed by the second operator, the first operator Identify a first transaction that an operator other than the first operator may execute among a plurality of transactions to be executed,
When a second transaction of the same type as the first transaction specified by the specifying process is included in a plurality of transactions executed by the second operator, in the execution order of the second operator, the second transaction The execution order of the second transaction is changed based on the timing at which the first transaction is executed in the execution order of one operator, and the first transaction is executed immediately before or immediately after the changed second transaction. Add a transaction, update the execution order of the second operator stored in the storage unit,
A business management program for executing each process for outputting the execution order of the second operator updated by the updating process.

Images