JP2020003905A - Rpa device, rpa system and program - Google Patents

Abstract

To provide an RPA device, an RPA system and a program that actualize one transaction by associating a plurality of pieces of software based upon robotic process automation (RPA).SOLUTION: An RPA device executes: a first process of acquiring a first output corresponding to an operation result of first software from the first software based upon RPA; and a second process of executing second software based upon RPA on the basis of the first output so as to generate a second output corresponding to an operation result of the second software.SELECTED DRAWING: Figure 2A

Description

  The present disclosure relates to an RPA device, an RPA system, and a program related to robotic process automation (RPA).

  In a computer system that executes a single task by appropriately starting and terminating a plurality of different software, various tasks required from the start to the end of the task are activated and terminated in the order of the task process, and the task is standardized. There is known a technology for making business efficient and efficient (for example, see Patent Document 1).

JP-A-09-097172

  However, it is difficult to link a plurality of software based on RPA (robotic process automation) with the above-described conventional technology. For example, it is highly convenient if software based on a plurality of RPAs can execute a task (for example, exchange of e-mail) executed in cooperation in different places in a similar cooperation mode. Further, even when a series of tasks is executed by one piece of software based on RPA, the user may want to check or change parameters and the like generated during the series of tasks each time. In this case, if a similar task can be realized by linking a plurality of RPA-based software instead of one RPA-based software, it is possible to meet the needs of the user.

  Therefore, in one aspect, an object of the present invention is to link a plurality of software based on RPA.

According to one aspect, a first process of obtaining a first output according to an operation result of the first software from first software based on robotic process automation (RPA),
An RPA device is provided that executes a second process for generating a second output according to an operation result of the second software by operating second software based on the RPA based on the first output.

  In one aspect, according to the present invention, it is possible to link a plurality of software based on RPA.

It is an explanatory view of conventional RPA software. It is a conceptual explanatory view (the 1) of cooperation of a plurality of software based on RPA. It is a conceptual explanatory view (the 2) of cooperation of a plurality of software based on RPA. It is a figure which shows roughly the flow of operation which the user performed when building the remittance RPA software of the remittance side. It is explanatory drawing of the example of the mail main text which concerns on a remittance mail. FIG. 4 is an explanatory diagram of remittance RPA software constructed based on the operation flow shown in FIG. 3. It is a figure which shows roughly the flow of the operation which the user performed when constructing the payment RPA software of the receiving side. It is explanatory drawing of the example of the mail text which concerns on the mail which notifies the payment confirmation result to the effect that payment was confirmed. It is explanatory drawing of the example of the mail text which concerns on the mail which notifies the payment confirmation result to the effect that payment could not be confirmed. FIG. 7 is an explanatory diagram of deposit RPA software constructed based on the operation flow shown in FIG. 6. It is a figure showing roughly composition of payment RPA software by other examples. FIG. 1 is a schematic diagram showing an entire RPA system. FIG. 2 is a diagram illustrating an example of a hardware configuration of an RPA device. It is a functional block diagram for explaining each function of two RPA devices cooperating. It is a conceptual explanatory view of software based on RPA.

  Hereinafter, each embodiment will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a conceptual explanatory diagram of software based on RPA. FIG. 1 is an explanatory diagram of the remittance RPA software RPA6 'constructed according to the comparative example. In the remittance RPA software RPA6 'constructed according to the comparative example, steps S500 to S506, steps S522 to S527, and steps S532 and S534 are executed at once without "pause (pause)".

Specifically, the remittance RPA software RPA6 'is for the user to send a remittance and to notify the remittee of the remittance by e-mail to the remittance destination, and the following steps S500 to S506 are performed. , Steps S522 to S527, and steps S532 and S534.
Step S500: Bank application AP1 activation step S502: Log in to bank application AP1 Step S504: Remittance destination account instruction step S506: Remittance amount instruction step S522: One-time password application activation step S524: Remittance instruction step S526: Mail application M1 activation step S527: Destination instruction step S532: Text content instruction step S534: Transmission instruction Here, as the account instruction of the remittance destination in step S504, the account of the remittance destination when the remittance RPA software RPA6 'is constructed is indicated. The remittance amount instruction in S506 indicates the remittance amount when the remittance RPA software RPA6 'is constructed, and the destination instruction in step S527 indicates the destination when the remittance RPA software RPA6' is constructed. Will be.

  In such a comparative example, the user cannot check or correct the remittance destination account, remittance amount, destination, and the like.

  As described above, conventionally, the RPA software does not have a function of executing a series of processes at a stretch and forming a pause state on the way. Conventionally, each RPA software is configured to operate individually, and is not configured to operate in cooperation.

  FIG. 2A and FIG. 2B are conceptual explanatory diagrams of cooperation of a plurality of software based on RPA.

  2A and 2B show the RPA software RPA4, RPA5, and RPA6, and the display device 10. FIG. 2B further shows the display device 14, the input device 15, and the parameter correction program PR1.

  In FIG. 2A, as an example, it is assumed that the RPA software RPA4, RPA5, and RPA6 are mounted on different user terminals (not shown) (an example of a first terminal and a second terminal). For example, the user of the RPA software RPA4 is different from the user of the RPA software RPA5. The user terminal is, for example, a smartphone, a tablet terminal, a personal computer, a wearable terminal, or the like.

  In FIG. 2A, the RPA software RPA4 is configured to receive an input and output a first output. The first output is an arbitrary parameter, and may be, for example, an image, a character, a sound, or the like. The first output may be output in the form of a file or a mail. The RPA software RPA5 is configured to operate based on the first output and output a second output. The second output is an arbitrary parameter, and may be, for example, an image, a character, a sound, or the like. The second output may be output in the form of a file or a mail. The second output may be provided to, for example, the RPA software RPA4, may be displayed on the display device 10, or may be provided to another RPA software RPA6.

  In FIG. 2B, as an example, it is assumed that the RPA software RPA4 and RPA5 are mounted on the same user terminal (not shown), and the RPA software RPA6 is mounted on a user terminal different from the RPA software RPA4 and RPA5.

  Similarly, in FIG. 2B, the RPA software RPA4 is configured to receive an input and output a first output. The RPA software RPA5 is configured to operate based on the first output and output a second output. The second output may be provided to, for example, the RPA software RPA4, may be displayed on the display device 10, or may be provided to another RPA software RPA6.

  Thus, in the present embodiment, it is possible to link a plurality of software based on RPA. For example, as shown in FIG. 2A, tasks (for example, exchange of e-mails) executed while cooperating in different places can be realized in a similar cooperative manner by RPA software RPA4 and RPA5.

  Further, for example, when a series of tasks is executed by the RPA software RPA4 or RPA5, the user may want to check or change parameters (first output) generated in the course of the series of tasks every time. In this case, as shown in FIG. 2B, the first output from the RPA software RPA4 is output to the display device 14 by the parameter correction program PR1. The user checks the first output on the display device 14, and corrects the first output output by the parameter correction program PR1 using the input device 15 as necessary. Note that the input device 15 may be an input device that uses a gesture recognition engine, a voice recognition engine, or the like, in addition to a keyboard and a touch switch. Thereafter, the user uses the input device 15 to give an OK instruction to the parameter correction program PR1. Upon receiving the OK instruction from the user, the parameter correction program PR1 provides the RPA software RPA5 with a first output (if modified, the modified first output). In this way, by providing a pause (pause) period after the operation of the RPA software RPA4 and before the operation of the RPA software RPA5, the user can output parameters and the like (first output) generated during a series of operations. It is possible to meet the user's need to check or change.

  Next, a specific example will be described with reference to FIGS. 3A and 3B together with FIGS. 2A and 2B.

  In FIG. 3 and subsequent figures, as an example, the cooperation between the RPA software RPA6 on the remittance side (user U1) and the RPA software RPA7 on the remittance side (user U2) will be described. Further, the cooperation between the respective RPA software RPAs 6-1, 6-2 and 6-3 in the RPA software RPA6 and the cooperation between the respective RPA software RPAs 7-1 and 7-2 in the RPA software RPA7 will also be described. Hereinafter, the RPA software on the remittance side, such as the RPA software RPA6, is also referred to as “remittance RPA software”, and the RPA software on the remittance side, such as the RPA software RPA7, is also referred to as “payment RPA software”.

  FIG. 3 is a diagram schematically illustrating a flow of operations performed by the user U1 when constructing the remittance RPA software RPA6.

  In step S300, the user U1 starts an application of the bank A1 (hereinafter, referred to as “bank application AP1”) on a user terminal (for example, a smartphone).

  In step S302, the user U1 inputs a password or the like and logs in to the bank application AP1.

  In step S304, the user U1 instructs (inputs) a remittance destination account to the bank application AP1. For example, the user U1 selects a remittance destination account from a plurality of registered account information.

  In step S306, the user U1 instructs (inputs) a remittance amount to the bank application AP1. For example, the user U1 manually inputs a remittance amount.

  In step S308, the user U1 activates an application for issuing a one-time password. The application that issues the one-time password may be different from the bank application AP1.

  In step S310, the user U1 inputs the issued one-time password and instructs remittance. For example, the user U1 inputs the issued one-time password, and then presses the remittance button.

  In step S312, the user U1 activates a mail application (hereinafter, referred to as “mail application M1”) on the user terminal.

  In step S314, the user U1 instructs (inputs) a destination to the mail application M1. For example, the user U1 selects an address (here, the address of the user U2) to be entered in the mail address column from the address book.

  In step S316, the user U1 instructs (inputs) the content of the text to the mail application M1. For example, the user U1 manually inputs the contents of the text. At this time, the contents of the text are, as schematically shown in FIG. 4, the bank information (an example of information indicating the payment destination) indicating the bank name (in this case, bank A1) and the amount information indicating the amount. And may be included. When the bank used by the user U1 to transfer money to the user U2 is always the bank A1, the bank information may be omitted. When the remittance amount is always constant, the amount information may be omitted. It may be omitted. Note that the email body may include a link 400 to a site where payment can be confirmed or the bank application AP1.

  In step S318, the user U1 instructs (inputs) transmission to the mail application M1. For example, the user U1 presses a mail transmission button. Thus, the remittance mail is transmitted to the input destination.

  FIG. 5 is an explanatory diagram of the remittance RPA software RPA6 constructed based on the operation flow shown in FIG. FIG. 5 shows, in a schematic flowchart form, each processing element for each of the remittance RPA software RPA6-1, RPA6-2, and RPA6-3.

  The remittance RPA software RPA6 includes three associated remittance RPA software RPA6-1, RPA6-2, and RPA6-3.

  The remittance RPA software RPA6-1 corresponds to steps S300 to S306 of the operation by the user U1 shown in FIG. Specifically, when the remittance RPA software RPA6-1 is activated on the user terminal in response to an instruction from the user U1, the remittance RPA software RPA6-1 activates the bank application AP1 as shown in FIG. 5 (step S500). Next, the remittance RPA software RPA6-1 inputs a password or the like and logs in to the bank application AP1 (step S502). Next, the remittance RPA software RPA6-1 instructs the bank application AP1 on the account of the remittance destination (step S504). At this time, the designated account is the same as that in step S304 of the operation by the user U1 shown in FIG. Next, the remittance RPA software RPA6-1 instructs the remittance amount to the bank application AP1 (step S506). At this time, the instructed remittance amount is the same as that in step S306 of the operation by the user U1 shown in FIG. Then, the remittance RPA software RPA6-1 outputs the remittance destination account and the remittance amount (an example of the first output), both of which are the instruction results (step S508). The remittance destination account and the remittance amount may be output (displayed) on a display device of the user terminal (for example, see the display device 14 in FIG. 2B).

  Next, when the remittance RPA software RPA6-1 outputs the remittance destination account and the remittance amount, it starts a parameter correction program PR6-1 (not shown) such as the parameter correction program PR1 shown in FIG. 2B ( Step S509).

  The user U1 (which may be a user other than the user U1) checks the account of the remittance destination and the remittance amount and, if necessary, uses an input device such as the input device 15 (see FIG. 2B) to transfer the remittance. Correct the previous account and remittance amount. The parameter correction program PR6-1 receives the remittance destination account and remittance amount, or receives an instruction not to correct the remittance destination account and remittance amount (if corrected, the remittance destination account and remittance amount after correction). ) Is input to the remittance RPA software RPA6-2. The parameter correction program PR6-1 may be incorporated in the remittance RPA software RPA6-1.

  The remittance RPA software RPA6-2 corresponds to steps S308 to S314 of the operation by the user U1 shown in FIG.

  When the remittance RPA software RPA6-2 is activated on the user terminal in response to the remittance RPA software RPA6-1 outputting the remittance destination account and the remittance amount, as shown in FIG. 5, the remittance destination account and the remittance amount ("NO" in step S520). That is, when the remittance RPA software RPA6-1 is completed, the remittance RPA software RPA6-1 is started (automatically) in a mode of taking over the remittance RPA software RPA6-1, and waits for an input of a remittee account and a remittance amount ( (Pause state).

  When the remittance RPA software RPA6-2 receives the input of the remittance destination account and the remittance amount via the parameter correction program PR6-1 ("YES" in step S520), it starts an application for issuing a one-time password (step S520). Step S522), input the issued one-time password, and instruct remittance (step S524). Next, the remittance RPA software RPA6-2 activates the mail application M1 (step S526) and specifies a destination (step S527). At this time, the mail application to be activated is the same as step S312 of the operation by the user U1 shown in FIG. 3, and the designated destination is the same as step S314 of the operation by the user U1 shown in FIG. Then, the remittance RPA software RPA6-2 outputs the destination (an example of the first output) as the instruction result (step S528). The destination may be output (displayed) in the form of e-mail on a display device of the user terminal (for example, see the display device 14 in FIG. 2B).

  Upon output of the destination, the remittance RPA software RPA6-2 starts a parameter correction program PR6-2 (not shown) such as the parameter correction program PR1 shown in FIG. 2B (step S529).

  The user U1 (possibly a user other than the user U1) checks the destination (and mailer) and corrects the destination using an input device such as the input device 15 (see FIG. 2B) as necessary. I do. Upon receiving an instruction to correct or not to correct the destination, the parameter correction program PR6-2 inputs the destination (if modified, the destination after correction) to the remittance RPA software RPA6-3. The parameter correction program PR6-2 may be incorporated in the remittance RPA software RPA6-2.

  The remittance RPA software RPA6-3 corresponds to steps S316 to S318 of the operation by the user U1 shown in FIG.

  When the remittance RPA software RPA6-3 is activated on the user terminal in response to the remittance RPA software RPA6-2 outputting the destination, as shown in FIG. 5, the destination RPA software RPA6-3 waits for the input of the destination ("NO" in step S530). ”). In other words, when the remittance RPA software RPA6-2 ends, the remittance RPA software RPA6-3 starts (automatically) taking over the remittance RPA software RPA6-2, and enters a destination input wait state (pause state).

  When the remittance RPA software RPA6-3 receives the destination input via the parameter correction program PR6-2 ("YES" in step S530), it instructs the contents of the text (step S532) and instructs the transmission (step S532). S534). In this way, the remittance mail (another example of the first output) is transmitted to the input destination. At this time, the content of the instructed text is the same as that in step S316 of the operation by the user U1 shown in FIG. 3, but if the remittance amount or the like is changed, the change is reflected.

  The remittance e-mail output by the remittance RPA software RPA6 is an e-mail including information indicating that a payment has been made. The information indicating that the payment has been made is arbitrary, and may be bank information or money amount information. Further, the information indicating that the payment has been made may be included in the title of the remittance email instead of or in addition to the text of the remittance email.

  According to the example shown in FIG. 5, it is possible to link a plurality of software based on RPA (three remittance RPA software RPA6-1, RPA6-2, and RPA6-3). That is, the three remittance RPA software RPA6-1, RPA6-2, and RPA6-3 constructed based on the user operation as shown in FIG. Business can be realized.

  Here, the effect of the example shown in FIG. 5 will be further described in comparison with the comparative example shown in FIG. In the remittance RPA software RPA6 'constructed according to the comparative example, as described above, steps S500 to S506, steps S522 to S527, and steps S532 and S534 are executed at once without "pause (pause)". In such a comparative example, the user cannot check or correct the remittance destination account, remittance amount, destination, and the like.

  In this regard, according to the example illustrated in FIG. 5, the activated remittance RPA software RPA6-2 is in a state of waiting for the input of the remittance destination account and the remittance amount, so that the user checks the remittee destination account and the remittance amount. After that, the remittance RPA software RPA6-2 can be executed. Similarly, the activated remittance RPA software RPA6-3 is in a state of waiting for the input of the destination, so that the user can execute the remittance RPA software RPA6-3 after confirming the destination. That is, since an automatic pause state is formed in the remittance RPA software RPA6, the user can easily execute the remittance RPA software RPA6 as intended.

  In the example shown in FIG. 5, the remittance RPA software RPA6 is constructed in such a manner that the contents of the body of the mail cannot be checked by the user U1, but is constructed so that the contents of the body of the mail can be checked by the user U1. Is also good. In this case, for example, the remittance RPA software RPA6-2 executes step S532 after step S527, and then outputs the destination and the contents of the text (an example of the first output) as the instruction result in step S528. Good.

  FIG. 6 is a diagram schematically showing a flow of operations performed by the user U2 when constructing the deposit RPA software RPA7 on the receiving side.

  In step S700, the user U2 starts a mail application (hereinafter, referred to as a “mail application M2”) on a user terminal (for example, a smartphone). Note that the mail application M2 may be the same as the above-described mail application M1. Note that the mail application M2 may be always in the activated state when the power of the user terminal is turned on. When the remittance mail is received, the mail application M2 may display the remittance mail in the form of a push notification.

  In step S702, the user U2 activates the bank application AP1 to confirm payment based on the bank information of the remittance mail (the mail transmitted in FIG. 3 or 5) from the user U1. At this time, the user U2 may activate the bank application AP1 using the link 400.

  In step S704, the user U2 inputs a password or the like and logs in to the bank application AP1.

  In step S706, the user U2 displays a payment screen to confirm the transfer status.

  In step S708, the user U2 activates the mail application M2 upon confirming that the payment has been made. If the mail application M2 has already been activated, step S708 may be omitted.

  In step S710, the user U2 instructs (inputs) a destination to the mail application M2. For example, the user U2 selects an address (here, the address of the user U1) to be entered in the mail address column from the address book.

  In step S712, the user U2 instructs (inputs) the content of the text to the mail application M2. For example, the user U2 manually inputs the contents of the text. At this time, depending on whether or not the payment has been confirmed, the content of the text is shown as schematically shown in FIG. 7A as the mail text 800 or the text of the mail 801 is shown in FIG. 7B. The content may be such that the payment has not been confirmed as schematically shown.

  In step S714, the user U2 instructs (inputs) transmission to the mail application M2. For example, the user U2 presses a mail transmission button.

  FIG. 8 is an explanatory diagram of the deposit RPA software RPA7 constructed based on the operation flow shown in FIG. FIG. 8 schematically illustrates each processing element in the received RPA software RPA7-1 and RPA7-2 in a schematic flowchart format.

  The deposit RPA software RPA7 includes two linked deposit RPA software RPA7-1 and RPA7-2. The payment RPA software RPA7-1 is RPA software for displaying a payment screen that outputs a transfer status (another example of the first output), and the payment RPA software RPA7-2 includes a payment confirmation mail (a mail for notifying a payment confirmation result). ) RPA software for transmission.

  The deposit RPA software RPA7-1 corresponds to steps S702 to S706 of the operation by the user U2 shown in FIG. More specifically, when the payment RPA software RPA7-1 is activated on the user terminal in response to an instruction from the user U2, it activates the bank application AP1 as shown in FIG. 8 (step S900). The user U2 looks at, for example, the remittance mail from the user U1, gives an instruction to activate the deposit RPA software RPA7-1, or looks at the deposit notification mail that can be transmitted from the bank A1, and checks the deposit RPA software RPA7. -1 may be given. Note that the deposit RPA software RPA7-1 may be automatically activated in conjunction with the receipt of a deposit notification email that can be transmitted from, for example, the bank A1. At this time, the bank application activated by the deposit RPA software RPA7-1 is the same bank application AP1 as in step S702 of the operation by the user U2 shown in FIG. Alternatively, the deposit RPA software RPA7-1 may automatically activate the bank application AP1 using the link 400 (see FIG. 4) that can be included in the remittance email from the user U1.

  Next, the deposit RPA software RPA7-1 inputs a password or the like and logs in to the bank application AP1 (step S902). At this time, the input password and the like are the same as those in step S704 of the operation by the user U2 shown in FIG. Next, the deposit RPA software RPA7-1 causes the bank application AP1 to display a deposit screen on which the transfer status can be confirmed (step S904).

  Upon displaying the payment screen, the payment RPA software RPA7-1 activates a parameter correction program PR7 such as the parameter correction program PR1 shown in FIG. 2B (step S906).

  The user U2 (which may be a user other than the user U2) checks the deposit screen, and uses an input device such as the input device 15 (see FIG. 2B) to display information indicating whether or not the deposit has been confirmed. input. When receiving the input of information indicating whether or not payment has been confirmed (hereinafter, “payment confirmation information”), the parameter correction program PR7 provides the payment confirmation information to the payment RPA software RPA7-2. The parameter correction program PR7 may be incorporated in the deposit RPA software RPA7-1.

  The deposit RPA software RPA7-2 corresponds to steps S708 to S714 of the operation by the user U2 shown in FIG.

  When the payment RPA software RPA7-2 is activated on the user terminal in response to the display of the payment screen by the payment RPA software RPA7-1, it enters a state of waiting for input of payment confirmation information as shown in FIG. 8 (step S910). "NO"). That is, when the payment RPA software RPA7-1 is completed, the payment RPA software RPA7-2 starts (automatically) in a manner of taking over the payment RPA software RPA7-1, and waits for input of payment confirmation information (pause state). Become.

  Receiving the payment confirmation information via the parameter correction program PR7 (“YES” in step S910), the payment RPA software RPA7-2 activates the mail application M2 (step S912) and specifies the destination (step S912). S914). At this time, the mail application to be activated is the same as step S708 of the operation by the user U2 shown in FIG. 6, and the destination to be instructed is the same as step S710 of the operation by the user U2 shown in FIG. Next, the payment RPA software RPA7-2 instructs the contents of the text (step S916), and instructs transmission (step S918). At this time, the content of the instructed text is the same as that in step S712 of the operation by the user U2 shown in FIG. 6, but the content is selected according to the payment confirmation information. For example, if the payment confirmation information indicates that the payment has been confirmed, the content as shown in FIG. 7A is selected, and if the payment confirmation information indicates that the payment has not been confirmed, the content is as illustrated in FIG. 7B. The content is selected. In this way, the payment confirmation mail (another example of the second output) is transmitted (replyed). The destination of the payment confirmation mail may be automatically set to the sender of the remittance mail.

  According to the example shown in FIG. 8, it is possible to link a plurality of software based on RPA (two payment RPA software RPA7-1 and RPA7-2). That is, while the two payment RPA software RPA7-1 and RPA7-2 constructed based on the user operation as shown in FIG. 6 cooperate, it is possible to realize the work related to the user operation as shown in FIG.

  Further, according to the example shown in FIG. 8, the activated payment RPA software RPA7-2 is in a state of waiting for input of payment confirmation information, so that the user checks the payment screen and then executes the payment RPA software RPA7-2. I can do it. That is, since an automatic pause state is formed in the remittance RPA software RPA7, the user can easily execute the remittance RPA software RPA7 as intended.

  Further, the payment RPA software RPA7 shown in FIG. 8 can realize exchange of a remittance mail and a payment confirmation mail in cooperation with the remittance RPA software RPA6 shown in FIG. That is, it is possible to link a plurality of software based on RPA (remittance RPA software RPA6 and deposit RPA software RPA7).

  Next, another example of the deposit RPA software will be described.

  FIG. 9 is a diagram schematically showing a configuration of a payment RPA software RPA7A according to another example.

  The payment RPA software RPA7A is different from the payment RPA software RPA7 shown in FIG. 8 in that a plurality of types of RPA software for displaying a payment screen are prepared. Specifically, the deposit RPA software RPA7A is different from the deposit RPA software RPA7 shown in FIG. 8 in that a deposit RPA software RPA7-1A, a deposit RPA software RPA7-1B, and the like are added.

  As described above with reference to FIG. 8, the deposit RPA software RPA7-1 activates the bank application AP1 to display the deposit screen, whereas the deposit RPA software RPA7-1A and the deposit RPA software RPA7. -1B and the like are different in that a bank application related to another bank is activated to display a payment screen. Such a configuration is suitable when the bank used for remittance is not constant but can vary variously. This is because the application differs for each bank, and the operations required until the payment screen is displayed are different. Specifically, the deposit RPA software RPA7-1A activates the bank application AP2 related to the bank A2 to display the deposit screen, and the deposit RPA software RPA7-1B activates the bank application AP3 related to the bank A3. To display the payment screen. The number of the deposit RPA software RPA7-1A, the deposit RPA software RPA7-1B, etc. is arbitrary as long as it is one or more.

  As described above, the payment RPA software RPA7A includes a plurality of types of RPA software (Payment RPA software RPA7-1, RPA7-1A, RPA7-1B, etc.) for displaying a payment screen, and RPA software RPA7-2 for transmitting a payment confirmation mail. Having. One of a plurality of types of RPA software for displaying a payment screen selected from a plurality of types of RPA software for displaying a payment screen, and an RPA software RPA7-2 for transmitting a payment confirmation mail are used as a set. Therefore, as a result, there are as many types of the payment RPA software RPA 7A as the types of the RPA software for displaying the payment screen.

  Which type of the RPA software for displaying the payment screen is selected (used) from the plurality of types of the RPA software for displaying the payment screen can be determined based on the bank information included in the remittance mail. For example, if the bank information included in the remittance email is “bank A2”, the deposit RPA software RPA7-1A is selected and used, and if the bank information included in the remittance email is “bank A3”, the deposit RPA The software RPA7-1B is selected and used.

  Thus, according to the deposit RPA software RPA7A, one of a plurality of types of RPA software for displaying a deposit screen is used based on the bank information included in the remittance mail from the remittance RPA software RPA6. It is possible to do. Thereby, the remittance RPA software RPA6 and the deposit RPA software RPA7A can be linked in various modes. As a result, it is possible to cope with diversification of business.

  Next, an RPA system and an RPA apparatus that can realize various functions using the above-described RPA software will be described with reference to FIG.

  FIG. 10 is a schematic diagram showing the entire RPA system 1.

  The RPA system 1 includes an RPA device 20 (an example of a first terminal) and an RPA device 21 (an example of a second terminal) connected via the network 4. The RPA system 1 may include one or more additional RPA devices in addition to the RPA device 20 and the RPA device 21.

  The network 4 may include the Internet, the World Wide Web, a WAN (Wide Area Network), a wireless communication network, a wired network, or any combination thereof.

  The RPA device 20 and the RPA device 21 correspond to the user terminals in the above description. The RPA device 20 and the RPA device 21 are, for example, smartphones, tablet terminals, personal computers, wearable terminals, and the like.

  FIG. 11 is a diagram illustrating an example of a hardware configuration of the RPA device 20. The same applies to the RPA device 21.

  In the example illustrated in FIG. 11, the RPA device 20 includes a control unit 101, a main storage unit 102, an auxiliary storage unit 103, a drive device 104, a network I / F unit 106, an input unit 107, and a display device 108.

  The control unit 101 is an arithmetic unit that executes a program stored in the main storage unit 102 or the auxiliary storage unit 103. The control unit 101 receives data from the input unit 107 or the storage device, calculates and processes the data, and outputs the data to the storage device or the like. I do.

  The main storage unit 102 is a ROM (Read Only Memory), a RAM (Random Access Memory), or the like. The main storage unit 102 is a storage device that stores or temporarily stores programs and data such as an OS (Operating System) and applications that are basic software executed by the control unit 101.

  The auxiliary storage unit 103 is an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like, and is a storage device that stores data related to RPA software, various applications, and the like.

  The drive device 104 reads a program from a recording medium 105, for example, a flexible disk, and installs the program in a storage device.

  The recording medium 105 stores a predetermined program. The program stored in the recording medium 105 is installed in the RPA device 20 via the drive device 104. The installed predetermined program can be executed by the RPA device 20.

  The network I / F unit 106 is an interface with a peripheral device having a communication function connected via a network constructed by a data transmission path such as a wired and / or wireless line.

  The input unit 107 has a keyboard, a mouse, a touch pad, and the like, which are provided with cursor keys, numeric input, various function keys, and the like. Note that the input unit 107 may be realized by a peripheral device connected via the network I / F unit 106. The input unit 107 can form the input device 15 shown in FIG. 2B.

  The display device 108 may be a liquid crystal display or the like. The display device 108 may be realized by a peripheral device connected via the network I / F unit 106. The display device 108 can form the display device 10 illustrated in FIGS. 2A and 2B or the display device 14 illustrated in FIG. 2B.

  Note that, in the example illustrated in FIG. 11, various processes described below can be realized by causing the RPA device 20 to execute a program. Further, it is also possible to record the program on the recording medium 105 and make the RPA device 20 read the recording medium 105 on which the program is recorded, thereby realizing various processes described below. Note that as the recording medium 105, various types of recording media can be used. For example, the recording medium 105 is a recording medium for recording information optically, electrically or magnetically, such as a CD (Compact Disc) -ROM, a flexible disk, a magneto-optical disk, or the like, or a ROM, a flash memory, or the like. May be a semiconductor memory or the like that electrically records the data.

  FIG. 12 is a functional block diagram for explaining each function of the RPA device 20 and the RPA device 21. Hereinafter, FIG. 12 will be described with reference to FIGS. 5, 8, and 9 described above.

  The RPA device 20 is a device that executes the remittance RPA software RPA6 shown in FIG. The RPA device 20 includes an RPA execution unit 201 (an example of a first execution unit) and an RPA software storage unit 204. For example, the RPA execution unit 201 may be configured such that the control unit 101 illustrated in FIG. 11 executes the programs (the above-described parameter correction programs PR6-1 and PR6-2) in the storage device (for example, the main storage unit 102) and the RPA software storage unit 204. (Including remittance RPA software RPA6 as described later). The RPA software storage unit 204 can be realized by the auxiliary storage unit 103, for example.

  The RPA execution unit 201 executes the RPA software in the RPA software storage unit 204. Here, as an example, it is assumed that the remittance RPA software RPA6 described above is stored in the RPA software storage unit 204.

  RPA execution section 201 includes a parameter correction program execution section 2012 and a remittance RPA software execution section 2014.

  The parameter correction program execution unit 2012 executes the above-described parameter correction programs PR6-1 and PR6-2. Specifically, the parameter correction program execution unit 2012 acquires instruction information from the user, and gives the acquired instruction information to the remittance RPA software execution unit 2014 (see steps S520 and S530 in FIG. 5). The instruction information from the user is information for instructing a remittance destination account, a remittance amount, a destination, and the like. The instruction information is input via the input unit 107 (see FIG. 11).

  The remittance RPA software execution unit 2014 executes the RPA software in the RPA software storage unit 204 based on the instruction information from the parameter correction program execution unit 2012. As a result, the remittance RPA software execution unit 2014 generates a remittance mail (another example of the first output) and transmits the generated remittance mail to the RPA device 21 via the network 4 (step in FIG. 5). See S534).

  The RPA device 21 is a device that executes the deposit RPA software RPA7A shown in FIG. The RPA device 21 includes an RPA execution unit 210 (an example of a second execution unit) and an RPA software storage unit 220. For example, the RPA execution unit 210 may be configured such that the control unit 101 illustrated in FIG. 11 executes a program (the above-described parameter correction program PR7) in a storage device (for example, the main storage unit 102) or a program (an after-mentioned program) in the RPA software storage unit 220. (Including the payment RPA software RPA7A). The RPA software storage unit 220 can be realized by the auxiliary storage unit 103, for example.

  The RPA execution unit 210 executes the RPA software in the RPA software storage unit 220. Here, as an example, it is assumed that the above-mentioned deposit RPA software RPA7A is stored in the RPA software storage unit 220. As described above with reference to FIG. 9, the payment RPA software RPA7A includes a plurality of types of RPA software (Payment RPA software RPA7-1, RPA7-1A, RPA7-1B, etc.) for displaying a payment screen, and a payment confirmation mail transmission. Trust RPA software 7-2.

  RPA execution section 210 includes remittance mail acquisition section 2100, parameter correction program execution section 2102, remittance mail analysis section 2104, and deposit RPA software execution section 2106.

  The remittance mail acquisition unit 2100 receives (acquires) the remittance mail (another example of the first output) from the RPA device 20 (the RPA execution unit 201) via the network 4 (an example of a first process).

  The parameter correction program execution unit 2102 executes the above-described parameter correction program PR7. Specifically, the parameter correction program execution unit 2102 acquires payment confirmation information from the user, and provides the acquired payment confirmation information to the payment RPA software execution unit 2106 (see step S910 in FIG. 8). The payment confirmation information from the user is information indicating whether or not payment has been confirmed. Payment confirmation information is input via the input unit 107 (see FIG. 11).

  The remittance mail analyzing unit 2104 analyzes the remittance mail (the remittance mail acquired by the remittance mail acquisition unit 2100) from the RPA device 20 (RPA execution unit 201) and specifies the bank to which the remittance is to be made. For example, the remittance email analyzing unit 2104 may specify the remittance destination bank based on bank information that can be included in the remittance email. When the remittance mail analysis unit 2104 specifies the remittance destination bank, the remittance destination is specified among a plurality of types of RPA software (Payment RPA software RPA7-1, RPA7-1A, RPA7-1B, etc.) for displaying a payment screen. RPA software for displaying a payment screen of a type corresponding to the bank is determined as an operation target (an example of determination processing).

  The payment RPA software execution unit 2106 executes the RPA software for displaying the payment screen of the operation target determined by the remittance mail analysis unit 2104. In this case, the parameter correction program execution unit 2102 provides the payment RPA software execution unit 2106 with the payment confirmation information based on the execution result of the RPA software for displaying the payment screen of the operation target determined by the remittance mail analysis unit 2104. Then, the payment RPA software execution unit 2106 executes the payment confirmation mail transmission RPA software 7-2 based on the payment confirmation information. As a result, the payment RPA software execution unit 2106 generates a payment confirmation mail (another example of the second output) (an example of the second processing), and transmits the generated payment confirmation mail to the RPA device 20 via the network 4. (See step S918 in FIG. 8).

  Note that FIG. 12 illustrates an example in which two RPA devices 20 and 21 cooperate, but three or more RPA devices may cooperate similarly.

  As described above, the embodiments have been described in detail. However, the present invention is not limited to the specific embodiments, and various modifications and changes can be made within the scope described in the claims. It is also possible to combine all or a plurality of the components of the embodiment described above.

  For example, in the above-described embodiment, the case where the present invention is mainly applied to the RPA related to the financial transaction (remittance) business is described. However, the present invention relates to another transaction business and a business other than the transaction. It is also applicable to RPA. In addition, the present invention can be applied to acts other than work. For example, in addition to the modification shown in FIG. 13 described later, when constructing an RPA for an order at a shopping site, the above-described pause is performed so that instruction information from the user can be obtained with respect to the order quantity and size of the product. A state may be formed. When constructing an RPA for an application at a travel application site, the pause state described above may be formed so that instruction information from the user can be obtained for the number of people, date, and the like.

  FIG. 13 is a conceptual explanatory diagram of software based on RPA according to a modification. FIG. 13 schematically shows three RPA software RPA1, RPA2, and RPA3. Note that the number of RPA software is arbitrary.

In FIG. 13, the RPA software RPA1 is named, for example, a release approval conference robo process, and includes the following processing elements from S1 to S5.
S1: Create entry contents using spreadsheet software S2: Create electronic bulletin board for public relations department S3: Create deadline management database S4: Create request mail S5: Send request mail Also, as one example, RPA software RPA2 is referred to as a large-scale project integration robo process. This is a name and includes the following processing elements from S10 to S15.
S10: Create an electronic bulletin board for the public relations department S11: Create a schedule using spreadsheet software S12: Create a request mail S13: Send a request mail S14: Receive a correction request S15: Update a schedule on the spreadsheet software RPA software RPA3 is an example. , A patent monthly monitoring robot process, and includes the following processing elements from S20 to S27.
S20: Receive monitoring request S21: Create electronic bulletin board for public relations section S22: Create confirmation request mail S23: Send confirmation request mail S24: Receive confirmed mail S25: Modify electronic bulletin board for public relations section S26: Create monitoring request mail S27: Monitoring Request transmission The RPA software RPA1 to RPA3, when given a predetermined input from the user, operate based on the input and execute all the processing elements respectively. For example, in the RPA software RPA3, the predetermined input includes the search condition in S20, the mail address of the destination in S23, the mail address of the destination in S26, and the like. In S25, the electronic bulletin board of the public relations section is corrected based on the content of the confirmed mail.

  In the RPA software RPA1, RPA2, and RPA3 as well, the pause state described above may be formed so that instruction information from the user can be obtained. For example, after step S4 of RPA1, the above-mentioned pause state may be formed so that instruction information from the user regarding the contents of the request mail is obtained. Further, after step S12 of RPA2, the above-described pause state may be formed so that instruction information from the user regarding the contents of the request mail is obtained. Further, after the step S22 of the RPA3, the above-described pause state may be formed so that instruction information from the user regarding the content of the confirmation request mail is obtained. Further, after the step S25 of the RPA3, the above-described pause state may be formed so as to obtain the instruction information from the user regarding the correction content.

  In addition, the following supplementary notes are disclosed with respect to the above embodiment.

[Appendix 1]
First processing for obtaining a first output according to an operation result of the first software from first software based on robotic process automation (RPA);
A second process for generating a second output according to an operation result of the second software by causing second software based on the RPA to operate based on the first output.

[Appendix 2]
The second software has a plurality of types,
2. The RPA device according to claim 1, further comprising: a determination process of determining a type of the second software to be operated among a plurality of types of the second software based on the first output.
[Appendix 3]
The first output includes information indicating a payment destination,
3. The RPA device according to claim 2, wherein the determining process determines the type of the second software to be operated among a plurality of types of the second software based on the information indicating the payment destination.
[Appendix 4]
The RPA device according to attachment 3, wherein the second output includes information indicating whether or not payment to the payment destination has been confirmed.
[Appendix 5]
The first process is a process of acquiring the first output by communication from a first terminal on which the first software has been executed,
The RPA device according to any one of Supplementary notes 1 to 4, wherein the second process is executed by a second terminal different from the first terminal.
[Appendix 6]
The RPA device according to appendix 5, further performing a process of sending the second output to the first terminal or a third terminal different from the first terminal and the second terminal.
[Appendix 7]
After the operation of the first software and before the operation of the second software, further execute a process of acquiring instruction information from the user for the first output;
2. The RPA device according to claim 1, wherein the second process operates the second software based on the instruction information.

[Appendix 8]
The RPA device according to attachment 7, wherein the first software and the second software can realize one transaction in cooperation with each other.
[Appendix 9]
An RPA system including a first execution unit and a second execution unit for executing software based on robotic process automation (RPA),
The first execution unit executes first software based on RPA, and transmits a first output according to an execution result of the first software to the second execution unit;
The RPA system, wherein the second execution unit executes second software based on RPA based on the first output, and generates a second output according to an execution result of the second software.
[Appendix 10]
A program based on Robotic Process Automation (RPA),
Acquiring the first output from software based on RPA that generates a first output according to an operation result;
Generating a second output based on the first output;
A program that causes a computer to execute processing.

1 RPA system 20 RPA device 21 RPA device 201 RPA execution unit 204 RPA software storage unit 210 RPA execution unit 220 RPA software storage unit 400 Link 800 Email body 801 Email body 2012 Parameter correction program execution unit 2014 Remittance RPA software execution unit 2100 Remittance Email acquisition unit 2102 Parameter correction program execution unit 2104 Remittance mail analysis unit 2106 Deposited RPA software execution unit

Claims (9)

First processing for obtaining a first output according to an operation result of the first software from first software based on robotic process automation (RPA);
A second process for generating a second output according to an operation result of the second software by causing second software based on the RPA to operate based on the first output. The second software has a plurality of types,
The RPA device according to claim 1, further comprising: a determination process of determining a type of the second software to be operated among a plurality of types of the second software based on the first output. The first output includes information indicating a payment destination,
The RPA device according to claim 2, wherein the determining process determines the type of the second software to be operated among a plurality of types of the second software based on information indicating the payment destination. The first process is a process of acquiring the first output by communication from a first terminal on which the first software has been executed,
The RPA device according to any one of claims 1 to 3, wherein the second processing is executed by a second terminal different from the first terminal.   The RPA device according to claim 4, further comprising a process of sending the second output to the first terminal or to a third terminal different from the first terminal and the second terminal. After the operation of the first software and before the operation of the second software, further execute a process of acquiring instruction information from the user for the first output;
The RPA device according to claim 1, wherein the second processing operates the second software based on the instruction information.   The RPA device according to claim 6, wherein the first software and the second software can realize one transaction in cooperation with each other. An RPA system including a first execution unit and a second execution unit for executing software based on robotic process automation (RPA),
The first execution unit executes first software based on RPA, and transmits a first output according to an execution result of the first software to the second execution unit;
The RPA system, wherein the second execution unit executes second software based on RPA based on the first output, and generates a second output according to an execution result of the second software. A program based on Robotic Process Automation (RPA),
Acquiring the first output from software based on RPA that generates a first output according to an operation result;
Generating a second output based on the first output;
A program that causes a computer to execute processing.