RPA development and operation management device, RPA development and operation management system, RPA development and operation management method, program, and recording medium

Abstract

To provide an RPA development operation management device that can grasp the development and operation status of RPA according to various needs.SOLUTION: In an RPA development operation management device 10, a data acquisition unit 11 acquires RPA data related to RPA. The RPA data includes RPA development data, RPA system data, and RPA operation management data. For each RPA, a data management unit 12 manages the RPA system data, the RPA development data, and the RPA operation management data in association with each other by an identifier. An inquiry item acquisition unit 13 acquires an inquiry item for RPA. With respect to the RPA that is the target of the inquiry item, a data aggregation unit 14 generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operation management data associated by the identifier. An aggregated data output unit 15 outputs the generated aggregated data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an RPA development and operation management device, an RPA development and operation management system, an RPA development and operation management method, a program, and a recording medium. [Background technology]

[0002] In recent years, the development and use of Robotic Process Automation (RPA) has been increasing for the purpose of improving the efficiency of clerical work and data analysis, etc. Prior Patent Document 1 discloses an RPA device that realizes one task by linking multiple software programs based on RPA. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-3905 A Summary of the Invention [Problem to be solved by the invention]

[0004] As RPA becomes more widespread, the development and operation (use) of multiple RPAs is increasingly being carried out simultaneously in parallel at one company or one business location. There are many people involved in RPA, and depending on their position, there is a need to understand various aspects of RPA. For example, a manager has a need to understand the effect of RPA implementation on business efficiency, an RPA promoter (implementation manager) has a need to understand the RPA development status, and an RPA operation manager has a need to understand the RPA license usage status. However, there was no technology that could understand the RPA development and operation status according to various needs.

[0005] Therefore, an object of the present invention is to provide an RPA development and operation management device and an RPA development and operation management method that are capable of grasping the development and operation status of RPA in accordance with various needs. [Means for solving the problem]

[0006] In order to achieve the above object, the RPA development and operation management device of the present invention comprises: The system includes a data acquisition unit, a data management unit, an inquiry item acquisition unit, a data aggregation unit, and an aggregated data output unit, The data acquisition unit acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data regarding the development of RPA, The RPA system data is data related to a system for which RPA is used, The Senki RPA operation and management data is data related to the operation and management of the developed RPA. The data management unit manages the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition unit acquires an inquiry item for the RPA, The data aggregation unit generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operations management data linked by the identifier with respect to the RPA that is the subject of the inquiry item, and The aggregated data output unit outputs the generated aggregated data. It is a device.

[0007] The RPA development and operation management system of the present invention comprises: Including RPA development and operation management equipment, RPA related terminals, and RPA-equipped terminals, the RPA development and operation management device and the RPA-equipped terminal are capable of communicating with each other via a communication line network; The RPA development and operation management device and the RPA related party terminal can communicate with each other via a communication line network, The RPA development and operation management device is an apparatus of the present invention, The data acquisition unit of the RPA development and operation management device acquires the RPA data from the RPA-related party terminal and the RPA-equipped terminal, The inquiry item acquisition unit of the RPA development and operation management device acquires an inquiry item for the RPA from the RPA-related party terminal, The aggregated data output unit of the RPA development and operation management device is a system that outputs the generated aggregated data to the RPA related party terminal.

[0008] The RPA development, operation and management method of the present invention comprises the steps of: The method includes a data acquisition step, a data management step, an inquiry item acquisition step, a data aggregation step, and an aggregated data output step. The data acquisition step acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data regarding the development of RPA, The RPA system data is data related to a system for which RPA is used, The Senki RPA operation and management data is data related to the operation and management of the developed RPA. The data management step manages the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition step acquires an inquiry item for the RPA, The data aggregation step generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operations management data linked by the identifier, for the RPA that is the subject of the inquiry item; The tabulated data output step outputs the generated tabulated data. This is the method. Effect of the Invention

[0009] According to the present invention, it becomes possible to grasp the development and operation status of RPA in accordance with various needs. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1(A) is a block diagram showing an example configuration of an RPA development and operation management device of embodiment 1, and FIG. 1(B) is a schematic diagram showing an example configuration of a system including the RPA development and operation management device of embodiment 1. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of the RPA development and operation management device according to the first embodiment. [Diagram 3] FIG. 3 is a flowchart illustrating an example of processing in the RPA development and operation management device of the first embodiment. [Figure 4] FIG. 4 is a schematic diagram illustrating an example of a data flow in the RPA development and operation management system of the second embodiment. [Diagram 5] FIG. 5 is a schematic diagram showing an example of developing and operating an RPA by the RPA development and operation management device of the second embodiment. [Figure 6] FIG. 6 is a schematic diagram illustrating an example of the relationship between the inquiry item, the aggregated data, and the RPA data. [Figure 7] FIG. 7 is an ER diagram showing an example of the data structure of the RPA data managed by the data management unit. [Figure 8] FIG. 8 is an ER diagram showing an example of the data structure of the RPA data managed by the data management unit. [Figure 9] FIG. 9 is an ER diagram illustrating an example of the data structure of the RPA data managed by the data management unit. [Figure 10] FIG. 10 is an ER diagram showing an example of the data structure of the RPA data managed by the data management unit. [Figure 11] FIG. 11 is an ER diagram showing an example of the data structure of the RPA data managed by the data management unit. [Figure 12] FIG. 12 is a schematic diagram showing an example of visualization of the aggregated data. [Figure 13]FIG. 13 is a schematic diagram showing an example of visualization of the aggregated data. [Figure 14] FIG. 14 is a schematic diagram showing an example of visualization of the aggregated data. [Figure 15] FIG. 15 is a schematic diagram showing an example of visualization of the aggregated data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] In the RPA development and operation management device and the RPA development and operation management method of the present invention, for example, The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data relating to an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for an RPA related to the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, development request data, development-related organization data, and development progress data may be linked to one another using the development application number as the identifier.

[0012] In the RPA development and operation management device and the RPA development and operation management method of the present invention, for example, The RPA system data includes RPA partner system data and RPA use system data, The RPA partner system data includes data on the partner system that is the target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA-utilizing system data may be linked to each other using the development application number as the identifier.

[0013] In the RPA development and operation management device and the RPA development and operation management method of the present invention, for example, The RPA operation management data includes RPA management data and RPA operation data, The RPA management data includes an RPA cooperation destination system login ID for each RPA, The RPA management data and the RPA operation data may be linked to each other using the development application number as the identifier.

[0014] The RPA development and operation management device of the present invention includes, for example, Further, a display processing unit is included, The display processing unit may execute a process of displaying the outputted summary data.

[0015] The RPA development, operation and management method of the present invention includes, for example, Further, a display processing step is included, The display processing step may be a step of executing a process of displaying the outputted summary data.

[0016] The program of the present invention is a program for causing a computer to execute each step of the method of the present invention as a procedure.

[0017] The recording medium of the present invention is a computer-readable recording medium having the program of the present invention recorded thereon.

[0018] The embodiments of the present invention will be described with reference to the drawings. The present invention is not limited to the following embodiments. In each of the drawings, the same parts are given the same reference numerals. In addition, the explanations of each embodiment can be mutually incorporated unless otherwise specified, and the configurations of each embodiment can be combined unless otherwise specified.

[0019] [Embodiment 1] FIG. 1(A) is a block diagram showing an example of the configuration of an RPA development operation management device 10 of this embodiment, and FIG. 1(B) is a schematic diagram showing an example of the configuration of an RPA development operation management system including the RPA development operation management device 10 of this embodiment. As shown in FIG. 1(A), this device 10 includes a data acquisition unit 11, a data management unit 12, an inquiry item acquisition unit 13, a data aggregation unit 14, an aggregated data output unit 15, and a display processing unit 16. The display processing unit 16 is an optional configuration and does not need to be included in this device 10. The RPA development operation management system is also called, for example, an RPA development operation management system device. The RPA development operation management system will be described later.

[0020] The device 10 may be, for example, a single device including each of the above-mentioned units, or a device to which each of the above-mentioned units can be connected via a communication network 40. The device 10 may be connected to an external device described later via the communication network 40. The communication network 40 is not particularly limited, and any known network may be used, for example, wired or wireless. Examples of the communication network 40 include an Internet line, a World Wide Web (WWW), a telephone line, a Local Area Network (LAN), a Storage Area Network (SAN), and a Delay Tolerant Networking (DTN). Examples of wireless communication include Wireless Fidelity (WiFi) and Bluetooth (registered trademark). The wireless communication may be either a form in which each device directly communicates (Ad Hoc communication) or an indirect communication via an access point. The device 10 may be, for example, incorporated in a server as a system. The device 10 may be, for example, a personal computer (PC, for example, desktop type or notebook type) in which the program of the present invention is installed, a mobile phone, a smartphone, a tablet terminal, or the like.

[0021] 2 illustrates a block diagram of the hardware configuration of the device 10. The device 10 includes, for example, a central processing unit (CPU, GPU, etc.) 101, a memory 102, a bus 103, a storage device 104, an input device 105, a display device 106, and a communication device 107. The components of the device 10 are connected to each other via the bus 103 and their respective interfaces (I / F).

[0022] The central processing unit 101 is responsible for the overall control of the device 10. In the device 10, the central processing unit 101 executes, for example, the program of the present invention and other programs, and also reads and writes various information. Specifically, for example, the central processing unit 101 functions as a data acquisition unit 11, a data management unit 12, an inquiry item acquisition unit 13, a data aggregation unit 14, an aggregated data output unit 15, and a display processing unit 16.

[0023] The bus 103 can also be connected to, for example, an external device. Examples of the external device include an external storage device (external database, etc.), a printer, etc. The present device 10 can be connected to an external network (communication line network 40) by, for example, a communication device 107 connected to the bus 103, and can also be connected to other devices via the external network.

[0024] An example of the memory 102 is a main memory (primary storage device). When the central processing unit 101 performs processing, the memory 102 reads various operation programs, such as the program of the present invention, stored in the storage device 104 described below, and the central processing unit 101 receives data from the memory 102 and executes the program. The main memory is, for example, a RAM (random access memory). The memory 102 may also be, for example, a ROM (read only memory).

[0025] The storage device 104 is also called an auxiliary storage device, for example, in contrast to the main memory (primary storage device). As described above, the storage device 104 stores an operation program including the program of the present invention. The storage device 104 may be, for example, a combination of a recording medium and a drive for reading and writing from and to the recording medium. The recording medium is not particularly limited, and may be, for example, an internal or external type, such as a hard disk (HD), CD-ROM, CD-R, CD-RW, MO, DVD, flash memory, or memory card. The storage device 104 may be, for example, a hard disk drive (HDD) in which a recording medium and a drive are integrated, or a solid state drive (SSD).

[0026] In the present device 10, the memory 102 and storage device 104 can also store user log information, as well as information obtained from an external database (not shown).

[0027] The device 10 may further include, for example, an input device 105 and a display device 106. The input device 105 is, for example, a touch panel, a keyboard, a mouse, etc. The display device 106 is, for example, an LED display, a liquid crystal display, etc.

[0028] Next, an example of the RPA development operation management method of this embodiment will be described with reference to the flowchart of Fig. 3. The RPA development operation management method of this embodiment is implemented as follows, for example, using the RPA development operation management device 10 of Fig. 1. Note that the RPA development operation management method of this embodiment is not limited to use of the RPA development operation management device 10 of Fig. 1.

[0029] First, the data acquisition unit 11 acquires RPA data related to robotic process automation (RPA) (S1). The format of the acquisition is not particularly limited, and may be acquired via the communication network 40, or may be acquired by inputting the RPA data by the input device 105. The RPA data includes RPA development data, RPA system data, and RPA operation management data. The RPA development data is data related to the development of RPA. The RPA system data is data related to a system that is the target of use of RPA. The RPA system data may include, for example, a planned use of RPA (RPA under development) and a candidate for use (whether or not RPA will be developed) and the like. The RPA operation management data is data related to the operation and management of the developed RPA. Specific details of the RPA development data, the RPA system data, and the RPA operation management data will be described later.

[0030] Next, the data management unit 12 manages the RPA system data, the RPA development data, and the RPA operation management data by linking them to each other using an identifier for each RPA (S2). The identifier is not particularly limited and may be, for example, a character, a symbol, a number, or a combination thereof.

[0031] Next, the inquiry item for the RPA is acquired by the inquiry item acquisition unit 13 (S3). The format of the acquisition is not particularly limited, and for example, the inquiry items may be acquired via the communication network 40, or may be acquired by inputting the RPA data by the input device 105. The inquiry items will be described later. For example, as shown in FIG. 3, the step (S3) may be processed in parallel with the steps (S1) to (S2), or may be processed following the step (S2).

[0032] Next, the data aggregation unit 14 generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operation management data linked by the identifier for the RPA that is the subject of the inquiry item (S4). The generated aggregated data may be stored in, for example, the memory 102 or the storage device 104.

[0033] Then, the generated tabulated data is output by the tabulated data output unit 15 (S5), and the process ends (END). The format of the output is not particularly limited, and may be output to the external device via the communication line network 40, or may be output to the display device 106 by the display processing unit 16 described later.

[0034] 3, if the device 10 further includes a display processing unit 16, the display processing unit 16 may execute a process of displaying the outputted aggregated data (S6) following the step (S5) and then terminate (END). The process may be, for example, a process on the display device 106 or a process on an external display device via the communication network 40.

[0035] According to the RPA development / operation management device 10 of the present embodiment, for example, by generating the aggregated data, it is possible to grasp the development / operation status of RPA in accordance with various needs.

[0036] [Embodiment 2] The RPA data, inquiry items, and aggregated data will be described with reference to Fig. 4 to Fig. 6. Note that the RPA data, inquiry items, and aggregated data shown in this embodiment are merely examples, and are not limited to these.

[0037] FIG. 4 shows an example of data flow in the RPA development and operation management system (hereinafter, also referred to as the system) of the present invention. As shown in FIG. 1(B) and FIG. 4, this system includes an RPA development and operation management device 10, an RPA related person terminal 20, and an RPA-equipped terminal 30. For example, this system may further include an RPA execution management terminal 50. The number of the RPA related person terminals 20, the RPA-equipped terminals 30, and the RPA execution management terminals 50 is not particularly limited, and each may be one, or may be two or more. The RPA-equipped terminal 30 may be, for example, a server. The RPA development and operation management device 10 and the RPA-equipped terminal 30 can communicate with each other via a communication line network 40. Also, the RPA development and operation management device 10 and the RPA related person terminal 20 can communicate with each other via the communication line network 40. Furthermore, for example, the RPA related person terminal 20 and the RPA-equipped terminal 30 may be able to communicate with each other via the communication line network 40. Also, for example, the RPA development operation management device 10 and the RPA execution management terminal 50 may be able to communicate with each other via a communication line network 40. The RPA development operation management device 10 is the RPA development operation management device 10 described in the first embodiment. The data acquisition unit 11 of the RPA development operation management device 10 acquires the RPA data from the RPA related person terminal 20 and the RPA-equipped terminal 30. Also, the RPA development operation management device 10 may acquire job and schedule data, etc. from the RPA execution management terminal 50, for example, as shown in FIG. 4. The RPA execution management terminal 50 is, for example, a device that manages the execution schedule of the RPA of the RPA-equipped terminal 30 and issues an execution instruction. The inquiry item acquisition unit 13 of the RPA development operation management device 10 acquires an inquiry item for the RPA from the RPA related person terminal 20. The inquiry item may be acquired as a file, for example, as shown in FIG. 4. The aggregated data output unit 15 of the RPA development operation management device 10 outputs the generated aggregated data to the RPA related person terminal 20. As shown in Fig. 4, the RPA development and operation management device 10 may output the aggregated data as a file, for example. The job in Fig. 4 is, for example, a job related to the execution of the RPA. The schedule data in Fig. 4 will be described later.Also, as shown in FIG. 4, a "login screen", a "menu screen", and the like are displayed on the display device 106 of the RPA development / operation management device 10, but these are merely examples and are not limited to these. Furthermore, as shown in FIG. 4, the RPA development / operation management device 10 may output the aggregated data to the RPA stakeholder terminal 20 via, for example, a BI (Business Intelligence) tool. The BI tool is, for example, a tool that analyzes and processes the aggregated data. The BI tool may or may not be included in the RPA development / operation management device 10. This allows, for example, the aggregated data to be visualized in an easy-to-understand manner for users (RPA stakeholders). An example of visualization will be described later.

[0038] FIG. 5 shows an example of developing and operating an RPA by the RPA development / operation management device 10 of the present invention. Each user (a person involved in RPA) shown in the upper part of FIG. 5 transmits an inquiry to the RPA development / operation management device 10 using, for example, an RPA-related person terminal 20. The RPA development / operation management device 10 acquires the inquiry and each data related to the development of RPA shown in the lower part of FIG. 5, and generates aggregated data as described above. Note that the "Web AP" shown in FIG. 5 means a Web application server, and does not need to be included in the RPA development / operation management device 10. Then, the RPA development / operation management device 10 outputs the aggregated data corresponding to each RPA-related person terminal 20. The "fault data" shown in FIG. 5 is, for example, data related to an RPA fault.

[0039] FIG. 6 shows an example of the relationship between the inquiry items, the aggregated data, and the RPA data. The left side of FIG. 6 shows an example of a user (a person concerned with RPA). Specifically, the RPA development data includes, for example, development application data, development request data, development related organization data, and development progress data, as shown in FIG. 6. The development application data, development request data, development related organization data, and development progress data are linked to each other using the development application number described later as the identifier. The development application data includes development application RPA data regarding the RPA for which a development application has been made, and the development application RPA data includes the development application number of the RPA for which a development application has been made. More specifically, the development application data is, for example, data that manages the status from development to operation of the RPA for which a development application has been made, and data that manages the reduction time effect derived from the business flow, the development scale, operation costs, etc. The development request data includes data regarding the user's request for the RPA regarding the development application. More specifically, the development request data is, for example, data that manages an overview of the business to which RPA is to be applied, and introduction effect prediction information regarding the prediction of the effect of the introduction of RPA, etc. The development-related organization data includes data on related organizations related to the development of the RPA related to the development application. More specifically, the development-related organization data is, for example, data linking the development application number with other identifiers (for example, a request management number described later, etc.), data managing information on related parties, etc. The related parties include, for example, an RPA purchaser (company, business division, person in charge, etc.), an RPA developer (company, business division, person in charge, etc.), an RPA user (RPA purchaser, etc.), and RAP-using system related parties (company, business division, person in charge, etc.). The development progress data includes data on the development progress status of the RPA related to the development application. More specifically, the development progress data is, for example, data managing a summary of the development progress status for each RPA that became the development target (shown as development progress data (1) in FIG. 6), and data managing the development progress status for each RPA that became the development target and / or for each development work task of the RPA (shown as development progress data (2) in FIG. 6).

[0040] Specifically, the RPA system data includes, for example, RPA cooperation destination system data (also referred to as RPA contact system data) and RPA use system data, as shown in FIG. 6. The RPA cooperation destination system data and the RPA use system data are linked to each other using the development application number as the identifier. The RPA cooperation destination system data includes data of the partner system that is the target of use of the RPA. More specifically, the RPA cooperation destination system data is, for example, data that manages the operation time, revision information, screen list, etc. of the system that is the cooperation destination of the RPA (hereinafter, also referred to as the cooperation destination system). The cooperation destination system is not particularly limited. The RPA use system data includes data of the system used by the RPA. More specifically, the RPA use system data is, for example, data that manages information on the system used by the RPA and the representative of the parties involved, such as the business manager and system manager of the system, and data that manages the screen of the system used by the RPA.

[0041] Specifically, the RPA operation management data includes RPA management data and RPA operation data, for example, as shown in FIG. 6. The RPA management data and the RPA operation data are linked to each other using the development application number as the identifier. The RPA management data includes an RPA cooperation destination system login ID (identification) for each RPA. More specifically, the RPA management data is, for example, data for managing the RPA cooperation destination system login ID of the RPA and information of the relevant person for each business to be automated (i.e., business to which the RPA is applied), etc. The RPA cooperation destination system login ID is, for example, an ID for logging in to a system that is a cooperation destination of the RPA. The RPA operation data is, for example, operation data (also called log information) output when the RPA is executed. More specifically, it is, for example, information indicating which RPA was executed in which environment from what time to what time. The RPA operation management data may include, for example, schedule data. The schedule data is, for example, data for managing the execution schedule of the RPA and the execution result (for example, normal completion, abnormality, running, etc.).

[0042] More specifically, when the inquiry item is "I want to see the introduction effect" shown in FIG. 6, the device 10 generates "effect creation time" from the development application data, development progress data (1), and development progress data (2), for example. Each of the collected data shown in FIG. 6 will be described below. The effect creation time means, for example, the time saved from existing work by introducing RPA. The RPA map means, for example, a table that lists the number of work for each business area, the number of RPAs, and the time saved by introducing RPA. The cost-effectiveness list is, for example, a graph that compares the cost of introducing RPA (development cost, operation cost, etc.) with the labor cost incurred in existing work, and expresses when the cost of introducing RPA can be recovered after introducing RPA, that is, when the cost of introducing RPA exceeds the labor cost. The case list is, for example, a table that displays the development schedule and release schedule for each case. The RPA management data is, for example, the same as described above. The RPA execution result confirmation is, for example, the same as the execution result. The list of revision information for systems in use (also called the list of revision information for systems in use RPA) and the revision information registration for systems in use (also called the revision information registration for systems in use RPA) are, for example, information showing the revision information for systems in use, which makes it possible to display a list of revision information and check the impact of revisions on RPA. The RPA operation status means, for example, information on when and how much RPA is operating. License consumption information is, for example, information showing how much RPA license is being used, which makes it possible to visualize license surpluses and shortages and to make effective use of RPA licenses.

[0043] Generally, the timing at which each RPA data can be acquired varies depending on the development and operation phase of the RPA, so it is difficult to link each RPA data to generate the aggregated data. Specifically, for example, information on a system to which the RPA is to be applied is acquired in a preparatory phase for the development of the RPA. Also, the development request data, the development-related organization data, the RPA management data, the development application data, and the development progress data are acquired, for example, in the development phase of the RPA. Furthermore, the RPA cooperation destination system data, the RPA operation data, and the RPA use system data are acquired, for example, in the operation phase of the RPA. However, according to the present invention, for example, the RPA data is managed by linking each RPA data to each other by an identifier (for example, a development application number, etc.) for each RPA, so that the aggregated data can be generated.

[0044] [Embodiment 3] Specific examples of the present invention are shown in Figures 7 to 11. Note that the RPA data, inquiry items, and tabulated data shown in this embodiment are merely examples, and the present invention is not limited to these.

[0045] First, an example of application of the present invention to an inquiry item of "I want to see the introduction effect" will be described. Specifically, the inquiry item is a content of wanting to grasp the introduction effect of the whole company and each business division. FIG. 7 is an ER diagram (Entity Relationship Diagram) showing an example of the data structure of RPA data managed by the data management unit 12. The ER diagram is shown in IDEF1X notation (the same applies to each ER diagram described later). As shown in FIG. 7, the present device 10 links and manages each RPA data, and generates aggregated data. The "development application number" is, for example, a number assigned at the timing when RPA conversion is confirmed. The "request management number" is, for example, a number assigned at the timing when a request for business automation is made. More specifically, the present device 10 manages, for example, the RPA development schedule for each business division and each business to be automated, visualizes the reduction process for each business division and month, and outputs the reduction process (reduction effect) for the target period, i.e., the introduction effect of RPA, as aggregated data when the business division and period are input. The reduction process means, for example, the time reduced by the introduction of RPA compared to before the introduction of RPA. The reduction process may be, for example, a reduction process in the development request data, a reduction process before screening, a reduction process after screening, etc. The screening is performed, for example, based on the development application number (see the data structure of the development application gate table in FIG. 7). Specifically, for example, a screening is performed to check whether the development of RPA is progressing according to the development schedule. The screening is also called, for example, a gate. The screening is managed, for example, by a gate number for each screening. The visualization can be performed by the BI tool, and an example of the visualization is described in the fourth embodiment. In this way, according to the present invention, each data that occurs at different times can be associated as a whole by the development application number. Therefore, for example, the reduction process (reduction effect) is managed, and the progress toward the reduction target can be visualized.

[0046] Next, an example of application of the present invention to an inquiry item of "I want to see the development progress and release schedule" will be described. Specifically, the inquiry item is a content of wanting to grasp the development progress and release of each RPA that was developed. FIG. 8 is an ER diagram (Entity Relationship Diagram) showing an example of the data structure of RPA data managed by the data management unit 12. As shown in FIG. 8, the present device 10 links and manages each RPA data, and generates aggregated data. Specifically, the present device 10 manages, for example, the RPA development schedule for each RPA, visualizes the development progress and release schedule for each RPA, and outputs the development progress and release schedule of each RPA in the target period as aggregated data when the company, business division, and period are input. The development progress and release schedule output as the aggregated data include, for example, the review development status, the result of the review, the start date of operation of the RPA, the scheduled date of operation of the RPA, the development schedule, and the development performance date. The review development status is data that manages the state (status) of each process, such as an estimate process, an interview process with the department that is planning to introduce RPA, a workflow creation process, a design process, a manufacturing process, a test process, an introduction process, and a revision process. Examples of the status include pass, fail, hold, and stop. In this case, the review is performed based on the development application number, the review development status, and the operation start date. The visualization can be performed by the BI tool, and an example of the visualization is described in the fourth embodiment. In this way, according to the present invention, each data that occurs at different times can be associated as a whole by the development application number. Therefore, for example, it is possible to visualize the development progress that is centrally managed.

[0047] Next, an example of application of the present invention to inquiries such as "I want to effectively utilize the license" and "I want to know the operation status" will be described. Specifically, the inquiries are such as "I want to effectively utilize the license related to the use of RPA" and "I want to know the operation status of RPA". FIG. 9 is an entity relationship diagram (ER diagram) showing an example of the data structure of RPA data managed by the data management unit 12. As shown in FIG. 9, the present device 10 generates aggregated data based on the RPA operation management data. Specifically, the present device 10 centrally manages each piece of information from the RPA operation management data, and when a period is input, outputs the number of licenses consumed by the RPA-equipped terminal, the number of RPA operations, and the operation time of the RPA during the target period as aggregated data. More specifically, the RPA operation management data includes, for example, an RPA cooperation destination system login ID, and the RPA cooperation destination system login IDs are linked to each other using the development application number as the identifier. In this way, according to the present invention, for example, it is possible to grasp the license operation status (the number of licenses consumed by the RPA-equipped terminal, the number of RPAs in operation, and the operation time of the RPA) that is managed centrally. Note that in Fig. 9, the RPA-equipped terminal 30a is a server, and the RPA-equipped terminal 30b is a terminal (also called an execution terminal) such as a PC or a smartphone.

[0048] Next, an example of application of the present invention to an inquiry item of "I want to know the extent of the impact of the revision of the linked system" will be described. Specifically, the inquiry item is such as "I want to know the extent of the impact on the constructed (developed) RPA in the revision of the linked system", "The screen is not shared with the system used by the RPA", "The RPA stops every time the linked system is revised", etc. FIG. 10 is an ER diagram (Entity Relationship Diagram) showing an example of the data structure of the RPA data managed by the data management unit 12. As shown in FIG. 10, the present device 10 links and manages each RPA data, and generates aggregated data. Note that the system screen master, system revision screen, robot linkage, and system used in FIG. 10 are also the RPA data. The development task of the "development progress data" in FIG. 10 means, for example, the work content of development such as design, manufacturing, and unit testing. Specifically, for example, when the development of an RPA is started, the device 10 registers the linked system and the target screen of the RPA in the device 10, and when the revision information of the linked system is acquired, the device 10 visualizes the range of influence due to the revision of the linked system, identifies the range of influence on the RPA under development or in operation, and outputs the target RPA and its development progress status as aggregate data when the linked system name and screen name to be revised are input. The visualization can be performed by the BI tool, and an example of the visualization will be described in the fourth embodiment. In this way, according to the present invention, each data generated at different times can be associated as a whole by the development application number. Therefore, for example, revision information of the linked system can be collected in advance, and the RPA can be repaired before it is stopped, so business is not stopped. In addition, since the RPA is not stopped, recovery work is not required.

[0049] FIG. 11 is an example of application of the present invention to an inquiry item of "I want to know the issuance status of the RPA linked system login ID." Specifically, the inquiry item is that the development is delayed because the ID of the linked system required for the development of the RPA is not issued. In this case, the device 10 generates aggregated data based on each RPA data shown in FIG. 11. Specifically, the device 10 registers the linked system and the target screen of the RPA in the device 10 at the start of the development of the RPA, manages the issuance status from the timing of the application for issuance of the RPA linked system login ID, and outputs the target RPA and its development progress status as aggregated data when the development application number to be revised is input. The RPA linked system login ID is applied for issuance to, for example, the supervisory department of the linked system. In this way, according to the present invention, each data generated at different times can be associated as a whole by the development application number. Therefore, for example, the development delay is reduced, thereby reducing the standby man-hours and the costs related to development management. In addition, it enables the early introduction of RPA.

[0050] [Embodiment 4] The visualization of the aggregated data will be described with reference to Figures 12 to 15. Note that the RPA data, inquiry items, and aggregated data shown in this embodiment are merely examples, and are not limited to these.

[0051] 12 and 13 are examples of visualization of aggregated data generated for RPA that was the subject of an inquiry item of "I want to see the introduction effect." Specifically, the aggregated data shown in Figs. 12 to 15 visualizes the reduced man-hours (cost) in graphs, numerical values, etc. based on the extraction conditions. Specifically, the graph in the upper part of Fig. 12 is, for example, a graph showing the reduced man-hours created by month. The graph in the lower part of Fig. 12 is, for example, a stacked graph showing the reduced man-hours created. The numerical values ​​shown in Fig. 13 are, for example, data in which the unit of business divisions is used as the business area, and the number of RPAs is aggregated in that unit.

[0052] Figure 14(A) is an example of visualization of aggregated data generated for the RPA that was the subject of an inquiry item, "I would like to see the development progress and release schedule." Specifically, the aggregated data shown in Figure 14(A) visualizes the RPA introduction schedule and development progress for each task to be automated in a case list.

[0053] Figure 14(B) is an example of visualization of aggregated data generated for the RPA that was the subject of the inquiry, "I want to know the operation status." Specifically, the aggregated data shown in Figure 14(B) is visualized by listing the RPA execution results and execution schedules for each task to be automated.

[0054] Fig. 15(A) is an example of visualization of aggregated data generated for RPAs that are the subject of inquiries such as "I want to know the linked system information" and "I want to know which RPA is using the linked system." Specifically, the aggregated data shown in Fig. 15(A) is visualized by listing the revision information of the linked system and breaking it down by item.

[0055] Figure 15(B) is an example of visualization of aggregated data generated for the RPA that was the subject of the inquiry, "I would like to make effective use of the license." Specifically, the aggregated data shown in Figure 15(B) is visualized by graphing the RPA operation status.

[0056] [Embodiment 5] The program of the present embodiment is a program for causing a computer to execute each step of the method of the present invention as a procedure. In the present invention, the "procedure" may be read as "processing." The program of the present embodiment may be recorded, for example, in a computer-readable recording medium. The recording medium is not particularly limited, and examples thereof include a read-only memory (ROM), a hard disk (HD), and an optical disk.

[0057] Although the present invention has been described above with reference to the embodiment, the present invention is not limited to the above embodiment. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0058] <Additional Notes> Some or all of the above embodiments may be described as follows, but are not limited to the following supplementary notes. (Appendix 1) The system includes a data acquisition unit, a data management unit, an inquiry item acquisition unit, a data aggregation unit, and an aggregated data output unit, The data acquisition unit acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data regarding the development of RPA, The RPA system data is data related to a system for which RPA is used, The RPA operation management data is data related to the operation and management of the developed RPA, The data management unit manages the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition unit acquires an inquiry item for the RPA, The data aggregation unit generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operations management data linked by the identifier with respect to the RPA that is the subject of the inquiry item, and The aggregated data output unit outputs the generated aggregated data. RPA development and operation management device. (Appendix 2) The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data relating to an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for an RPA related to the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, the development request data, the development-related organization data, and the development progress data are linked to each other using the development application number as the identifier. Attachment 1 describes an RPA development and operation management device. (Appendix 3) The RPA system data includes RPA partner system data and RPA use system data, The RPA partner system data includes data on the partner system that is the target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA utilization system data are linked to each other using the development application number as the identifier. Attachment 2 describes an RPA development and operation management device. (Appendix 4) The RPA operation management data includes RPA management data and RPA operation data, The RPA management data includes an RPA cooperation destination system login ID for each RPA, The RPA management data and the RPA operation data are linked to each other using the development application number as the identifier. 4. The RPA development and operation management device according to claim 2 or 3. (Appendix 5) Further, a display processing unit is included, The display processing unit executes a process of displaying the outputted aggregated data. 5. An RPA development and operation management device according to any one of appendix 1 to 4. (Appendix 6) Including RPA development and operation management equipment, RPA related terminals, and RPA-equipped terminals, the RPA development and operation management device and the RPA-equipped terminal are capable of communicating with each other via a communication line network; The RPA development and operation management device and the RPA related party terminal can communicate with each other via a communication line network, The RPA development and operation management device is an apparatus according to any one of Supplementary Notes 1 to 5, The data acquisition unit of the RPA development and operation management device acquires the RPA data from the RPA-related party terminal and the RPA-equipped terminal, The inquiry item acquisition unit of the RPA development and operation management device acquires an inquiry item for the RPA from the RPA-related party terminal, The aggregated data output unit of the RPA development and operation management device outputs the generated aggregated data to the RPA related party terminal. RPA development and operation management system. (Appendix 7) The method includes a data acquisition step, a data management step, an inquiry item acquisition step, a data aggregation step, and an aggregated data output step. The data acquisition step acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data regarding the development of RPA, The RPA system data is data related to a system for which RPA is used, The RPA operation management data is data related to the operation and management of the developed RPA, The data management step manages the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition step acquires an inquiry item for the RPA, The data aggregation step generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operations management data linked by the identifier, for the RPA that is the subject of the inquiry item; The tabulated data output step outputs the generated tabulated data. RPA development, operation and management methods. (Appendix 8) The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data relating to an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for an RPA related to the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, the development request data, the development-related organization data, and the development progress data are linked to each other using the development application number as the identifier. The RPA development, operation and management method described in Appendix 7. (Appendix 9) The RPA system data includes RPA partner system data and RPA use system data, The RPA partner system data includes data on the partner system that is the target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA utilization system data are linked to each other using the development application number as the identifier. The RPA development, operation and management method described in Appendix 8. (Appendix 10) The RPA operation management data includes RPA management data and RPA operation data, The RPA management data includes an RPA cooperation destination system login ID for each RPA, The RPA management data and the RPA operation data are linked to each other using the development application number as the identifier. An RPA development, operation and management method as described in Appendix 8 or 9. (Appendix 11) Further, a display processing step is included, The display processing step executes a process of displaying the outputted summary data. An RPA development, operation and management method as set forth in any one of Appendices 7 to 10. (Appendix 12) A program for causing a computer to execute procedures including a data acquisition procedure, a data management procedure, an inquiry item acquisition procedure, a data compilation procedure, and a compilation data output procedure, The data acquisition step acquires robotic process automation (RPA) data relating to RPA, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data regarding the development of RPA, The RPA system data is data related to a system for which RPA is used, The RPA operation management data is data related to the operation and management of the developed RPA, The data management step includes managing the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition step acquires an inquiry item for the RPA, The data aggregation step generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operations management data linked by the identifier, for the RPA that is the subject of the inquiry item; The aggregated data output step outputs the generated aggregated data. program. (Appendix 13) The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data relating to an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for an RPA related to the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, the development request data, the development-related organization data, and the development progress data are linked to each other using the development application number as the identifier. 13. The program according to claim 12. (Appendix 14) The RPA system data includes RPA partner system data and RPA use system data, The RPA partner system data includes data on the partner system that is the target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA utilization system data are linked to each other using the development application number as the identifier. 14. The program according to claim 13. (Appendix 15) The RPA operation management data includes RPA management data and RPA operation data, The RPA management data includes an RPA cooperation destination system login ID for each RPA, The RPA management data and the RPA operation data are linked to each other using the development application number as the identifier. 15. The program according to claim 13 or 14. (Appendix 16) Further, a display process step is included, The display processing step executes a process of displaying the outputted summary data. 16. The program according to any one of appendix 12 to 15. (Appendix 17) A computer-readable recording medium having recorded thereon a program according to any one of appendixes 12 to 16. [Industrial Applicability]

[0059] According to the present invention, it is possible to grasp the development and operation status of RPA in accordance with various needs. Therefore, the present invention is useful, for example, in fields where the development and operation (use) of multiple RPAs are carried out simultaneously in parallel. [Explanation of symbols]

[0060] 10 RPA development and operation management device 11 Data Acquisition Section 12 Data Management Department 13. Inquiry Item Acquisition Department 14 Data Collection Section 15. Aggregated data output section 16 Display processing section 20 RPA personnel terminals 30 RPA-equipped terminals 40 Communication Network 50 RPA execution management terminal 101 Central Processing Unit 102 Memory 103 Bus 104 Storage device 105 Input Device 106 Display device 107 Communication Devices

Claims

1. The system includes a data acquisition unit, a data management unit, an inquiry item acquisition unit, a data aggregation unit, and an aggregated data output unit, The data acquisition unit acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data related to the development of RPA, The RPA system data is data related to a system that is a target for RPA use, The RPA operation management data is data related to the operation and management of the developed RPA, The data management unit manages the RPA system data, the RPA development data, and the RPA operation management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition unit acquires an inquiry item for the RPA and an RPA that is the subject of the inquiry item, The inquiry items for the RPA include matters regarding the extent of the impact on the RPA of the revision of the partner system, The data aggregation unit generates aggregation data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operation management data linked by the identifier with respect to the RPA that is the subject of the inquiry item, The aggregated data includes data regarding RPA affected by the revision of the linked system, The aggregated data output unit outputs the generated aggregated data. RPA development and operation management device.

2. The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data regarding an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for the RPA regarding the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, the development request data, the development-related organization data, and the development progress data are linked to each other using the development application number as the identifier. The RPA development and operation management device according to claim 1.

3. The RPA system data includes RPA collaboration destination system data and RPA utilization system data, The RPA partner system data includes data of a partner system that is a target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA utilization system data are linked to each other using the development application number as the identifier. The RPA development and operation management device according to claim 2.

4. The RPA operation management data includes RPA management data and RPA operation data, The RPA management data includes an RPA cooperation destination system login ID for each RPA, The RPA management data and the RPA operation data are linked to each other using the development application number as the identifier. The RPA development and operation management device according to claim 2 or 3.

5. Further, a display processing unit is included, The display processing unit executes a process of displaying the outputted aggregated data. The RPA development and operation management device according to any one of claims 1 to 4.

6. An RPA development and operation management device, an RPA related party terminal, and an RPA-equipped terminal, The RPA development and operation management device and the RPA-equipped terminal are capable of communicating with each other via a communication line network, The RPA development and operation management device and the RPA related party terminal are capable of communicating with each other via a communication line network, The RPA development and operation management device is an apparatus according to any one of claims 1 to 5, The data acquisition unit of the RPA development and operation management device acquires the RPA data from the RPA-related party terminal and the RPA-equipped terminal, The inquiry item acquisition unit of the RPA development and operation management device acquires an inquiry item regarding the RPA from the RPA related party terminal, The aggregated data output unit of the RPA development and operation management device outputs the generated aggregated data to the RPA related party terminal. RPA development and operation management system.

7. The method includes a data acquisition step, a data management step, an inquiry item acquisition step, a data aggregation step, and an aggregated data output step. The data acquisition step acquires robotic process automation (RPA) data, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data related to the development of RPA, The RPA system data is data related to a system that is a target for RPA use, The RPA operation management data is data related to the operation and management of the developed RPA, The data management step manages the RPA system data, the RPA development data, and the RPA operation management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition step acquires an inquiry item for the RPA and an RPA that is the subject of the inquiry item, The inquiry items for the RPA include matters regarding the extent of the impact on the RPA of the revision of the partner system, The data aggregation step generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operation management data linked by the identifier with respect to the RPA that is the subject of the inquiry item, The aggregated data includes data regarding RPA affected by the revision of the linked system, The tabulated data output step outputs the generated tabulated data. RPA development, operation and management methods.

8. The RPA development data includes development application data, development request data, development-related organization data, and development progress data, The development application data includes development application RPA data regarding an RPA for which a development application has been made, The development application RPA data includes a development application number of the RPA for which a development application has been made, The development request data includes data regarding a user's request for the RPA regarding the development application, The development-related organization data includes data on related organizations involved in the development of the RPA related to the development application, The development progress data includes data on the development progress status of the RPA related to the development application, The development application data, the development request data, the development-related organization data, and the development progress data are linked to each other using the development application number as the identifier. The RPA development, operation and management method according to claim 7.

9. The RPA system data includes RPA collaboration destination system data and RPA utilization system data, The RPA partner system data includes data of a partner system that is a target of use of the RPA, The RPA-utilizing system data includes data of a system utilized by the RPA, The RPA cooperation destination system data and the RPA utilization system data are linked to each other using the development application number as the identifier. The RPA development, operation and management method according to claim 8.

10. A program for causing a computer to execute procedures including a data acquisition procedure, a data management procedure, an inquiry item acquisition procedure, a data compilation procedure, and a compilation data output procedure, The data acquisition step includes acquiring robotic process automation (RPA) data related to RPA, The RPA data includes RPA development data, RPA system data, and RPA operation management data, The RPA development data is data related to the development of RPA, The RPA system data is data related to a system that is a target for RPA use, The RPA operation management data is data related to the operation and management of the developed RPA, The data management procedure includes managing the RPA system data, the RPA development data, and the RPA operations management data by linking them to each other using an identifier for each RPA, The inquiry item acquisition step acquires an inquiry item for the RPA and an RPA that is the subject of the inquiry item, The inquiry items for the RPA include matters regarding the extent of the impact on the RPA of the revision of the partner system, The data aggregation step generates aggregated data based on the inquiry item from the RPA system data, the RPA development data, and the RPA operation management data linked by the identifier, with respect to the RPA that is the subject of the inquiry item; The aggregated data includes data regarding RPA affected by the revision of the linked system, The aggregated data output step outputs the generated aggregated data. program.

Images