WO2024127637A1 - Scenario proposing device, scenario proposing method, and scenario proposing program - Google Patents

Scenario proposing device, scenario proposing method, and scenario proposing program Download PDF

Info

Publication number
WO2024127637A1
WO2024127637A1 PCT/JP2022/046413 JP2022046413W WO2024127637A1 WO 2024127637 A1 WO2024127637 A1 WO 2024127637A1 JP 2022046413 W JP2022046413 W JP 2022046413W WO 2024127637 A1 WO2024127637 A1 WO 2024127637A1
Authority
WO
WIPO (PCT)
Prior art keywords
scenario
proposal
unit
work
rpa
Prior art date
Application number
PCT/JP2022/046413
Other languages
French (fr)
Japanese (ja)
Inventor
公雄 土川
諒 内田
泰輔 若杉
晴夫 大石
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to PCT/JP2022/046413 priority Critical patent/WO2024127637A1/en
Publication of WO2024127637A1 publication Critical patent/WO2024127637A1/en

Links

Images

Definitions

  • One aspect of the present invention relates to a scenario proposal device, a scenario proposal method, and a scenario proposal program.
  • the first method is to use a task classification technique, such as that disclosed in Non-Patent Document 1, to analyze the task logs of the tasks being performed at each work center, and to determine which tasks at each work center are eligible for each RPA scenario.
  • a task classification technique such as that disclosed in Non-Patent Document 1
  • the second method is to set up a portal site that can be viewed within the organization and register the RPA scenarios for each work base on this portal site, allowing horizontal deployment between work bases.
  • the third method is to set up a specialized department within the organization, and each work base brings in measures and issues to this specialized department, which then matches the measures and issues with the RPA scenario, thereby developing the RPA scenario.
  • task classification technology can only classify and visualize tasks, and with the first method, the selection of tasks to which the RPA scenario should be applied must be interpreted by a human, which is highly dependent on the individual.
  • the second method also has the problem of the costs involved in setting up a portal site.
  • the uploading party needs to provide an explanation of the RPA scenario on the portal site, and the user needs to understand their own work and then interpret whether the uploaded RPA scenario matches their own work. Therefore, it is highly dependent on the individual on both the uploading and the user sides.
  • the third method requires the establishment of a specialized department. This specialized department must then understand the tasks to which each RPA scenario is applied and interpret whether the RPA scenario matches the tasks being performed at the work site, which is highly dependent on individual skills.
  • This invention was made in response to the above-mentioned circumstances, and its purpose is to provide technology that makes it possible to reduce the amount of work required to create and operate RPA scenarios.
  • the scenario proposal device includes an operation log collection unit, a classification unit, a scenario collection unit, and a proposal unit.
  • the operation log collection unit collects operation logs of operations on computers via a network from computers at multiple bases, each of which performs at least one task using a scenario describing a work procedure and/or one task not using a scenario.
  • the classification unit divides and classifies the operation logs collected by the operation log collection unit to generate a work operation log, which is an operation log for each task.
  • the scenario collection unit collects scenarios introduced at each base from the computers at multiple bases via the network.
  • the proposal unit transmits a scenario introduction proposal via the network to a computer at a base that performs a task for a work operation log that has a degree of agreement with the scenario collected by the scenario collection unit that is equal to or greater than a certain value among the work operation logs generated by the classification unit.
  • RPA scenarios from other locations can be used with less dependency on individual personnel, which can reduce the amount of work required to create and operate RPA scenarios.
  • FIG. 1 is a block diagram showing an example of the hardware configuration of each electronic device included in the scenario proposal system according to the first embodiment.
  • FIG. 2 is a block diagram showing an example of the software configuration of a server serving as a scenario proposal device according to the first embodiment, which is located at the headquarters and constitutes the scenario proposal system.
  • FIG. 3 is a diagram showing an example of the contents of an operation information record for each base for storing operation information for each base in the RAM included in the control unit of the server.
  • FIG. 4 is a block diagram showing an example of the software configuration of a computer located at a base that constitutes the scenario proposal system.
  • FIG. 5 is a flowchart showing the processing procedure and processing contents of the server in the first embodiment.
  • FIG. 6 is a flowchart showing the processing procedure and processing contents of the server's operation log collection and RPA scenario proposal processing in the first embodiment.
  • FIG. 7 is a flowchart showing the procedure and content of the operation log classification process of the server in the first embodiment.
  • FIG. 8 is a flowchart showing the processing procedure and processing contents of the RPA scenario collection processing of the server in the first embodiment.
  • FIG. 9 is a flowchart showing the processing procedure and processing contents of the proposed RPA scenario determination processing of the server in the first embodiment.
  • FIG. 10 is a diagram showing an example of the correspondence between operations in an operation log and operations in an RPA scenario.
  • FIG. 11 is a diagram showing examples of items that can be acquired as an operation log.
  • FIG. 12 is a diagram showing an example of vectors of operations included in one work unit.
  • FIG. 13 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process.
  • FIG. 14 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process.
  • FIG. 15 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process.
  • FIG. 16 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process.
  • FIG. 17 is a block diagram showing an example of the software configuration of a server serving as a scenario proposal device according to the second embodiment.
  • FIG. 18 is a block diagram showing an example of the software configuration of a computer disposed at a base in the second embodiment.
  • FIG. 19 is a flowchart showing the processing procedure and processing contents of the server in the second embodiment.
  • FIG. 20 is a flowchart showing the procedure and content of operation log collection processing of a server in the second embodiment.
  • FIG. 21 is a flowchart showing the processing procedure and processing contents of an RPA scenario proposal process by a server in the second embodiment.
  • FIG. 22 is a flowchart showing the processing procedure and processing contents of an RPA scenario transmission process by a server in the second embodiment.
  • FIG. 23 is a flowchart showing the processing procedure and processing contents of the proposed RPA scenario determination processing of the server in the third embodiment.
  • FIG. 1 is a block diagram showing an example of the hardware configuration of each electronic device included in a scenario proposal system S in the first embodiment.
  • the scenario proposal system S includes multiple electronic devices included in a headquarters H and multiple electronic devices included in each of multiple (three in the example of Fig. 1) bases B.
  • the headquarters H includes, as electronic devices, a server 1, an input device 101, and an output device 102.
  • the base B includes, as electronic devices, a computer 2, an input device 201, and an output device 202.
  • the server 1 at headquarters H and the computer 2 at each location B can communicate with each other via a network NW.
  • Location B is the work location where the actual work is carried out; for example, if headquarters H is the head office of a company, location B can be a remote branch office of the company.
  • the network NW can be a network using a dedicated line such as a VPN (Virtual Private Network), or a network using a public line such as the Internet or a mobile communications network.
  • location B can be each work department within the company, in which case the network NW can be an in-house LAN (Local Area Network), etc.
  • the server 1 in the headquarters H is a scenario proposal device according to the first embodiment.
  • the server 1 comprises a control unit 11, a program storage unit 12, a data storage unit 13, a communication interface 14, and an input/output interface 15. Each element of the server 1 is connected to each other via a bus.
  • the control unit 11 corresponds to the central part of the server 1.
  • the control unit 11 has a processor such as a central processing unit (CPU).
  • the processor may be a multi-core/multi-threaded one, and can execute multiple processes in parallel.
  • the control unit 11 has a ROM (Read Only Memory) as a non-volatile memory area.
  • the control unit 11 has a RAM (Random Access Memory) as a volatile memory area.
  • the processor expands the programs stored in the ROM or the program storage unit 12 into the RAM.
  • the control unit 11 realizes each functional unit described below by the processor executing the programs expanded into the RAM.
  • the control unit 11 constitutes a computer.
  • the program storage unit 12 is configured with a non-volatile memory that can be written to and read from at any time, such as a HDD (Hard Disk Drive) or SSD (Solid State Drive) as a storage medium.
  • the program storage unit 12 stores programs necessary for executing various control processes.
  • the program storage unit 12 stores programs that cause the server 1 to execute processes by each functional unit (described later) realized in the control unit 11.
  • the program storage unit 12 is an example of storage.
  • the data storage unit 13 is configured with a non-volatile memory such as an HDD or SSD as a storage medium that can be written to and read from at any time.
  • a non-volatile memory such as an HDD or SSD as a storage medium that can be written to and read from at any time.
  • the data storage unit 13 is an example of a storage or memory unit.
  • the communication interface 14 includes various interfaces that connect the server 1 to other electronic devices so that they can communicate with each other using a communication protocol defined by the network NW.
  • the input/output interface 15 is an interface that enables communication between the server 1 and each of the input device 101 and the output device 102.
  • the input/output interface 15 may include an interface for wired communication or an interface for wireless communication.
  • the hardware configuration of the server 1 is not limited to the above configuration.
  • the server 1 allows the above components to be omitted or modified, and new components to be added, as appropriate.
  • the input device 101 is an electronic device for inputting information to be provided to the control unit 11, such as a keyboard, a pointing device such as a mouse, a microphone, etc.
  • the output device 102 is an electronic device for outputting information from the control unit 11, such as a display, printer, or speaker.
  • Computer 2 at each site B is an example of a computer that executes at least one task using an RPA scenario that describes a work procedure and at least one task that does not use an RPA scenario.
  • Computer 2 includes a control unit 21, a program storage unit 22, a data storage unit 23, a communication interface 24, and an input/output interface 25. Each element of computer 2 is connected to each other via a bus.
  • the control unit 21 may be equipped with a processor, ROM, and RAM, similar to the control unit 11 in the server 1 of the headquarters H.
  • the processor may be multi-core/multi-threaded, and can execute multiple processes in parallel.
  • the processor loads the program stored in the ROM or the program storage unit 22 into the RAM.
  • the processor executes the program loaded into the RAM, and the control unit 21 realizes each of the functional units described below.
  • the program storage unit 22 may be configured in the same manner as the program storage unit 12 in the server 1 of the headquarters H.
  • the data storage unit 23 may be configured similarly to the data storage unit 13 in the server 1 of the headquarters H.
  • the communication interface 24 may be configured similarly to the communication interface 14 in the server 1 at the headquarters H.
  • the communication interface 24 includes various interfaces that communicatively connect the computer 2 to other electronic devices.
  • the input/output interface 25 may be configured similarly to the input/output interface 15 in the server 1 of the headquarters H.
  • the input/output interface 25 enables communication between the computer 2 and each of the input device 201 and the output device 202.
  • Computer 2 allows the omission and modification of the above components and the addition of new components as appropriate.
  • the input device 201 is an electronic device for inputting information to be provided to the control unit 21, such as a keyboard, a pointing device such as a mouse, a microphone, etc.
  • the output device 202 is an electronic device for outputting information from the control unit 21, such as a display, printer, or speaker.
  • the server 1 in the headquarters H includes an operation log collection unit 111, a log classification unit 112, a scenario collection unit 113, a coincidence calculation unit 114, a combination extraction unit 115, and a scenario proposal unit 116.
  • Each functional unit is realized by the execution of a program by the control unit 11. It can also be said that each functional unit is included in the control unit 11 or the processor. Each functional unit can be read as the control unit 11 or the processor.
  • Each functional unit may also be realized in various other forms, including integrated circuits such as ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (field-programmable gate array), GPU (Graphics Processing Unit), etc.
  • the server 1 includes an operation log memory unit 131, a classification result memory unit 132, a scenario memory unit 133, and a proposal memory unit 134.
  • the operation log storage unit 131, the classification result storage unit 132, the scenario storage unit 133, and the proposal storage unit 134 are realized by the data storage unit 13.
  • the operation log collection unit 111 collects operation information transmitted from the computer 2 at each base B via the network NW through the communication interface 14 each time an operation is performed on the computer 2 by the input device 201, and generates an operation log for each base B.
  • FIG. 3 is a diagram showing an example of the contents of the operation information record 111R for each base for storing the operation information for each base in the RAM provided in the control unit 11 of the server 1.
  • the operation log collection unit 111 receives operation information from the computer 2 at the base B, it temporarily stores the operation information together with the reception time in the operation information record 111R having the base ID of the base B provided in the RAM.
  • the base ID is an example of base information for uniquely identifying each base B.
  • the operation log collection unit 111 adds and stores the operation information and reception time temporarily stored in the operation information record 111R to the operation log of the base B stored in the operation log storage unit 131. In this way, the operation log collection unit 111 collects the operation log for each base B.
  • the operation log collection unit 111 is an example of an operation log collection unit that collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW.
  • the operation log collection unit 111 also determines whether or not work has been completed on all computers 2 at bases B based on the received operation information, and if it determines that work has been completed, transmits this to the log classification unit 112. For example, when operation information is received indicating that an operation to turn off the power of a computer 2 has been performed, the operation log collection unit 111 can determine that work on that computer 2 has been completed. Note that there may be bases B that do not turn off the power of their computers 2 even when work for the day is completed. Therefore, the operation log collection unit 111 may be configured to determine that work on that computer 2 has been completed when no operation information is received for a specified time, such as three hours.
  • Whether or not this specified time has passed can be easily determined by comparing the reception time of the operation information record 111R with the current time.
  • the operation log collection unit 111 transmits the completion of work to the log classification unit 112, it clears the operation information record 111R for the base B.
  • the operation log collection unit 111 judges whether each computer 2 starts work again after judging that work on each computer 2 has been completed, based on the received operation information. For example, when operation information indicating that an operation to turn on the computer 2 has been performed is received, the operation log collection unit 111 can judge that work on the computer 2 has started. If it judges that work has started, the operation log collection unit 111 judges whether an RPA scenario introduction proposal has been sent to the computer 2 of the site B that started the work via the communication interface 14 through the network NW. As shown in FIG. 3, the operation information record 111R is configured to temporarily store a sent flag in addition to the operation information and the reception time.
  • the operation log collection unit 111 checks the sent flag in the operation information record 111R of the corresponding site, and if the flag is cleared, it can judge that an RPA scenario introduction proposal has not been sent. If it is determined that the RPA scenario introduction proposal has not been sent, the operation log collection unit 111 instructs the scenario proposal unit 116 to send the RPA scenario introduction proposal to the computer 2 at the site B via the network NW via the communication interface 14.
  • the log classification unit 112 When the log classification unit 112 is notified by the operation log collection unit 111 that work has been completed on the computers 2 of all bases B, it uses a work classification technique, such as that disclosed in Non-Patent Document 1, to divide and classify the operation logs of each base B stored in the operation log storage unit 131 into work units, and generates a work operation log that is an operation log for each work unit. Then, the log classification unit 112 saves the generated work operation log for each base B in the classification result storage unit 132.
  • the log classification unit 112 is an example of a classification unit that divides and classifies the operation logs collected by the operation log collection unit, and generates a work operation log that is an operation log for each work unit.
  • the scenario collection unit 113 collects the RPA scenarios installed in the computers 2 at each site B from the computers 2 via the network NW through the communication interface 14, and records the collected sets of RPA scenarios and site information in the scenario storage unit 133. Specifically, the scenario collection unit 113, for example, transmits a scenario request to the computers 2 at each site B via the network NW through the communication interface 14, requesting the transmission of the RPA scenarios installed in the computers 2. Then, the scenario collection unit 113 receives the RPA scenarios returned from the computers 2 at each site B via the network NW in response to this scenario request, through the communication interface 14.
  • the scenario collection unit 113 is an example of a scenario collection unit that collects scenarios installed in each site B from the computers 2 at multiple sites B via the network NW.
  • the matching calculation unit 114, the combination extraction unit 115, and the scenario proposal unit 116 are an example of a proposal unit that transmits a scenario introduction proposal via the network NW to the computer 2 at the base B that performs work for a work operation log generated by the classification unit that has a matching degree of a certain value or more with the scenario collected by the scenario collection unit.
  • the coincidence calculation unit 114 calculates the degree of coincidence between the work operation logs for each task at each base B stored in the classification result storage unit 132 and the RPA scenarios stored in the scenario storage unit 133 for all combinations. Then, the coincidence calculation unit 114 transmits the calculated degree of coincidence for each combination to the combination extraction unit 115.
  • the coincidence calculation unit 114 is an example of a coincidence calculation unit that calculates the degree of coincidence between the work operation logs generated by the classification unit and the scenarios collected by the scenario collection unit for all combinations.
  • the combination extraction unit 115 extracts combinations whose degree of coincidence is equal to or greater than a certain value among the degrees of coincidence between the combinations of the work operation log and the RPA scenario transmitted from the coincidence calculation unit 114.
  • the combination extraction unit 115 then records the pair of the work of the work operation log and the RPA scenario in the extracted combination in the proposal storage unit 134. In this case, if the combination extraction unit 115 determines that the RPA scenario is an introduced work based on the pair of the RPA scenario and the base information stored in the scenario storage unit 133, it excludes the pair of the work and the RPA scenario from being recorded in the proposal storage unit 134.
  • the proposal storage unit 134 may record RPA scenario information for identifying the RPA scenario stored in the scenario storage unit 133, rather than recording the RPA scenario itself.
  • the combination extraction unit 115 is an example of a combination extraction unit that extracts combinations whose degree of coincidence calculated by the coincidence calculation unit is equal to or greater than a certain value.
  • the scenario proposal unit 116 When the scenario proposal unit 116 is instructed by the operation log collection unit 111 to send an introduction proposal for an RPA scenario to the computer 2 at site B that has started work, the scenario proposal unit 116 sends an introduction proposal proposing the introduction of an RPA scenario suitable for executing the work based on the pair of work and RPA scenario stored in the proposal storage unit 134 via the communication interface 14 and the network NW. Then, the scenario proposal unit 116 sets the transmitted flag in the operation information record 111R corresponding to the site B that sent the introduction proposal, i.e. records "1".
  • the scenario proposal unit 116 receives a proposal acceptance that accepts the introduction proposal, which is sent via the network NW from the computer 2 at site B that received the introduction proposal, via the communication interface 14, it sends the RPA scenario stored in the scenario storage unit 133 to the computer 2 at site B via the communication interface 14 and the network NW.
  • the scenario proposal unit 116 is an example of a scenario proposal unit that transmits an introduction proposal proposing the introduction of a scenario in the extracted combination via the network NW to the computer 2 at site B that performs the work in the combination extracted by the combination extraction unit.
  • the scenario proposal unit 116 is also an example of a proposal unit that transmits the proposed introduction scenario to the computer 2 via the network NW when it receives an acceptance of the proposal via the network NW from the computer 2 at site B that received the scenario introduction proposal.
  • FIG. 4 is a block diagram showing an example of the software configuration of a computer 2 located at a base B that constitutes a scenario proposal system S according to the first embodiment.
  • the computer 2 at site B comprises an operation execution unit 211, an operation information transmission unit 212, a scenario output unit 213, and a proposal acquisition unit 214.
  • Each functional unit is realized by the execution of a program by the control unit 21. It can also be said that each functional unit is comprised by the control unit 21 or a processor. Each functional unit can be read as the control unit 21 or a processor. Each functional unit may also be realized in a variety of other forms, including integrated circuits such as ASIC, DSP, FPGA, GPU, etc.
  • the computer 2 comprises a scenario storage unit 231.
  • the scenario storage unit 231 is realized by the data storage unit 23.
  • the work execution unit 211 executes various tasks according to the work programs for the various tasks stored in the program storage unit 22. At this time, if an RPA scenario describing the work procedure for the task is stored in the scenario storage unit 231, the work execution unit 211 can execute the task using the RPA scenario. If the corresponding RPA scenario is not stored in the scenario storage unit 231, the work execution unit 211 naturally executes the task according to the work program without using the RPA scenario. In executing tasks using or not using this RPA scenario, the work execution unit 211 receives operations from the input device 201 and outputs the work content from the output device 202. The work execution unit 211 transmits operation information indicating the operation received during the execution of the task to the operation information transmission unit 212.
  • the operation information transmission unit 212 transmits the operation information transmitted from the work execution unit 211 to the server 1 in the headquarters H via the network NW via the communication interface 24.
  • the scenario output unit 213 When the scenario output unit 213 receives a scenario request from server 1 of headquarters H via network NW through communication interface 24, it reads out the RPA scenario stored in the scenario memory unit 231. Then, the scenario output unit 213 transmits the read-out RPA scenario to server 1 of headquarters H via network NW through communication interface 24 as the RPA scenario installed at base B.
  • the proposal acquisition unit 214 When the proposal acquisition unit 214 receives an introduction proposal from the server 1 of the headquarters H via the network NW through the communication interface 24, which proposes the introduction of an RPA scenario suitable for the work to be performed at the base B, the proposal acquisition unit 214 outputs the introduction proposal through the output device 202. Then, when the proposal acquisition unit 214 receives an operation to accept the introduction proposal through the input device 201, it transmits the proposal acceptance to the server 1 of the headquarters H via the network NW through the communication interface 24. When the server 1 of the headquarters H that has received the proposal acceptance transmits an RPA scenario via the network NW, the proposal acquisition unit 214 receives it through the communication interface 24 and registers it in the scenario storage unit 231.
  • Example of operation 5 is a flowchart showing the processing procedure and processing contents of the server 1 as a scenario proposal device according to the first embodiment.
  • the server 1 operates to collect an operation log for each operation at each base B, create an introduction proposal when work at the base B ends, for example, at the end of a day, and present the introduction proposal when work at each base B starts the next day.
  • the control unit 11 of the server 1 executes an operation log collection/RPA scenario proposal process that collects operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW (step S11).
  • an operation log collection/RPA scenario proposal process that collects operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW (step S11).
  • a typical example of this operation log collection/RPA scenario proposal process will be described later.
  • control unit 11 of the server 1 executes an operation log classification process that divides and classifies the collected operation logs to generate a work operation log, which is an operation log for each task (step S12).
  • an operation log classification process that divides and classifies the collected operation logs to generate a work operation log, which is an operation log for each task (step S12).
  • control unit 11 of the server 1 executes a PA scenario collection process to collect RPA scenarios introduced at each of the multiple bases B from the computers 2 at the bases B via the network NW (step S13).
  • a PA scenario collection process to collect RPA scenarios introduced at each of the multiple bases B from the computers 2 at the bases B via the network NW (step S13).
  • control unit 11 of the server 1 executes a proposed RPA scenario determination process to determine a proposal for introducing a scenario to be sent via the network NW to the computer at base B that performs the work of the work operation logs that have a degree of match with the collected scenario that is equal to or greater than a certain value among the generated work operation logs (step S14).
  • a proposed RPA scenario determination process to determine a proposal for introducing a scenario to be sent via the network NW to the computer at base B that performs the work of the work operation logs that have a degree of match with the collected scenario that is equal to or greater than a certain value among the generated work operation logs.
  • control unit 11 of the server 1 proceeds to the operation log collection/RPA scenario proposal process of step S11 above, and in this operation log collection/RPA scenario proposal process, sends the introduction proposal for the determined scenario to the corresponding computer 2 at site B via the network NW.
  • FIG. 6 is a flowchart showing the processing procedure and processing contents of the operation log collection and RPA scenario proposal processing of the server 1.
  • FIG. 6 shows a typical example of the processing of step S11.
  • the control unit 11 of the server 1 operates as an operation log collection unit 111 and a scenario proposal unit 116.
  • the processing related to the operation log collection unit 111 will be explained.
  • the control unit 11 determines whether operation information has been received from the computer 2 at any of the bases B via the network NW through the communication interface 14 (step S111). As described above, in the computer 2 at each base B, the operation information transmitting unit 212 transmits operation information indicating operations received from the input device 201, including power-on operation information when the power is turned on, to the server 1 at the headquarters H via the network NW through the communication interface 24.
  • the control unit 11 determines whether or not work has been completed on all of the computers 2 at site B (step S112). As described above, the end of work on the computers 2 at site B can include a time when operation information indicating that a power-off operation has been performed is received from the computers 2 at site B, and a time when no operation information is received from the computers 2 at site B for a specified period of time. If the control unit 11 determines that work has not yet been completed on all of the computers 2 at site B, it proceeds to the processing of step S111 above.
  • step S111 If it is determined in step S111 above that operation information has been received from the computer 2 of one of the locations B, the control unit 11 temporarily stores the received operation information in the operation information record 111R of the location B that sent the operation information (step S113). Specifically, the control unit 11 overwrites the received operation information and its reception time in the operation information record 111R. Therefore, here, the transmitted flag of the operation information record 111R maintains its value.
  • control unit 11 checks the transmission flag of the operation information record 111R of the corresponding base B and determines whether or not the proposal to introduce the RPA scenario has been sent to the source base that sent the operation information (step S114).
  • control unit 11 determines whether the received operation information indicates that an operation to accept the proposal to introduce the RPA scenario has been performed (step S115).
  • control unit 11 determines that the received operation information is not an operation for accepting the introduction proposal, the control unit 11 additionally stores the operation information temporarily stored in the operation information record 111R and the reception time in the operation log of the computer 2 of the relevant site B among the operation logs for each site stored in the operation log storage unit 131 (step S116). After that, the control unit 11 proceeds to the process of step S112 above.
  • step S112 If it is determined in step S112 that the work has been completed on the computers 2 of all bases B, the control unit 11 clears the operation information and the transmission flags temporarily stored in the operation information records 111R for all bases B (step S117). That is, the control unit 11 resets the transmission flags of the corresponding operation information records 111R to "0" and deletes the values of the operation information and the reception time.
  • control unit 11 transitions to the operation log classification process of step S12.
  • This transition to the operation log classification process is an example of the operation log collection unit 111 notifying the log classification unit 112 that work on the computers 2 at all bases B has been completed.
  • FIG. 7 is a flowchart showing the procedure and content of the operation log classification process of the server 1 in the first embodiment.
  • FIG. 7 shows a typical example of the process of step S12.
  • the control unit 11 of the server 1 operates as the log classification unit 112.
  • the control unit 11 refers to the operation log storage unit 131 and determines whether there are any unclassified operation logs (step S121).
  • control unit 11 If it is determined that there is an unclassified operation log, the control unit 11 reads one unclassified operation log from the operation log storage unit 131 (step S122).
  • the control unit 11 then divides and classifies the read operation log into task units to generate a task operation log, which is an operation log for each task unit (step S123).
  • control unit 11 stores the generated work operation log in the classification result storage unit 132 (step S124). After that, the control unit 11 proceeds to the process of step S121.
  • step S121 If it is determined in step S121 that there are no unclassified operation logs, i.e., that all operation logs for each base B stored in the operation log storage unit 131 have been classified, the control unit 11 proceeds to the RPA scenario collection process in step S13.
  • FIG. 8 is a flowchart showing the processing procedure and processing contents of the RPA scenario collection process of the server 1 in the first embodiment.
  • FIG. 8 shows a typical example of the processing of step S13.
  • the control unit 11 of the server 1 operates as a scenario collection unit 113.
  • control unit 11 clears the collected scenarios stored in the scenario storage unit 133, that is, the pairs of RPA scenarios and base information recorded during the previous processing operation (step S131).
  • control unit 11 refers to the scenario storage unit 133 to determine whether there is a location B for which an RPA scenario has not yet been collected (step S132).
  • control unit 11 sends a scenario request to one of the unclassified locations B via the communication interface 14 over the network NW, requesting the transmission of the RPA scenario installed in the computer 2 of that location B (step S133).
  • control unit 11 determines whether or not an RPA scenario returned from the computer 2 at site B via the network NW in response to this scenario request has been received by the communication interface 14 (step S134). If it is determined that an RPA scenario has not been received, the control unit 11 repeats the process of step S134 again. In this way, the control unit 11 waits to receive an RPA scenario.
  • the scenario output unit 213 when the scenario output unit 213 receives a scenario request sent via the network NW, the scenario output unit 213 reads out the implemented RPA scenario stored in the scenario storage unit 231 and transmits it to the server 1 via the network NW. Note that if there is no implemented RPA scenario, the scenario output unit 213 can return a message that there is no scenario.
  • the control unit 11 When it is determined that an RPA scenario transmitted from the computer 2 at base B has been received, the control unit 11 records a pair of the received RPA scenario and base information indicating its sender in the scenario storage unit 133 (step S135).
  • the base information can be a base ID uniquely assigned to each base B, as described above. Note that when no scenario is received, the control unit 11 can record a pair of the sender's base information and no RPA scenario information in the scenario storage unit 133. The control unit 11 then proceeds to the processing of step S132 above.
  • step S132 If it is determined in step S132 that there is no location B for which RPA scenarios have not been collected, the control unit 11 proceeds to the proposed RPA scenario determination process in step S14.
  • FIG. 9 is a flowchart showing the procedure and content of the proposed RPA scenario determination process of the server 1 in the first embodiment.
  • FIG. 9 shows a typical example of the process of step S14.
  • the control unit 11 of the server 1 operates as a coincidence calculation unit 114 and a combination extraction unit 115.
  • the control unit 11 refers to the classification result storage unit 132 and determines whether there are any work operation logs that have not been compared for their degree of consistency with the RPA scenario (step S141).
  • control unit 11 reads one uncompared work operation log from the classification result storage unit 132 (step S142).
  • control unit 11 refers to the scenario storage unit 133 to determine whether there is an RPA scenario that has not been compared for the degree of consistency with the read work operation log (step S143).
  • control unit 11 reads out one uncompared RPA scenario from the scenario storage unit 133 (step S144).
  • control unit 11 compares the read work operation logs with the read RPA scenario (step S145).
  • the method of this comparison is not particularly limited. As an example, the comparison can be made using cosine similarity.
  • control unit 11 when calculating the degree of match between a work operation log and an RPA scenario using cosine similarity, the control unit 11 identifies identical operations among the operations (each row) in the operation log and each operation (node) in the RPA scenario, then creates a vector for each operation and calculates the similarity.
  • FIG 10 is a diagram showing an example of the correspondence between operations in the operation log LOG and operations in an RPA scenario.
  • the control unit 11 can determine identity, for example, from the "win_title" item in the operation log LOG and the window title of the operation target in the node details screen NDS of the RPA scenario (bidirectional arrow AR1).
  • Figure 11 is a diagram showing examples of items that can be acquired as an operation log.
  • the control unit 11 can also determine identity, for example, from the attribute name of the GUI part of the operation target (bidirectional arrow AR2).
  • the control unit 11 creates a vector of each operation and calculates the similarity, for example, in the following manner.
  • the control unit 11 uses a Bag of Word (BoW) to create vectors of each operation (row) in the work operation log and vectors of each operation (node) in the RPA scenario.
  • Fig. 12 is a diagram showing an example of the created vectors of each operation included in the work operation log or RPA scenario of one work unit.
  • the control unit 11 can store such created vectors in its own RAM.
  • the control unit 11 calculates the cosine similarity.
  • the cosine similarity between the vector of the work operation log t n and the vector of the RPA scenario s m is expressed by the following formula.
  • the control unit 11 determines whether the degree of match between the work operation log and the RPA scenario, for example, cosine similarity, is equal to or greater than a predetermined value (step S146). If the control unit 11 determines that the degree of match is not equal to or greater than the predetermined value, it proceeds to the processing of step S143. In this way, the work operation log read out in step S142 is compared with each RPA scenario stored in the scenario storage unit 133. Then, when comparison with all RPA scenarios has been performed, the control unit 11 determines in step S143 that there is no uncompared RPA scenario, and proceeds to the processing of step S141. This allows the control unit 11 to proceed to the comparison processing with the RPA scenario for the next uncompared work operation log stored in the classification result storage unit 132.
  • a predetermined value for example, cosine similarity
  • step S147 the control unit 11 determines whether the work at base B in the work operation log is a work for which the RPA scenario has already been introduced (step S147).
  • the scenario storage unit 133 stores a pair of an RPA scenario and base information. Therefore, the control unit 11 can refer to the classification result storage unit 132 to confirm which base B the work operation log belongs to, and determine from the scenario storage unit 133 whether the RPA scenario whose degree of match is determined to be equal to or greater than a certain value has already been introduced at that base B.
  • the control unit 11 proceeds to the processing of step S143 above.
  • control unit 11 records the pair of the work in the work operation log and the RPA scenario as a proposal for base B in the proposal storage unit 134 (step S148). In this way, the control unit 11 can extract combinations of work operation logs and RPA scenarios whose degree of matching is equal to or greater than a certain value. Thereafter, the control unit 11 proceeds to the processing of step S143 described above.
  • control unit 11 can determine the RPA scenarios that can be proposed for introduction for the work operation logs of each classified work stored in the classification result storage unit 132. Then, in the above step S141, if it is determined that there are no uncompared work operation logs, the control unit 11 proceeds to the operation log collection/RPA scenario proposal process of the above step S11.
  • the operation information determined to have been received in the above step S111 may be operation information indicating a power-on operation on the computer 2 of one of the bases B.
  • the control unit 11 determines in the above step S114 that the proposal to introduce the RPA scenario has not been sent to the sending base B.
  • the control unit 11 determines whether or not there is a proposal for the source location B (step S118). Specifically, the control unit 11 determines whether or not a pair of an operation and an RPA scenario is stored in the proposal storage unit 134 as a proposal for the source location B.
  • the control unit 11 transmits an RPA scenario introduction proposal to the source location B via the network NW using the communication interface 14 (step S119). That is, based on the pair of task and RPA scenario stored in the proposal storage unit 134 as a proposal for the source location B, the control unit 11 creates an introduction proposal proposing the introduction of an RPA scenario suitable for executing the task, and transmits it to the source location B.
  • control unit 11 sets the transmitted flag of the operation information record 111R corresponding to the base B that transmitted the introduction proposal, i.e., records "1" (step S1110). After that, the control unit 11 proceeds to the process of step S116, and additionally stores the operation information indicating the power-on operation and the reception time in the operation log of the computer 2 of the base B in the operation log storage unit 131.
  • step S118 If it is determined in step S118 that there is no proposal for the source location B, the control unit 11 proceeds to the process of step S1110, where the control unit 11 sets the transmitted flag of the operation information record 111R corresponding to location B, i.e., records "1", although no introduction proposal has been transmitted.
  • the proposal acquisition unit 214 when the proposal acquisition unit 214 receives the introduction proposal sent via the network NW, the proposal acquisition unit 214 presents the proposed work and an RPA scenario that can be introduced into that work via the output device 202.
  • the operation information transmission unit 212 transmits operation information of the operation to accept the introduction proposal to the server 1 via the network NW.
  • control unit 11 determines in step S115 that the received operation information is an operation to accept the introduction proposal, it reads out the RPA scenario proposed for introduction from the scenario storage unit 133 and transmits it to the computer 2 at site B via the network NW via the communication interface 14 (step S1111). Thereafter, the control unit 11 proceeds to the processing of step S116, and additionally stores the operation information indicating the operation of accepting the proposal and the reception time in the operation log of the computer 2 at site B in the operation log storage unit 131.
  • the proposal acquisition unit 214 when the proposal acquisition unit 214 receives the RPA scenario sent via the network NW, the proposal acquisition unit 214 stores the RPA scenario in the scenario storage unit 231. Then, when performing subsequent work that can use the RPA scenario, the RPA scenario is used to perform the work.
  • Figures 13 to 16 are diagrams showing an example of a comparison between each operation log and each RPA scenario in the proposed RPA scenario determination process.
  • there are three bases B namely, branches A, B, and C.
  • branch A the operation log t1 of operation w1 , the operation log t2 of operation w2 , and the operation log t3 of operation w3 are stored as operation logs at branch A in the classification result storage unit 132 by the operation log collection/RPA scenario proposal process and the operation log classification process, and a pair of branch A and RPA scenario s1 is stored in the scenario storage unit 133 by the RPA scenario collection process.
  • the operation log t4 for operation w4 , the operation log t5 for operation w5, and the operation log t6 for operation w6 are stored in the classification result storage unit 132 as work operation logs for branch B by the operation log collection/RPA scenario proposal process and the operation log classification process, and a pair of branch B and RPA scenario s2 and a pair of branch B and RPA scenario s3 are stored in the scenario storage unit 133 by the RPA scenario collection process.
  • the operation log t7 for operation w7 , the work operation log t8 for operation w8, and the work operation log t9 for operation w9 are stored in the classification result storage unit 132 as work operation logs for branch C by the operation log collection / RPA scenario proposal process and the operation log classification process.
  • the proposed RPA scenario determination process calculates the degree of similarity between nine work operation logs t1 , t2 , ..., t9 for work w1 , w2 , ..., w9 being performed at branches A , B, and C and RPA scenarios s1 , s2 , and s3 , and extracts combinations with a high degree of similarity (above a certain value).
  • the degree of match between the work operation log t1 and the RPA scenario s1 is judged. If the degree of match is judged to be low, it is compared with the RPA scenarios s2 and s3 . If the degree of match is low, the work operation log t2 is compared with the RPA scenarios s1 , s2 , and s3 . If the degree of match is also low, the next comparison is made with the work operation log t3 .
  • step S147 it is determined in step S147 that the RPA scenario s1 , whose degree of match is determined to be equal to or greater than a certain value, has already been introduced at the base B (branch A), the introduction of this RPA scenario s1 is not proposed to branch A. Therefore, the work operation log t3 is compared with the next RPA scenario s2 .
  • the process similarly proceeds to comparing the work operation log t3 with the RPA scenarios s2 and s3 , comparing the work operation log t4 of branch B with the RPA scenarios s1 , s2 , and s3 , and comparing the work operation log t5 with the RPA scenarios s1 , s2 , and s3 .
  • step S147 it is determined in step S147 that the RPA scenario s1 , whose degree of match is determined to be equal to or greater than a certain value, has not been introduced to the base B (branch B). Therefore, in order to propose to branch B that the RPA scenario s1 be introduced to the work w6 , which is the work of the work operation log t6 , the pair of the work w6 and the RPA scenario s1 is stored in the proposal storage unit 134.
  • the work operation log t6 is compared with the RPA scenarios s2 and s3
  • the work operation log t7 of branch C is compared with the RPA scenarios s1 , s2 , and s3
  • the proposed RPA scenario determination process is terminated.
  • the work operation log t8 is further determined to have a high degree of agreement with the RPA scenario s3 , and therefore the pair of the work w8 and the RPA scenario s3 is stored in the proposal storage unit 134 in order to propose to branch C that the RPA scenario s3 be introduced into the work w8 , which is the work of the work operation log t8 .
  • the server 1 collects operation logs of operations on the computers 2 via the network NW from the computers 2 at multiple bases B, each of which performs at least one task using an RPA scenario that describes a task procedure and one that does not use an RPA scenario, divides and classifies the collected operation logs to generate task operation logs that are operation logs for each task, and collects the RPA scenarios introduced at each base B from the computers 2 at multiple bases B via the network NW. Then, the server 1 transmits a proposal for introducing the RPA scenario via the network NW to the computers 2 at the base B that perform tasks for task operation logs that have a degree of agreement with the collected RPA scenario among the generated task operation logs.
  • the server 1 matches the collected RPA scenario with the task operation logs of the tasks at each base B to propose the introduction of the RPA scenario to the computers 2 at the base B that perform tasks for which an RPA scenario has not been introduced.
  • each base B can know that a similar RPA scenario exists at the other bases B, and can consider whether to use the RPA scenario at the other bases B. Therefore, since it is less dependent on individuals and it becomes possible to use RPA scenarios from other locations, it is possible to reduce the amount of work required to create and operate RPA scenarios.
  • the server 1 calculates the degree of match between the generated work operation logs and the collected RPA scenarios for all combinations, extracts combinations for which the degree of match is a certain value or higher, and transmits an introduction proposal proposing the introduction of an RPA scenario for the extracted combination via the network NW to the computer 2 at the site B that performs the work for the extracted combination. Therefore, by using the degree of match, it is possible to thoroughly and easily determine whether an RPA scenario can be introduced for each work being performed at each site B.
  • the server 1 only sends a proposal to introduce an RPA scenario to the computer 2 at site B that is not executing work using an RPA scenario with a degree of similarity equal to or greater than a certain value. This makes it possible to prevent the waste of communication resources for the computer 2 that has already introduced the RPA scenario.
  • the server 1 generates an operation log from the operation information transmitted from the computer 2 at base B via the network NW, and starts operations subsequent to classifying the collected operation log in response to detection of the end of work by the computer 2 at base B based on the operation information, and transmits an introduction proposal for an RPA scenario in response to detection of the start of work by the computer 2 at base B based on the operation information.
  • the server 1 collects operation logs for each operation at each base B, creates an introduction proposal when work at base B ends, such as at the end of the day, and transmits the introduction proposal when work at each base B starts the next day. This makes it possible to prevent an introduction proposal from being presented while work is being performed at base B.
  • the server 1 when the server 1 receives an acceptance of the proposal via the network NW from the computer 2 at site B that received the proposal to introduce the RPA scenario, it transmits the proposed RPA scenario to the computer 2 via the network NW. Therefore, by immediately transmitting the RPA scenario to the computer 2 that accepted the proposal, the introduction work of the RPA scenario on the computer at site B can be quickly carried out.
  • (Configuration example) 17 is a block diagram showing an example of the software configuration of the server 1 as a scenario proposal device according to the second embodiment.
  • the control unit 11 of the server 1 in the headquarters H in this embodiment includes, as functional units, an operation log collection unit 117 and a scenario proposal unit 118 instead of the operation log collection unit 111 and the scenario proposal unit 116.
  • the data storage unit 13 does not include the proposal storage unit 134.
  • the operation log collection unit 117 transmits a log request to the computer 2 at each location B via the network NW using the communication interface 14 at any timing, receives the operation log transmitted from the computer 2 in response to this log request, and stores it in the operation log storage unit 131.
  • the arbitrary timing may be a preset timing such as midnight, or may be the timing of an instruction to collect operation logs from the user via the input device 101.
  • the operation log collection unit 117 is an example of an operation log collection unit that collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW.
  • the log classification unit 112 starts an operation of dividing and classifying the operation logs of each base B stored in the operation log storage unit 131 into task units at an arbitrary timing, regardless of the operation of the operation log collection unit 117, and generating a work operation log, which is an operation log for each task unit.
  • the arbitrary timing may be a preset timing, such as 1:00 a.m., or may be the timing of a user's instruction to generate a work operation log via the input device 101.
  • the combination extraction unit 115 also transmits the pair of the work in the work operation log and the RPA scenario in the extracted combination to the scenario suggestion unit 118.
  • the scenario proposal unit 118 When the scenario proposal unit 118 receives a pair of an operation and an RPA scenario from the combination extraction unit 115, the scenario proposal unit 118 transmits an introduction proposal proposing the introduction of an RPA scenario suitable for executing the operation based on the pair of the operation and the RPA scenario to the computer 2 at the site B that executes the operation via the communication interface 14 and the network NW. Then, when the scenario proposal unit 118 receives a proposal acceptance that accepts the introduction proposal transmitted via the network NW from the computer 2 at the site B that received the introduction proposal via the communication interface 14, the scenario proposal unit 118 transmits the RPA scenario stored in the scenario storage unit 133 to the computer 2 at the site B via the communication interface 14 and the network NW.
  • the scenario proposal unit 118 is an example of a scenario proposal unit that transmits an introduction proposal proposing the introduction of a scenario in the extracted combination via the network NW to the computer 2 at the site B that executes the operation in the combination extracted by the combination extraction unit.
  • the scenario proposal unit 118 is an example of a proposal unit that, when it receives a proposal acceptance via the network NW from the computer 2 at site B that received the scenario introduction proposal, transmits the scenario proposed for introduction to the computer 2 via the network NW.
  • FIG. 18 is a block diagram showing an example of the software configuration of the computer 2 arranged at the base B in the second embodiment.
  • the computer 2 at the base B in this embodiment has, as functional units, an operation log recording unit 215 and a log output unit 216 instead of the operation information transmission unit 212.
  • the data storage unit 23 further has an operation log storage unit 232.
  • the operation log recording unit 215 updates the operation log stored in the operation log storage unit 232 by additionally recording the operation information transmitted from the task execution unit 211 to the operation log.
  • the operation log may include the operation time of the operation information.
  • the log output unit 216 When the log output unit 216 receives a log request from the server 1 via the network NW, it transmits the operation log stored in the operation log storage unit 232 to the server 1 via the network NW.
  • Example of operation 19 is a flowchart showing the processing procedure and processing contents of the server 1 in the second embodiment.
  • a log is recorded at each site B every time an operation is performed at each site B, and the server 1 operates to collect the logs from each site B at any timing and create a proposal.
  • the control unit 11 of the server 1 executes an operation log collection process to collect operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW at any timing (step S15).
  • an operation log collection process to collect operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW at any timing (step S15).
  • a typical example of this operation log collection process will be described later.
  • the control unit 11 of the server 1 determines whether or not to implement the proposed RPA scenario (step S16). For example, the control unit 11 can determine this based on whether or not a preset time has arrived, or whether or not a user has issued an instruction to generate a work operation log via the input device 101. If it is determined that the proposed RPA scenario will not be implemented, the control unit 11 proceeds to the processing of step S15 above.
  • control unit 11 executes the operation log classification process of step S12 and the PA scenario collection process of step S13, as in the first embodiment.
  • control unit 11 of the server 1 executes an RPA scenario proposal process to send an RPA scenario introduction proposal via the network NW to the computer at base B that executes the work of the work operation logs that have a degree of match with the collected scenario that is equal to or greater than a certain value among the generated work operation logs (step S17).
  • RPA scenario proposal process A typical example of this RPA scenario proposal process will be described later.
  • the control unit 11 of the server 1 then proceeds to the operation log collection process of step S15 above.
  • the server 1 control unit 11 executes an RPA scenario transmission process to transmit the RPA scenario via the network NW to the computer 2 of site B that accepted the proposal (step S18). A typical example of this RPA scenario transmission process will be described later. Then, the control unit 11 of the server 1 proceeds to the operation log collection process of step S15.
  • FIG. 20 is a flowchart showing the procedure and content of the operation log collection process of the server 1 in the second embodiment.
  • FIG. 20 shows a typical example of the process of step S15.
  • the control unit 11 of the server 1 operates as the operation log collection unit 117.
  • the control unit 11 determines whether or not it is time to collect an operation log, which is an arbitrary timing (step S151). If it is determined that it is not time to collect the operation log, the control unit 11 proceeds to the process of step S16.
  • control unit 11 refers to the operation log storage unit 131 and determines whether there is a location B for which operation logs have not yet been collected (step S152).
  • control unit 11 sends a log request to one of the locations B from which operation logs have not been collected, via the communication interface 14 and the network NW, requesting the sending of the operation logs stored in the computer 2 of that location B (step S153).
  • the log output unit 216 of the computer 2 at site B When the log output unit 216 of the computer 2 at site B receives a log request sent via the network NW, the log output unit 216 reads out the operation log stored in the operation log memory unit 232 and transmits it to the server 1 via the network NW.
  • the control unit 11 receives the operation log returned from the computer 2 at the site B via the network NW in response to the log request through the communication interface 14 (step S154).
  • control unit 11 records a pair of the received operation log and the base information indicating its sender in the operation log storage unit 131 (step S155).
  • the base information can be a base ID uniquely assigned to each base B. Thereafter, the control unit 11 proceeds to the process of step S152.
  • step S152 If it is determined in step S152 that there is no location B for which operation logs have not been collected, the control unit 11 proceeds to the processing of step S16.
  • FIG. 21 is a flowchart showing the processing procedure and processing contents of the RPA scenario proposal processing of the server 1 in the second embodiment.
  • FIG. 21 shows a typical example of the processing of step S17.
  • the control unit 11 of the server 1 operates as a coincidence calculation unit 114, a combination extraction unit 115, and a scenario proposal unit 118.
  • control unit 11 refers to the classification result storage unit 132 to determine whether there are any uncompared work operation logs that have not been compared for their degree of similarity with the RPA scenario (step S171).
  • control unit 11 If it is determined that there is an uncompared work operation log, the control unit 11 reads one uncompared work operation log from the classification result storage unit 132 (step S172), similar to step S142 in the first embodiment.
  • control unit 11 refers to the scenario storage unit 133 to determine whether there is an RPA scenario that has not been compared with the read work operation log for degree of similarity (step S173).
  • control unit 11 reads out one uncompared RPA scenario from the scenario storage unit 133 (step S174), similar to step S144 in the first embodiment.
  • control unit 11 compares the read work operation logs with the read RPA scenario (step S175), similar to step S145 in the first embodiment.
  • control unit 11 determines whether the degree of match between the work operation log and the RPA scenario, for example the cosine similarity, is equal to or greater than a predetermined value (step S176), similar to step S146 in the first embodiment. If the control unit 11 determines that the degree of match is not equal to or greater than the predetermined value, it proceeds to the process of step S173.
  • step S176 determines whether the degree of match between the work operation log and the RPA scenario is equal to or greater than a certain value.
  • the control unit 11 determines whether the work at base B in the work operation log is a work for which the RPA scenario has already been introduced (step S177), similar to step S147 in the first embodiment.
  • step S177 determines whether the work at base B in the work operation log is a work for which the RPA scenario has already been introduced (step S177), similar to step S147 in the first embodiment.
  • the control unit 11 proceeds to the processing of step S173.
  • control unit 11 creates an RPA scenario introduction proposal based on the pair of the task and the RPA scenario in the task operation log, and transmits it via the communication interface 14 over the network NW to the computer 2 at site B that will execute the task (step S178). After that, the control unit 11 proceeds to the processing of step S173.
  • matching is performed by determining the degree of agreement between the RPA scenarios and work operation logs operated at each base B, and for work at base B that has not yet introduced an RPA scenario among combinations with a high degree of agreement, horizontal expansion can be supported by proposing RPA from base B, which has already introduced an RPA scenario for similar work, to the base B that has not yet introduced an RPA scenario.
  • FIG. 22 is a flowchart showing the procedure and content of the RPA scenario transmission process of the server 1 in the second embodiment.
  • FIG. 22 shows a typical example of the process of step S18.
  • the control unit 11 of the server 1 operates as a scenario suggestion unit 118.
  • the control unit 11 determines whether or not a proposal acceptance transmitted via the network NW has been received from the computer 2 at any of the locations B (step S181). If it is determined that a proposal acceptance has not been received, the control unit 11 transitions to the process of step S18 again.
  • the proposal acquisition unit 214 when the proposal acquisition unit 214 receives the introduction proposal transmitted via the network NW in step S178 of the RPA scenario proposal process, the proposal acquisition unit 214 presents the proposed work and an RPA scenario that can be introduced into that work via the output device 202.
  • the operation information transmission unit 212 transmits a proposal acceptance indicating that the introduction proposal is accepted to the server 1 via the network NW.
  • control unit 11 determines in step S181 that it has received a proposal acceptance from the computer 2 of one of the locations B, it reads out the RPA scenario proposed for introduction to that location B in step S178 from the scenario storage unit 133 and transmits it to the computer 2 of that location B via the network NW via the communication interface 14 (step S182). After that, the control unit 11 again proceeds to the processing of step S18.
  • the proposal acquisition unit 214 when the proposal acquisition unit 214 receives the RPA scenario sent via the network NW, the proposal acquisition unit 214 stores the RPA scenario in the scenario storage unit 231. Then, when the work execution unit 211 executes a task that can use the RPA scenario thereafter, the work execution unit 211 uses the RPA scenario to execute the task.
  • the server 1 also collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW, and at any timing divides and classifies the collected operation logs to generate work operation logs that are operation logs for each task, and collects RPA scenarios introduced at each location B from the computers 2 at multiple locations B via the network NW. Then, the server 1 transmits an introduction proposal for the RPA scenario via the network NW to the computers 2 at the location B that execute the work of the work operation logs that have a degree of agreement with the collected RPA scenario among the generated work operation logs. Therefore, in the second embodiment, as in the first embodiment, it is possible to use RPA scenarios at other locations with low dependency on individuals, and therefore it is possible to reduce the creation and operation of the RPA scenario.
  • the server 1 also receives operation logs sent from the computer 2 at site B via the network NW, and classifies the operation logs, collects scenarios, and proposes scenarios at preset times or in response to user instructions. Therefore, there is no need to constantly obtain operation information from the computer 2 at each site B, and operation logs can be collected and kept at any time, preventing the continuous consumption of communication resources. It is also possible to adjust the start timing of processing for scenario proposal based on the collected operation logs.
  • the degree of match between the work operation log and the RPA scenario is calculated one by one, and it is determined whether or not to propose an RPA scenario each time.
  • all the degrees of match between the work operation log and the RPA scenario are calculated, and it is determined whether or not to propose an RPA scenario for the combination with the highest degree of match among all the degrees of match.
  • step S145 if the work operation log and the RPA scenario are compared in step S145, the control unit 11 stores the degree of agreement obtained by the comparison in its own RAM (step S149). Of course, it is also possible to store the degree of agreement in a memory unit by securing the degree of agreement in the data memory unit 23. After that, the control unit 11 proceeds to the processing of step S143. In this way, the work operation log read in step S142 is compared with the RPA scenario read in step S144.
  • step S143 determines in step S143 that there is no uncompared RPA scenario, and proceeds to the processing of step S141.
  • the control unit 11 can proceed to the comparison processing of each RPA scenario with the next uncompared work operation log stored in the classification result memory unit 132. In this way, the control unit 11 can store all the degrees of agreement between the work operation log and the RPA scenario.
  • control unit 11 extracts pairs of work operation logs and RPA scenarios whose degree of matching is equal to or greater than a certain value from all the stored degrees of matching (step S1410).
  • control unit 11 excludes pairs of work operation logs and RPA scenarios in which an RPA scenario has already been introduced into work at site B from among the extracted pairs of work operation logs and RPA scenarios whose degree of match is equal to or greater than a certain value (step S1411).
  • control unit 11 proceeds to the process of step S148, and records a proposal for an RPA scenario for the relevant base B in the proposal storage unit 134 based on each of the remaining pairs of work operation logs and RPA scenarios that have been extracted. After that, the control unit 11 proceeds to the operation log collection and extended UI proposal process of step S11.
  • the proposal to introduce an RPA scenario and the transmission of an actual RPA scenario are separate processes, but the proposal to introduce an RPA scenario may include the RPA scenario itself and transmit it.
  • the proposal acquisition unit 214 of the computer 2 at site B receives such an introduction proposal, it registers the RPA scenario in the scenario storage unit 231 only when the proposal is accepted, and discards the received RPA scenario when the proposal is not accepted.
  • the scenario proposal device may be realized as a single device as described in the above example, or may be realized as multiple devices with distributed functions.
  • the program may be transferred in a state where it is stored in an electronic device, or in a state where it is not stored in an electronic device. In the latter case, the program may be transferred via a network, or in a state where it is recorded on a recording medium.
  • the recording medium is a non-transitory tangible medium.
  • the recording medium is a computer-readable medium.
  • the recording medium may be in any form, such as a CD-ROM or memory card, as long as it is capable of storing the program and is computer-readable.
  • this invention is not limited to the above-described embodiment as it is, and in the implementation stage, the components can be modified and embodied without departing from the gist of the invention.
  • various inventions can be formed by appropriate combinations of multiple components disclosed in the above-described embodiment. For example, some components may be deleted from all of the components shown in the embodiment. Furthermore, components from different embodiments may be appropriately combined.
  • Reference Signs List 1 Server 2: Computer 11, 21: Control unit 12, 22: Program storage unit 13, 23: Data storage unit 14, 24: Communication interface 15, 25: Input/output interface 101, 201: Input device 102, 202: Output device 111, 117: Operation log collection unit 111R: Operation information record 112: Log classification unit 113: Scenario collection unit 114: Matching degree calculation unit 115: Combination extraction unit 116, 118: Scenario proposal unit 131, 232: Operation log storage unit 132: Classification result storage unit 133, 231: Scenario storage unit 134: Proposal storage unit 211: Work execution unit 212: Operation information transmission unit 213: Scenario output unit 214: Proposal acquisition unit 215: Operation log recording unit 216: Log output unit B: Base H: Headquarters LOG: Operation log NDS: Node details screen NW: Network S: Scenario proposal system

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

In one embodiment of the present invention, a scenario proposing device comprises an operation log collection unit, a classification unit, a scenario collection unit, and a proposing unit. The operation log collection unit collects, via the network, operation logs of operations on computers from computers at a plurality of locations, each computer performing (a) task(s) using a scenario describing a task procedure and/or (a) task(s) not using a scenario. The classification unit divides and classifies the operation logs collected by the operation log collection unit to generate task operation logs, which are operation logs in units of tasks. The scenario collection unit collects, from the computers at a plurality of locations via the network, scenarios adopted at each location. The proposing unit transmits, via the network, a scenario adoption proposal to a computer at a location that executes the tasks of task operation logs for which the degree of matching with a scenario collected by the scenario collection unit is a certain value or greater from among the task operation logs generated by the classification unit.

Description

シナリオ提案装置、シナリオ提案方法及びシナリオ提案プログラムScenario proposal device, scenario proposal method, and scenario proposal program
 この発明の一態様は、シナリオ提案装置、シナリオ提案方法及びシナリオ提案プログラムに関する。 One aspect of the present invention relates to a scenario proposal device, a scenario proposal method, and a scenario proposal program.
 企業等における稼働削減の方法として、RPA(Robotic Process Automation)やUI拡張等の導入が有る。とりわけ、作業部門の社員がベンダに頼らず自分たちのニーズに即した開発を行う市民開発が脚光を浴びている。しかしながら、或る程度規模の大きい組織においては、部署や支店といった作業拠点単位で独自の施策やRPAシナリオが作成・運用されており、このRPAシナリオの他作業拠点への水平展開の機会は限られていた。 Methods of reducing operations in companies include the introduction of RPA (Robotic Process Automation) and UI extensions. In particular, citizen development, in which employees in operational departments develop software tailored to their own needs without relying on vendors, has been attracting attention. However, in relatively large organizations, unique measures and RPA scenarios are created and operated at each operational base, such as a department or branch office, and there are limited opportunities to horizontally deploy these RPA scenarios to other operational bases.
 ここで、RPAシナリオの十分な水平展開がなされていれば、それぞれ異なる作業拠点で類似の作業に対して重複したRPAシナリオを作成する必要が無くなり、RAPシナリオの作成・運用稼働を削減することができる。そこで、以下のような手法が試みられている。 Here, if RPA scenarios are deployed horizontally to a sufficient extent, there will be no need to create duplicate RPA scenarios for similar tasks at different work locations, and it will be possible to reduce the amount of RPA scenario creation and operation work. Therefore, the following methods are being attempted:
 第1の手法は、例えば非特許文献1に開示されているような作業分類技術を用いて、各作業拠点が実施している作業についてその作業ログを分析することで、各作業拠点での作業の中から、各RPAシナリオの適用対象作業を見極めるというものである。 The first method is to use a task classification technique, such as that disclosed in Non-Patent Document 1, to analyze the task logs of the tasks being performed at each work center, and to determine which tasks at each work center are eligible for each RPA scenario.
 第2の手法は、組織内で閲覧可能なポータルサイトを設置し、このポータルサイトに各作業拠点のRPAシナリオを登録することで、作業拠点間での水平展開を行うというものである。 The second method is to set up a portal site that can be viewed within the organization and register the RPA scenarios for each work base on this portal site, allowing horizontal deployment between work bases.
 第3の手法は、組織内に専門部署を設置し、各作業拠点からのこの専門部署への施策の持ち込み及び課題の持ち込みにより、専門部署において施策及び課題とRPAシナリオとのマッチングを行うことで、RPAシナリオを展開するというものである。 The third method is to set up a specialized department within the organization, and each work base brings in measures and issues to this specialized department, which then matches the measures and issues with the RPA scenario, thereby developing the RPA scenario.
 しかしながら、作業分類技術でできるのは作業分類及び可視化までであり、第1の手法では、RPAシナリオの適用対象業務の選定自体は人が解釈して行う必要が有り、属人性が高い。 However, task classification technology can only classify and visualize tasks, and with the first method, the selection of tasks to which the RPA scenario should be applied must be interpreted by a human, which is highly dependent on the individual.
 また、第2の手法では、ポータルサイトの設置にコストが掛かるという問題が有る。そして、これに加えて、アップロードする側は、RPAシナリオの説明情報をポータルサイトに記載する必要が有り、更に、利用する側においては、自身の作業を理解した上で、アップロードされているRPAシナリオが自身の作業にマッチするかを解釈する必要が有る。よって、アップロードする側、利用する側の何れにおいても、属人性が高い。 The second method also has the problem of the costs involved in setting up a portal site. In addition to this, the uploading party needs to provide an explanation of the RPA scenario on the portal site, and the user needs to understand their own work and then interpret whether the uploaded RPA scenario matches their own work. Therefore, it is highly dependent on the individual on both the uploading and the user sides.
 また、第3の手法では、専門部署を設置する必要が有る。そして、その専門部署が各RPAシナリオの適用対象の作業を理解した上で、作業拠点で実施される作業にRPAシナリオがマッチするかを解釈する必要が有り、属人性が高い。 In addition, the third method requires the establishment of a specialized department. This specialized department must then understand the tasks to which each RPA scenario is applied and interpret whether the RPA scenario matches the tasks being performed at the work site, which is highly dependent on individual skills.
 このように、RPAの適用対象作業の選定や作業に利用可能なRPAシナリオの選定は属人性が高いため、たとえ他作業拠点に利用可能なRPAシナリオが有ったとしても、その利用が難しく、RPAシナリオの作成・運用稼働が高いという課題が有る。 As such, the selection of tasks to which RPA can be applied and the selection of RPA scenarios that can be used for those tasks are highly dependent on the individual, so even if there are RPA scenarios available at other work locations, it is difficult to use them, and there is an issue with the high cost of creating and operating RPA scenarios.
 この発明は、上記事情に着目してなされたもので、その目的とするところは、RPAシナリオの作成・運用稼働の削減を可能とする技術を提供することにある。 This invention was made in response to the above-mentioned circumstances, and its purpose is to provide technology that makes it possible to reduce the amount of work required to create and operate RPA scenarios.
 この発明の一実施形態では、シナリオ提案装置は、操作ログ収集部と、分類部と、シナリオ収集部と、提案部と、を備える。操作ログ収集部は、それぞれ、作業手順を記述したシナリオを使用した作業とシナリオを使用しない作業との少なくとも一方の作業を少なくとも一つ実行する、複数の拠点のコンピュータから、ネットワークを介して、コンピュータに対する操作の操作ログを収集する。分類部は、操作ログ収集部が収集した操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成する。シナリオ収集部は、複数の拠点のコンピュータから、ネットワークを介して、各拠点に導入されているシナリオを収集する。提案部は、分類部が生成した作業操作ログの内、シナリオ収集部が収集したシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点のコンピュータへ、ネットワークを介して、シナリオの導入提案を送信する。 In one embodiment of the present invention, the scenario proposal device includes an operation log collection unit, a classification unit, a scenario collection unit, and a proposal unit. The operation log collection unit collects operation logs of operations on computers via a network from computers at multiple bases, each of which performs at least one task using a scenario describing a work procedure and/or one task not using a scenario. The classification unit divides and classifies the operation logs collected by the operation log collection unit to generate a work operation log, which is an operation log for each task. The scenario collection unit collects scenarios introduced at each base from the computers at multiple bases via the network. The proposal unit transmits a scenario introduction proposal via the network to a computer at a base that performs a task for a work operation log that has a degree of agreement with the scenario collected by the scenario collection unit that is equal to or greater than a certain value among the work operation logs generated by the classification unit.
 この発明の一態様によれば、属人性低く、他拠点のRPAシナリオを利用できるようになるので、RPAシナリオの作成・運用稼働の削減が可能となる。 According to one aspect of the invention, RPA scenarios from other locations can be used with less dependency on individual personnel, which can reduce the amount of work required to create and operate RPA scenarios.
図1は、第1の実施形態におけるシナリオ提案システムに含まれる各電子機器のハードウェア構成の一例を示すブロック図である。FIG. 1 is a block diagram showing an example of the hardware configuration of each electronic device included in the scenario proposal system according to the first embodiment. 図2は、シナリオ提案システムを構成する本部に配置された第1の実施形態に係るシナリオ提案装置としてのサーバのソフトウェア構成の一例を示すブロック図である。FIG. 2 is a block diagram showing an example of the software configuration of a server serving as a scenario proposal device according to the first embodiment, which is located at the headquarters and constitutes the scenario proposal system. 図3は、サーバの制御部が備えるRAMに拠点毎の操作情報を記憶するための拠点毎の操作情報レコードの内容の一例を示す図である。FIG. 3 is a diagram showing an example of the contents of an operation information record for each base for storing operation information for each base in the RAM included in the control unit of the server. 図4は、シナリオ提案システムを構成する拠点に配置されたコンピュータのソフトウェア構成の一例を示すブロック図である。FIG. 4 is a block diagram showing an example of the software configuration of a computer located at a base that constitutes the scenario proposal system. 図5は、第1の実施形態におけるサーバの処理手順と処理内容を示すフローチャートである。FIG. 5 is a flowchart showing the processing procedure and processing contents of the server in the first embodiment. 図6は、第1の実施形態におけるサーバの操作ログ収集・RPAシナリオ提案処理の処理手順と処理内容を示すフローチャートである。FIG. 6 is a flowchart showing the processing procedure and processing contents of the server's operation log collection and RPA scenario proposal processing in the first embodiment. 図7は、第1の実施形態におけるサーバの操作ログ分類処理の処理手順と処理内容を示すフローチャートである。FIG. 7 is a flowchart showing the procedure and content of the operation log classification process of the server in the first embodiment. 図8は、第1の実施形態におけるサーバのRPAシナリオ収集処理の処理手順と処理内容を示すフローチャートである。FIG. 8 is a flowchart showing the processing procedure and processing contents of the RPA scenario collection processing of the server in the first embodiment. 図9は、第1の実施形態におけるサーバの提案RPAシナリオ決定処理の処理手順と処理内容を示すフローチャートである。FIG. 9 is a flowchart showing the processing procedure and processing contents of the proposed RPA scenario determination processing of the server in the first embodiment. 図10は、操作ログ中の操作とRPAシナリオ中の操作との対応の一例を示す図である。FIG. 10 is a diagram showing an example of the correspondence between operations in an operation log and operations in an RPA scenario. 図11は、操作ログとして取得できる項目の例を示す図である。FIG. 11 is a diagram showing examples of items that can be acquired as an operation log. 図12は、一つの作業単位に含まれる各操作のベクトルの一例を示す図である。FIG. 12 is a diagram showing an example of vectors of operations included in one work unit. 図13は、提案RPAシナリオ決定処理における各作業ログと各RPAシナリオの比較の一例を示す図である。FIG. 13 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process. 図14は、提案RPAシナリオ決定処理における各作業ログと各RPAシナリオの比較の一例を示す図である。FIG. 14 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process. 図15は、提案RPAシナリオ決定処理における各作業ログと各RPAシナリオの比較の一例を示す図である。FIG. 15 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process. 図16は、提案RPAシナリオ決定処理における各作業ログと各RPAシナリオの比較の一例を示す図である。FIG. 16 is a diagram showing an example of a comparison between each work log and each RPA scenario in the proposed RPA scenario determination process. 図17は、第2の実施形態に係るシナリオ提案装置としてのサーバのソフトウェア構成の一例を示すブロック図である。FIG. 17 is a block diagram showing an example of the software configuration of a server serving as a scenario proposal device according to the second embodiment. 図18は、第2の実施形態において拠点に配置されたコンピュータのソフトウェア構成の一例を示すブロック図である。FIG. 18 is a block diagram showing an example of the software configuration of a computer disposed at a base in the second embodiment. 図19は、第2の実施形態におけるサーバの処理手順と処理内容を示すフローチャートである。FIG. 19 is a flowchart showing the processing procedure and processing contents of the server in the second embodiment. 図20は、第2の実施形態におけるサーバの操作ログ収集処理の処理手順と処理内容を示すフローチャートである。FIG. 20 is a flowchart showing the procedure and content of operation log collection processing of a server in the second embodiment. 図21は、第2の実施形態におけるサーバのRPAシナリオ提案処理の処理手順と処理内容を示すフローチャートである。FIG. 21 is a flowchart showing the processing procedure and processing contents of an RPA scenario proposal process by a server in the second embodiment. 図22は、第2の実施形態におけるサーバのRPAシナリオ送信処理の処理手順と処理内容を示すフローチャートである。FIG. 22 is a flowchart showing the processing procedure and processing contents of an RPA scenario transmission process by a server in the second embodiment. 図23は、第3の実施形態におけるサーバの提案RPAシナリオ決定処理の処理手順と処理内容を示すフローチャートである。FIG. 23 is a flowchart showing the processing procedure and processing contents of the proposed RPA scenario determination processing of the server in the third embodiment.
 以下、図面を参照して、この発明に係る幾つかの実施形態を説明する。 Below, several embodiments of the present invention will be described with reference to the drawings.
 [第1の実施形態]
 (構成例)
 図1は、第1の実施形態におけるシナリオ提案システムSに含まれる各電子機器のハードウェア構成の一例を示すブロック図である。シナリオ提案システムSは、本部Hに含まれる複数の電子機器と、複数(図1の例では3つ)の拠点Bのそれぞれに含まれる複数の電子機器と、を含む。本部Hは、電子機器として、サーバ1、入力装置101及び出力装置102を備える。拠点Bは、電子機器として、コンピュータ2、入力装置201及び出力装置202を備える。
[First embodiment]
(Configuration example)
Fig. 1 is a block diagram showing an example of the hardware configuration of each electronic device included in a scenario proposal system S in the first embodiment. The scenario proposal system S includes multiple electronic devices included in a headquarters H and multiple electronic devices included in each of multiple (three in the example of Fig. 1) bases B. The headquarters H includes, as electronic devices, a server 1, an input device 101, and an output device 102. The base B includes, as electronic devices, a computer 2, an input device 201, and an output device 202.
 本部Hのサーバ1及び各拠点Bのコンピュータ2は、ネットワークNWを介して互いに通信可能である。拠点Bは、実際に作業が実行される作業拠点であり、例えば、本部Hが企業の本社であれば、拠点Bは企業の遠隔支店であることができる。この場合、ネットワークNWはVPN(Virtual Private Network)等の専用線によるネットワークや、インターネット、モバイル通信網等の公衆回線を利用したネットワークであることができる。また、本部Hが例えば会社の管理部署であれば、拠点Bは会社内の各作業部署であることができ、この場合は、ネットワークNWは社内LAN(Local Area Network)等であることができる。 The server 1 at headquarters H and the computer 2 at each location B can communicate with each other via a network NW. Location B is the work location where the actual work is carried out; for example, if headquarters H is the head office of a company, location B can be a remote branch office of the company. In this case, the network NW can be a network using a dedicated line such as a VPN (Virtual Private Network), or a network using a public line such as the Internet or a mobile communications network. Also, if headquarters H is, for example, the management department of a company, location B can be each work department within the company, in which case the network NW can be an in-house LAN (Local Area Network), etc.
 本部Hのサーバ1は、第1の実施形態に係るシナリオ提案装置である。サーバ1は、制御部11、プログラム記憶部12、データ記憶部13、通信インタフェース14及び入出力インタフェース15を備える。サーバ1が備える各要素は、バスを介して、互いに接続されている。 The server 1 in the headquarters H is a scenario proposal device according to the first embodiment. The server 1 comprises a control unit 11, a program storage unit 12, a data storage unit 13, a communication interface 14, and an input/output interface 15. Each element of the server 1 is connected to each other via a bus.
 制御部11は、サーバ1の中枢部分に相当する。制御部11は、中央処理ユニット(Central Processing Unit:CPU)等のプロセッサを備える。プロセッサは、マルチコア/マルチスレッドのものであって良く、複数の処理を併行して実行することができる。制御部11は、不揮発性のメモリ領域としてROM(Read Only Memory)を備える。制御部11は、揮発性のメモリ領域としてRAM(Random Access Memory)を備える。プロセッサは、ROM又はプログラム記憶部12に記憶されているプログラムをRAMに展開する。プロセッサがRAMに展開されるプログラムを実行することで、制御部11は、後述する各機能部を実現する。制御部11は、コンピュータを構成する。 The control unit 11 corresponds to the central part of the server 1. The control unit 11 has a processor such as a central processing unit (CPU). The processor may be a multi-core/multi-threaded one, and can execute multiple processes in parallel. The control unit 11 has a ROM (Read Only Memory) as a non-volatile memory area. The control unit 11 has a RAM (Random Access Memory) as a volatile memory area. The processor expands the programs stored in the ROM or the program storage unit 12 into the RAM. The control unit 11 realizes each functional unit described below by the processor executing the programs expanded into the RAM. The control unit 11 constitutes a computer.
 プログラム記憶部12は、記憶媒体としてHDD(Hard Disk Drive)又はSSD(Solid State Drive)等の随時書込み及び読出しが可能な不揮発性メモリで構成される。プログラム記憶部12は、各種制御処理を実行するために必要なプログラムを記憶する。例えば、プログラム記憶部12は、制御部11に実現される後述する各機能部による処理をサーバ1に実行させるプログラムを記憶する。プログラム記憶部12は、ストレージの一例である。 The program storage unit 12 is configured with a non-volatile memory that can be written to and read from at any time, such as a HDD (Hard Disk Drive) or SSD (Solid State Drive) as a storage medium. The program storage unit 12 stores programs necessary for executing various control processes. For example, the program storage unit 12 stores programs that cause the server 1 to execute processes by each functional unit (described later) realized in the control unit 11. The program storage unit 12 is an example of storage.
 データ記憶部13は、記憶媒体としてHDD、又はSSD等の随時書込み及び読出しが可能な不揮発性メモリで構成される。データ記憶部13は、ストレージ又は記憶部の一例である。 The data storage unit 13 is configured with a non-volatile memory such as an HDD or SSD as a storage medium that can be written to and read from at any time. The data storage unit 13 is an example of a storage or memory unit.
 通信インタフェース14は、ネットワークNWにより定義される通信プロトコルを使用して、サーバ1を他の電子機器と通信可能に接続する種々のインタフェースを含む。 The communication interface 14 includes various interfaces that connect the server 1 to other electronic devices so that they can communicate with each other using a communication protocol defined by the network NW.
 入出力インタフェース15は、サーバ1と入力装置101及び出力装置102のそれぞれとの通信を可能にするインタフェースである。入出力インタフェース15は、有線通信のインタフェースを備えていても良いし、無線通信のインタフェースを備えていても良い。 The input/output interface 15 is an interface that enables communication between the server 1 and each of the input device 101 and the output device 102. The input/output interface 15 may include an interface for wired communication or an interface for wireless communication.
 なお、サーバ1のハードウェア構成は、上述の構成に限定されるものではない。サーバ1は、適宜、上述の構成要素の省略、及び変更並びに新たな構成要素の追加を可能とする。 The hardware configuration of the server 1 is not limited to the above configuration. The server 1 allows the above components to be omitted or modified, and new components to be added, as appropriate.
 入力装置101は、キーボード、マウス等のポインティングデバイス、マイクロフォン、等の制御部11に与えるべき情報を入力するための電子機器である。 The input device 101 is an electronic device for inputting information to be provided to the control unit 11, such as a keyboard, a pointing device such as a mouse, a microphone, etc.
 出力装置102は、ディスプレイ、プリンタ、スピーカ、等の制御部11からの情報を出力するための電子機器である。 The output device 102 is an electronic device for outputting information from the control unit 11, such as a display, printer, or speaker.
 各拠点Bのコンピュータ2は、作業手順を記述したRPAシナリオを使用した作業とRPAシナリオを使用しない作業との少なくとも一方の作業を少なくとも一つ実行するコンピュータの一例である。コンピュータ2は、制御部21、プログラム記憶部22、データ記憶部23、通信インタフェース24及び入出力インタフェース25を備える。コンピュータ2が備える各要素は、バスを介して、互いに接続されている。 Computer 2 at each site B is an example of a computer that executes at least one task using an RPA scenario that describes a work procedure and at least one task that does not use an RPA scenario. Computer 2 includes a control unit 21, a program storage unit 22, a data storage unit 23, a communication interface 24, and an input/output interface 25. Each element of computer 2 is connected to each other via a bus.
 制御部21は、本部Hのサーバ1における制御部11と同様に、プロセッサ、ROM及びRAMを備えることができる。プロセッサは、マルチコア/マルチスレッドのものであって良く、複数の処理を併行して実行することができる。プロセッサは、ROM、又はプログラム記憶部22に記憶されているプログラムをRAMに展開する。プロセッサがRAMに展開されるプログラムを実行することで、制御部21は、後述する各機能部を実現する。 The control unit 21 may be equipped with a processor, ROM, and RAM, similar to the control unit 11 in the server 1 of the headquarters H. The processor may be multi-core/multi-threaded, and can execute multiple processes in parallel. The processor loads the program stored in the ROM or the program storage unit 22 into the RAM. The processor executes the program loaded into the RAM, and the control unit 21 realizes each of the functional units described below.
 プログラム記憶部22は、本部Hのサーバ1におけるプログラム記憶部12と同様に構成され得る。 The program storage unit 22 may be configured in the same manner as the program storage unit 12 in the server 1 of the headquarters H.
 データ記憶部23は、本部Hのサーバ1におけるデータ記憶部13と同様に構成され得る。 The data storage unit 23 may be configured similarly to the data storage unit 13 in the server 1 of the headquarters H.
 通信インタフェース24は、本部Hのサーバ1における通信インタフェース14と同様に構成され得る。通信インタフェース24は、コンピュータ2を他の電子機器と通信可能に接続する種々のインタフェースを含む。 The communication interface 24 may be configured similarly to the communication interface 14 in the server 1 at the headquarters H. The communication interface 24 includes various interfaces that communicatively connect the computer 2 to other electronic devices.
 入出力インタフェース25は、本部Hのサーバ1における入出力インタフェース15と同様に構成され得る。入出力インタフェース25は、コンピュータ2と入力装置201及び出力装置202のそれぞれとの通信を可能にする。 The input/output interface 25 may be configured similarly to the input/output interface 15 in the server 1 of the headquarters H. The input/output interface 25 enables communication between the computer 2 and each of the input device 201 and the output device 202.
 なお、コンピュータ2のハードウェア構成は、上述の構成に限定されるものではない。コンピュータ2は、適宜、上述の構成要素の省略、及び変更並びに新たな構成要素の追加を可能とする。 The hardware configuration of computer 2 is not limited to the above configuration. Computer 2 allows the omission and modification of the above components and the addition of new components as appropriate.
 入力装置201は、キーボード、マウス等のポインティングデバイス、マイクロフォン、等の制御部21に与えるべき情報を入力するための電子機器である。 The input device 201 is an electronic device for inputting information to be provided to the control unit 21, such as a keyboard, a pointing device such as a mouse, a microphone, etc.
 出力装置202は、ディスプレイ、プリンタ、スピーカ、等の制御部21からの情報を出力するための電子機器である。 The output device 202 is an electronic device for outputting information from the control unit 21, such as a display, printer, or speaker.
 図2は、シナリオ提案システムSを構成する本部Hに配置された第1の実施形態に係るシナリオ提案装置としてのサーバ1のソフトウェア構成の一例を示すブロック図である。本部Hのサーバ1は、操作ログ収集部111、ログ分類部112、シナリオ収集部113、一致度算出部114、組み合わせ抽出部115及びシナリオ提案部116を備える。各機能部は、制御部11によるプログラムの実行によって実現される。各機能部は、制御部11又はプロセッサが備えると言うこともできる。各機能部は、制御部11又はプロセッサと読み替え可能である。各機能部は、また、ASIC(Application Specific Integrated Circuit)、DSP(Digital Signal Processor)、FPGA(field-programmable gate array)、GPU(Graphics Processing Unit)、等の集積回路を含む、他の多様な形式で実現されても良い。更に、サーバ1は、操作ログ記憶部131、分類結果記憶部132、シナリオ記憶部133及び提案記憶部134を備える。これら操作ログ記憶部131、分類結果記憶部132、シナリオ記憶部133及び提案記憶部134は、データ記憶部13によって実現される。 2 is a block diagram showing an example of the software configuration of the server 1 as a scenario proposal device according to the first embodiment, which is disposed in the headquarters H constituting the scenario proposal system S. The server 1 in the headquarters H includes an operation log collection unit 111, a log classification unit 112, a scenario collection unit 113, a coincidence calculation unit 114, a combination extraction unit 115, and a scenario proposal unit 116. Each functional unit is realized by the execution of a program by the control unit 11. It can also be said that each functional unit is included in the control unit 11 or the processor. Each functional unit can be read as the control unit 11 or the processor. Each functional unit may also be realized in various other forms, including integrated circuits such as ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (field-programmable gate array), GPU (Graphics Processing Unit), etc. Furthermore, the server 1 includes an operation log memory unit 131, a classification result memory unit 132, a scenario memory unit 133, and a proposal memory unit 134. The operation log storage unit 131, the classification result storage unit 132, the scenario storage unit 133, and the proposal storage unit 134 are realized by the data storage unit 13.
 操作ログ収集部111は、通信インタフェース14によりネットワークNWを介して各拠点Bのコンピュータ2から、当該コンピュータ2対して入力装置201によって操作が行われる毎に送信されてくる操作情報を収集して、拠点B毎の操作ログを生成する。図3は、サーバ1の制御部11が備えるRAMに拠点毎の操作情報を記憶するための拠点毎の操作情報レコード111Rの内容の一例を示す図である。操作ログ収集部111は、拠点Bのコンピュータ2から操作情報を受信すると、その操作情報を、その受信時刻と共に、RAMに設けた当該拠点Bの拠点IDを持つ操作情報レコード111Rに一時保存する。拠点IDは、各拠点Bを一意に識別するための拠点情報の一例である。そして、操作ログ収集部111は、この操作情報レコード111Rに一時保存した操作情報及び受信時刻を、操作ログ記憶部131に記憶されている当該拠点Bの操作ログに追加記憶させる。こうして、操作ログ収集部111は、拠点B毎の操作ログを収集する。操作ログ収集部111は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、コンピュータ2に対する操作の操作ログを収集する操作ログ収集部の一例である。 The operation log collection unit 111 collects operation information transmitted from the computer 2 at each base B via the network NW through the communication interface 14 each time an operation is performed on the computer 2 by the input device 201, and generates an operation log for each base B. FIG. 3 is a diagram showing an example of the contents of the operation information record 111R for each base for storing the operation information for each base in the RAM provided in the control unit 11 of the server 1. When the operation log collection unit 111 receives operation information from the computer 2 at the base B, it temporarily stores the operation information together with the reception time in the operation information record 111R having the base ID of the base B provided in the RAM. The base ID is an example of base information for uniquely identifying each base B. Then, the operation log collection unit 111 adds and stores the operation information and reception time temporarily stored in the operation information record 111R to the operation log of the base B stored in the operation log storage unit 131. In this way, the operation log collection unit 111 collects the operation log for each base B. The operation log collection unit 111 is an example of an operation log collection unit that collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW.
 また、操作ログ収集部111は、受信した操作情報に基づいて、全拠点Bのコンピュータ2での作業が終了したか否か判断し、作業終了と判断した場合には、そのことをログ分類部112に伝達する。例えば、コンピュータ2の電源を落とす操作が行われたことを示す操作情報を受信したとき、操作ログ収集部111は、当該コンピュータ2での作業が終了したと判断することができる。なお、1日の作業が終了してもコンピュータ2の電源を落とさない拠点Bも有り得る。そこで、操作ログ収集部111は、例えば3時間等の規定時間の間、操作情報が受信されないとき、当該コンピュータ2での作業が終了したと判別するような構成としても良い。この規定時間が経過したか否かは、操作情報レコード111Rの受信時刻と現在時刻との比較により、容易に判断することができる。操作ログ収集部111は、作業終了をログ分類部112に伝達したとき、前記拠点Bについての操作情報レコード111Rをクリアする。 The operation log collection unit 111 also determines whether or not work has been completed on all computers 2 at bases B based on the received operation information, and if it determines that work has been completed, transmits this to the log classification unit 112. For example, when operation information is received indicating that an operation to turn off the power of a computer 2 has been performed, the operation log collection unit 111 can determine that work on that computer 2 has been completed. Note that there may be bases B that do not turn off the power of their computers 2 even when work for the day is completed. Therefore, the operation log collection unit 111 may be configured to determine that work on that computer 2 has been completed when no operation information is received for a specified time, such as three hours. Whether or not this specified time has passed can be easily determined by comparing the reception time of the operation information record 111R with the current time. When the operation log collection unit 111 transmits the completion of work to the log classification unit 112, it clears the operation information record 111R for the base B.
 更に、操作ログ収集部111は、各コンピュータ2での作業が終了したと判断した後の再度のコンピュータ2それぞれの作業開始を、受信した操作情報に基づいて判断する。例えば、コンピュータ2の電源を投入する操作が行われたことを示す操作情報を受信したとき、操作ログ収集部111は、当該コンピュータ2での作業が開始したと判断することかできる。作業開始と判断した場合、操作ログ収集部111は、その作業を開始した拠点Bのコンピュータ2に、通信インタフェース14によりネットワークNWを介して、RPAシナリオの導入提案を送信済みであるか否か判断する。図3に示されるように、操作情報レコード111Rは、操作情報及び受信時刻に加えて、送信済みフラグが一時保存されるように構成されている。操作ログ収集部111は、該当する拠点の操作情報レコード111Rにおける送信済みフラグを確認し、当該フラグがクリアされていれば、RPAシナリオの導入提案を送信済みではないと判断することができる。RPAシナリオの導入提案を送信済みではないと判断した場合、操作ログ収集部111は、シナリオ提案部116に、当該拠点Bのコンピュータ2に対して通信インタフェース14によりネットワークNWを介して、RPAシナリオの導入提案を送信するよう指示する。 Furthermore, the operation log collection unit 111 judges whether each computer 2 starts work again after judging that work on each computer 2 has been completed, based on the received operation information. For example, when operation information indicating that an operation to turn on the computer 2 has been performed is received, the operation log collection unit 111 can judge that work on the computer 2 has started. If it judges that work has started, the operation log collection unit 111 judges whether an RPA scenario introduction proposal has been sent to the computer 2 of the site B that started the work via the communication interface 14 through the network NW. As shown in FIG. 3, the operation information record 111R is configured to temporarily store a sent flag in addition to the operation information and the reception time. The operation log collection unit 111 checks the sent flag in the operation information record 111R of the corresponding site, and if the flag is cleared, it can judge that an RPA scenario introduction proposal has not been sent. If it is determined that the RPA scenario introduction proposal has not been sent, the operation log collection unit 111 instructs the scenario proposal unit 116 to send the RPA scenario introduction proposal to the computer 2 at the site B via the network NW via the communication interface 14.
 ログ分類部112は、操作ログ収集部111から全拠点Bのコンピュータ2での作業が終了したことを伝達されたとき、例えば非特許文献1に開示されているような作業分類技術を用いて、操作ログ記憶部131に記憶された各拠点Bの操作ログを作業の単位に分割・分類して、作業単位の操作ログである作業操作ログを生成する。そして、ログ分類部112は、生成した拠点B毎の作業操作ログを、分類結果記憶部132に保存する。ログ分類部112は、操作ログ収集部が収集した操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成する分類部の一例である。 When the log classification unit 112 is notified by the operation log collection unit 111 that work has been completed on the computers 2 of all bases B, it uses a work classification technique, such as that disclosed in Non-Patent Document 1, to divide and classify the operation logs of each base B stored in the operation log storage unit 131 into work units, and generates a work operation log that is an operation log for each work unit. Then, the log classification unit 112 saves the generated work operation log for each base B in the classification result storage unit 132. The log classification unit 112 is an example of a classification unit that divides and classifies the operation logs collected by the operation log collection unit, and generates a work operation log that is an operation log for each work unit.
 シナリオ収集部113は、通信インタフェース14によりネットワークNWを介して各拠点Bのコンピュータ2から、当該コンピュータ2に導入されているRPAシナリオを収集し、収集したRPAシナリオと拠点情報の組をシナリオ記憶部133に記録する。具体的には、シナリオ収集部113は、例えば、通信インタフェース14によりネットワークNWを介して各拠点Bのコンピュータ2に対して、当該コンピュータ2に導入されているRPAシナリオの送信を依頼するシナリオ要求を送信する。そして、シナリオ収集部113は、このシナリオ要求に応答して各拠点Bのコンピュータ2からネットワークNWを介して返信されてくるRPAシナリオを通信インタフェース14により受信する。シナリオ収集部113は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、各拠点Bに導入されているシナリオを収集するシナリオ収集部の一例である。 The scenario collection unit 113 collects the RPA scenarios installed in the computers 2 at each site B from the computers 2 via the network NW through the communication interface 14, and records the collected sets of RPA scenarios and site information in the scenario storage unit 133. Specifically, the scenario collection unit 113, for example, transmits a scenario request to the computers 2 at each site B via the network NW through the communication interface 14, requesting the transmission of the RPA scenarios installed in the computers 2. Then, the scenario collection unit 113 receives the RPA scenarios returned from the computers 2 at each site B via the network NW in response to this scenario request, through the communication interface 14. The scenario collection unit 113 is an example of a scenario collection unit that collects scenarios installed in each site B from the computers 2 at multiple sites B via the network NW.
 一致度算出部114、組み合わせ抽出部115及びシナリオ提案部116は、分類部が生成した作業操作ログの内、シナリオ収集部が収集したシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点Bのコンピュータ2へ、ネットワークNWを介して、シナリオの導入提案を送信する提案部の一例である。 The matching calculation unit 114, the combination extraction unit 115, and the scenario proposal unit 116 are an example of a proposal unit that transmits a scenario introduction proposal via the network NW to the computer 2 at the base B that performs work for a work operation log generated by the classification unit that has a matching degree of a certain value or more with the scenario collected by the scenario collection unit.
 即ち、一致度算出部114は、分類結果記憶部132に記憶されている各拠点Bにおける作業毎の作業操作ログとシナリオ記憶部133に記憶されているRPAシナリオとの一致度を、全ての組み合わせについて算出する。そして、一致度算出部114は、算出した各組み合わせの一致度を組み合わせ抽出部115に伝達する。一致度算出部114は、分類部が生成した作業操作ログとシナリオ収集部が収集したシナリオとの一致度を全ての組み合わせについて算出する一致度算出部の一例である。 In other words, the coincidence calculation unit 114 calculates the degree of coincidence between the work operation logs for each task at each base B stored in the classification result storage unit 132 and the RPA scenarios stored in the scenario storage unit 133 for all combinations. Then, the coincidence calculation unit 114 transmits the calculated degree of coincidence for each combination to the combination extraction unit 115. The coincidence calculation unit 114 is an example of a coincidence calculation unit that calculates the degree of coincidence between the work operation logs generated by the classification unit and the scenarios collected by the scenario collection unit for all combinations.
 組み合わせ抽出部115は、一致度算出部114から伝達される作業操作ログとRPAシナリオとの組み合わせの一致度の内、その一致度が一定値以上の組み合わせを抽出する。そして、組み合わせ抽出部115は、その抽出した組み合わせにおける作業操作ログの作業とRPAシナリオの組を、提案記憶部134に記録する。この場合、組み合わせ抽出部115は、シナリオ記憶部133に記憶されているRPAシナリオと拠点情報の組に基づいて、RPAシナリオが導入済みの作業であると判断したならば、当該作業とRPAシナリオの組は、提案記憶部134への記録から除外する。なお、提案記憶部134には、RPAシナリオそのものを記録するのではなく、シナリオ記憶部133に記憶されたRPAシナリオを特定するためのRPAシナリオ情報を記録するようにしても良い。組み合わせ抽出部115は、一致度算出部が算出した一致度が一定値以上の組み合わせを抽出する組み合わせ抽出部の一例である。 The combination extraction unit 115 extracts combinations whose degree of coincidence is equal to or greater than a certain value among the degrees of coincidence between the combinations of the work operation log and the RPA scenario transmitted from the coincidence calculation unit 114. The combination extraction unit 115 then records the pair of the work of the work operation log and the RPA scenario in the extracted combination in the proposal storage unit 134. In this case, if the combination extraction unit 115 determines that the RPA scenario is an introduced work based on the pair of the RPA scenario and the base information stored in the scenario storage unit 133, it excludes the pair of the work and the RPA scenario from being recorded in the proposal storage unit 134. Note that the proposal storage unit 134 may record RPA scenario information for identifying the RPA scenario stored in the scenario storage unit 133, rather than recording the RPA scenario itself. The combination extraction unit 115 is an example of a combination extraction unit that extracts combinations whose degree of coincidence calculated by the coincidence calculation unit is equal to or greater than a certain value.
 シナリオ提案部116は、操作ログ収集部111から作業を開始した拠点Bのコンピュータ2に対してRPAシナリオの導入提案を送信するよう指示されたとき、提案記憶部134に記憶された作業とRPAシナリオの組に基づいて、当該作業を実行するのに適したRPAシナリオの導入を提案する導入提案を、通信インタフェース14によりネットワークNWを介して送信する。そして、シナリオ提案部116は、その導入提案を送信した拠点Bに対応する操作情報レコード111Rにおける送信済みフラグをセット、即ち「1」を記録する。その後、シナリオ提案部116は、この導入提案を受けた拠点Bのコンピュータ2からネットワークNWを介して送信されてくる、当該導入提案を受け入れる提案受諾を通信インタフェース14により受信したならば、シナリオ記憶部133に記憶されているそのRPAシナリオを、通信インタフェース14によりネットワークNWを介して当該拠点Bのコンピュータ2へ送信する。 When the scenario proposal unit 116 is instructed by the operation log collection unit 111 to send an introduction proposal for an RPA scenario to the computer 2 at site B that has started work, the scenario proposal unit 116 sends an introduction proposal proposing the introduction of an RPA scenario suitable for executing the work based on the pair of work and RPA scenario stored in the proposal storage unit 134 via the communication interface 14 and the network NW. Then, the scenario proposal unit 116 sets the transmitted flag in the operation information record 111R corresponding to the site B that sent the introduction proposal, i.e. records "1". After that, when the scenario proposal unit 116 receives a proposal acceptance that accepts the introduction proposal, which is sent via the network NW from the computer 2 at site B that received the introduction proposal, via the communication interface 14, it sends the RPA scenario stored in the scenario storage unit 133 to the computer 2 at site B via the communication interface 14 and the network NW.
 シナリオ提案部116は、組み合わせ抽出部が抽出した組み合わせにおける作業を実行する拠点Bのコンピュータ2へ、抽出した組み合わせにおけるシナリオの導入を提案する導入提案を、ネットワークNWを介して送信するシナリオ提案部の一例である。また、シナリオ提案部116は、シナリオの導入提案を受信した拠点Bのコンピュータ2からネットワークNWを介して提案受諾を受信したとき、当該コンピュータ2へネットワークNWを介して、導入提案を行ったシナリオを送信する提案部の一例である。 The scenario proposal unit 116 is an example of a scenario proposal unit that transmits an introduction proposal proposing the introduction of a scenario in the extracted combination via the network NW to the computer 2 at site B that performs the work in the combination extracted by the combination extraction unit. The scenario proposal unit 116 is also an example of a proposal unit that transmits the proposed introduction scenario to the computer 2 via the network NW when it receives an acceptance of the proposal via the network NW from the computer 2 at site B that received the scenario introduction proposal.
 図4は、第1の実施形態に係るシナリオ提案システムSを構成する拠点Bに配置されたコンピュータ2のソフトウェア構成の一例を示すブロック図である。 FIG. 4 is a block diagram showing an example of the software configuration of a computer 2 located at a base B that constitutes a scenario proposal system S according to the first embodiment.
 拠点Bのコンピュータ2は、作業実行部211、操作情報送信部212、シナリオ出力部213及び提案取得部214を備える。各機能部は、制御部21によるプログラムの実行によって実現される。各機能部は、制御部21又はプロセッサが備えると言うこともできる。各機能部は、制御部21又はプロセッサと読み替え可能である。各機能部は、また、ASIC、DSP、FPGA、GPU、等の集積回路を含む、他の多様な形式で実現されても良い。更に、コンピュータ2は、シナリオ記憶部231を備える。シナリオ記憶部231は、データ記憶部23によって実現される。 The computer 2 at site B comprises an operation execution unit 211, an operation information transmission unit 212, a scenario output unit 213, and a proposal acquisition unit 214. Each functional unit is realized by the execution of a program by the control unit 21. It can also be said that each functional unit is comprised by the control unit 21 or a processor. Each functional unit can be read as the control unit 21 or a processor. Each functional unit may also be realized in a variety of other forms, including integrated circuits such as ASIC, DSP, FPGA, GPU, etc. Furthermore, the computer 2 comprises a scenario storage unit 231. The scenario storage unit 231 is realized by the data storage unit 23.
 作業実行部211は、プログラム記憶部22に記憶されている各種作業のための作業プログラムに従って、各種作業を実行する。このとき、作業実行部211は、シナリオ記憶部231に当該作業についての作業手順を記述したRPAシナリオが記憶されていれば、それを利用して作業を実行することができる。シナリオ記憶部231に該当するRPAシナリオが記憶されていない場合には、当然、RPAシナリオを利用しないで、作業プログラムに従って作業を実行する。このRPAシナリオを利用した又は利用しない作業の実行において、作業実行部211は、入力装置201による操作を受け、また、作業内容を出力装置202により出力する。作業実行部211は、作業の実行中に受けた操作を示す操作情報を操作情報送信部212に伝達する。 The work execution unit 211 executes various tasks according to the work programs for the various tasks stored in the program storage unit 22. At this time, if an RPA scenario describing the work procedure for the task is stored in the scenario storage unit 231, the work execution unit 211 can execute the task using the RPA scenario. If the corresponding RPA scenario is not stored in the scenario storage unit 231, the work execution unit 211 naturally executes the task according to the work program without using the RPA scenario. In executing tasks using or not using this RPA scenario, the work execution unit 211 receives operations from the input device 201 and outputs the work content from the output device 202. The work execution unit 211 transmits operation information indicating the operation received during the execution of the task to the operation information transmission unit 212.
 操作情報送信部212は、作業実行部211から伝達された操作情報を、通信インタフェース24によりネットワークNWを介して、本部Hのサーバ1へ送信する。 The operation information transmission unit 212 transmits the operation information transmitted from the work execution unit 211 to the server 1 in the headquarters H via the network NW via the communication interface 24.
 シナリオ出力部213は、通信インタフェース24によりネットワークNWを介して本部Hのサーバ1からシナリオ要求を受信したとき、シナリオ記憶部231に記憶しているRPAシナリオを読み出す。そして、シナリオ出力部213は、その読み出したRPAシナリオを、当該拠点Bに導入されているRPAシナリオとして、通信インタフェース24によりネットワークNWを介して本部Hのサーバ1へ送信する。 When the scenario output unit 213 receives a scenario request from server 1 of headquarters H via network NW through communication interface 24, it reads out the RPA scenario stored in the scenario memory unit 231. Then, the scenario output unit 213 transmits the read-out RPA scenario to server 1 of headquarters H via network NW through communication interface 24 as the RPA scenario installed at base B.
 提案取得部214は、通信インタフェース24によりネットワークNWを介して本部Hのサーバ1から、当該拠点Bで実行する作業について、その実行に適したRPAシナリオの導入を提案する導入提案を受信したとき、その導入提案を出力装置202により出力する。そして、提案取得部214は、入力装置201により当該導入提案を受諾する操作を受けると、通信インタフェース24によりネットワークNWを介して本部Hのサーバ1に提案受諾を送信する。この提案受諾を受信した本部Hのサーバ1からネットワークNWを介してRPAシナリオが送信されてくると、提案取得部214は、通信インタフェース24によりそれを受信して、シナリオ記憶部231に登録する。 When the proposal acquisition unit 214 receives an introduction proposal from the server 1 of the headquarters H via the network NW through the communication interface 24, which proposes the introduction of an RPA scenario suitable for the work to be performed at the base B, the proposal acquisition unit 214 outputs the introduction proposal through the output device 202. Then, when the proposal acquisition unit 214 receives an operation to accept the introduction proposal through the input device 201, it transmits the proposal acceptance to the server 1 of the headquarters H via the network NW through the communication interface 24. When the server 1 of the headquarters H that has received the proposal acceptance transmits an RPA scenario via the network NW, the proposal acquisition unit 214 receives it through the communication interface 24 and registers it in the scenario storage unit 231.
 (動作例)
 図5は、第1の実施形態に係るシナリオ提案装置としてのサーバ1の処理手順と処理内容を示すフローチャートである。本第1の実施形態においては、サーバ1は、各拠点Bでの操作の都度、操作ログを収集し、例えば1日の終わり等の前記拠点Bでの作業終了時に導入提案を作成し、翌日の各拠点Bの作業開始時に導入提案を提示するよう動作する。
(Example of operation)
5 is a flowchart showing the processing procedure and processing contents of the server 1 as a scenario proposal device according to the first embodiment. In this first embodiment, the server 1 operates to collect an operation log for each operation at each base B, create an introduction proposal when work at the base B ends, for example, at the end of a day, and present the introduction proposal when work at each base B starts the next day.
 サーバ1の制御部11は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、当該コンピュータ2に対する操作の操作ログを収集する操作ログ収集・RPAシナリオ提案処理を実行する(ステップS11)。この操作ログ収集・RPAシナリオ提案処理の典型例については後述する。 The control unit 11 of the server 1 executes an operation log collection/RPA scenario proposal process that collects operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW (step S11). A typical example of this operation log collection/RPA scenario proposal process will be described later.
 次に、サーバ1の制御部11は、収集した操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成する操作ログ分類処理を実行する(ステップS12)。この操作ログ分類処理の典型例については後述する。 Next, the control unit 11 of the server 1 executes an operation log classification process that divides and classifies the collected operation logs to generate a work operation log, which is an operation log for each task (step S12). A typical example of this operation log classification process will be described later.
 次に、サーバ1の制御部11は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、各拠点Bに導入されているRPAシナリオを収集するPAシナリオ収集処理を実行する(ステップS13)。このRPAシナリオ収集処理の典型例については後述する。 Next, the control unit 11 of the server 1 executes a PA scenario collection process to collect RPA scenarios introduced at each of the multiple bases B from the computers 2 at the bases B via the network NW (step S13). A typical example of this RPA scenario collection process will be described later.
 次に、サーバ1の制御部11は、生成した作業操作ログの内、収集したシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点Bのコンピュータへ、ネットワークNWを介して送信する、シナリオの導入提案を決定する提案RPAシナリオ決定処理を実行する(ステップS14)。この提案RPAシナリオ決定処理の典型例については後述する。 Then, the control unit 11 of the server 1 executes a proposed RPA scenario determination process to determine a proposal for introducing a scenario to be sent via the network NW to the computer at base B that performs the work of the work operation logs that have a degree of match with the collected scenario that is equal to or greater than a certain value among the generated work operation logs (step S14). A typical example of this proposed RPA scenario determination process will be described later.
 そして、サーバ1の制御部11は、上記ステップS11の操作ログ収集・RPAシナリオ提案処理に移行し、この操作ログ収集・RPAシナリオ提案処理において、決定したシナリオの導入提案をネットワークNWを介して対応する拠点Bのコンピュータ2に送信する。 Then, the control unit 11 of the server 1 proceeds to the operation log collection/RPA scenario proposal process of step S11 above, and in this operation log collection/RPA scenario proposal process, sends the introduction proposal for the determined scenario to the corresponding computer 2 at site B via the network NW.
 図6は、サーバ1の操作ログ収集・RPAシナリオ提案処理の処理手順と処理内容を示すフローチャートである。図6は、ステップS11の処理の典型例を示す。ここでは、サーバ1の制御部11は、操作ログ収集部111及びシナリオ提案部116として動作する。先ず、操作ログ収集部111に係わる処理から説明していく。 FIG. 6 is a flowchart showing the processing procedure and processing contents of the operation log collection and RPA scenario proposal processing of the server 1. FIG. 6 shows a typical example of the processing of step S11. Here, the control unit 11 of the server 1 operates as an operation log collection unit 111 and a scenario proposal unit 116. First, the processing related to the operation log collection unit 111 will be explained.
 制御部11は、通信インタフェース14により、何れかの拠点Bのコンピュータ2からの操作情報を、ネットワークNWを介して受信したか否か判断する(ステップS111)。前述したように、各拠点Bのコンピュータ2においては、操作情報送信部212により、電源が投入された際の電源投入の操作情報をはじめとして入力装置201から受けた操作を示す操作情報を、通信インタフェース24によりネットワークNWを介して、本部Hのサーバ1へ送信するようになっている。 The control unit 11 determines whether operation information has been received from the computer 2 at any of the bases B via the network NW through the communication interface 14 (step S111). As described above, in the computer 2 at each base B, the operation information transmitting unit 212 transmits operation information indicating operations received from the input device 201, including power-on operation information when the power is turned on, to the server 1 at the headquarters H via the network NW through the communication interface 24.
 ここで、操作情報を受信していないと判断した場合、制御部11は、全拠点Bのコンピュータ2での作業が終了しているか否か判断する(ステップS112)。前述したように、拠点Bのコンピュータ2での作業の終了とは、拠点Bのコンピュータ2から電源を落とす操作が行われたことを示す操作情報を受信したときと、拠点Bのコンピュータ2から規定時間の間、操作情報が受信されないときと、を含むことができる。制御部11は、全拠点Bのコンピュータ2での作業が未だ終了していないと判断した場合、上記ステップS111の処理へ移行する。 If it is determined that no operation information has been received, the control unit 11 determines whether or not work has been completed on all of the computers 2 at site B (step S112). As described above, the end of work on the computers 2 at site B can include a time when operation information indicating that a power-off operation has been performed is received from the computers 2 at site B, and a time when no operation information is received from the computers 2 at site B for a specified period of time. If the control unit 11 determines that work has not yet been completed on all of the computers 2 at site B, it proceeds to the processing of step S111 above.
 上記ステップS111において、何れかの拠点Bのコンピュータ2からの操作情報を受信したと判断した場合、制御部11は、受信した操作情報を、その操作情報を送信した送信元の拠点Bの操作情報レコード111Rに一時保存する(ステップS113)。具体的には、制御部11は、受信した操作情報とその受信時刻とを操作情報レコード111Rに上書きする。従って、ここでは、操作情報レコード111Rの送信済みフラグは、その値が維持される。 If it is determined in step S111 above that operation information has been received from the computer 2 of one of the locations B, the control unit 11 temporarily stores the received operation information in the operation information record 111R of the location B that sent the operation information (step S113). Specifically, the control unit 11 overwrites the received operation information and its reception time in the operation information record 111R. Therefore, here, the transmitted flag of the operation information record 111R maintains its value.
 その後、制御部11は、その対応する拠点Bの操作情報レコード111Rの送信済みフラグを確認して、操作情報を送信した送信元拠点へ、RPAシナリオの導入提案を送信済みであるか否か判断する(ステップS114)。 Then, the control unit 11 checks the transmission flag of the operation information record 111R of the corresponding base B and determines whether or not the proposal to introduce the RPA scenario has been sent to the source base that sent the operation information (step S114).
 ここで、既に送信元拠点へRPAシナリオの導入提案を送信済みであると判断した場合、制御部11は、受信した操作情報が導入提案を受諾する操作が行われたことを示すものであるか否か判断する(ステップS115)。 If it is determined that the proposal to introduce the RPA scenario has already been sent to the source location, the control unit 11 determines whether the received operation information indicates that an operation to accept the proposal to introduce the RPA scenario has been performed (step S115).
 受信した操作情報が導入提案を受諾する操作ではないと判断した場合、制御部11は、操作ログ記憶部131に記憶されている拠点毎の操作ログの内、当該拠点Bのコンピュータ2の操作ログに、操作情報レコード111Rに一時保存されている操作情報及び受信時刻を追加記憶させる(ステップS116)。その後、制御部11は、上記ステップS112の処理へ移行する。 If the control unit 11 determines that the received operation information is not an operation for accepting the introduction proposal, the control unit 11 additionally stores the operation information temporarily stored in the operation information record 111R and the reception time in the operation log of the computer 2 of the relevant site B among the operation logs for each site stored in the operation log storage unit 131 (step S116). After that, the control unit 11 proceeds to the process of step S112 above.
 そして、上記ステップS112において、全拠点Bのコンピュータ2での作業が終了していると判断した場合、制御部11は、全拠点Bについての操作情報レコード111Rに一時保存されている操作情報及び送信済みフラグをクリアする(ステップS117)。即ち、制御部11は、該当する操作情報レコード111Rの送信済みフラグを「0」にリセットし、操作情報及び受信時刻の値を削除する。 If it is determined in step S112 that the work has been completed on the computers 2 of all bases B, the control unit 11 clears the operation information and the transmission flags temporarily stored in the operation information records 111R for all bases B (step S117). That is, the control unit 11 resets the transmission flags of the corresponding operation information records 111R to "0" and deletes the values of the operation information and the reception time.
 その後、制御部11は、上記ステップS12の操作ログ分類処理へ移行する。この操作ログ分類処理への移行は、操作ログ収集部111が全拠点Bのコンピュータ2での作業が終了したことをログ分類部112に伝達することの一例である。 Then, the control unit 11 transitions to the operation log classification process of step S12. This transition to the operation log classification process is an example of the operation log collection unit 111 notifying the log classification unit 112 that work on the computers 2 at all bases B has been completed.
 図7は、第1の実施形態におけるサーバ1の操作ログ分類処理の処理手順と処理内容を示すフローチャートである。図7は、ステップS12の処理の典型例を示す。ここでは、サーバ1の制御部11は、ログ分類部112として動作する。 FIG. 7 is a flowchart showing the procedure and content of the operation log classification process of the server 1 in the first embodiment. FIG. 7 shows a typical example of the process of step S12. Here, the control unit 11 of the server 1 operates as the log classification unit 112.
 制御部11は、操作ログ記憶部131を参照して、未分類の操作ログが有るか否か判断する(ステップS121)。 The control unit 11 refers to the operation log storage unit 131 and determines whether there are any unclassified operation logs (step S121).
 未分類の操作ログが有ると判断した場合、制御部11は、操作ログ記憶部131から未分類の操作ログを一つ読み出す(ステップS122)。 If it is determined that there is an unclassified operation log, the control unit 11 reads one unclassified operation log from the operation log storage unit 131 (step S122).
 次に、制御部11は、この読み出した操作ログを、作業の単位に分割・分類して、作業単位の操作ログである作業操作ログを生成する(ステップS123)。 The control unit 11 then divides and classifies the read operation log into task units to generate a task operation log, which is an operation log for each task unit (step S123).
 そして、制御部11は、生成した作業操作ログを、分類結果記憶部132に保存する(ステップS124)。その後、制御部11は、上記ステップS121の処理に移行する。 Then, the control unit 11 stores the generated work operation log in the classification result storage unit 132 (step S124). After that, the control unit 11 proceeds to the process of step S121.
 そして、上記ステップS121において、未分類の操作ログが無い、つまり操作ログ記憶部131に記憶されている各拠点Bの操作ログを全て分類したと判断すると、制御部11は、上記ステップS13のRPAシナリオ収集処理へ移行する。 If it is determined in step S121 that there are no unclassified operation logs, i.e., that all operation logs for each base B stored in the operation log storage unit 131 have been classified, the control unit 11 proceeds to the RPA scenario collection process in step S13.
 図8は、第1の実施形態におけるサーバ1のRPAシナリオ収集処理の処理手順と処理内容を示すフローチャートである。図8は、ステップS13の処理の典型例を示す。ここでは、サーバ1の制御部11は、シナリオ収集部113として動作する。 FIG. 8 is a flowchart showing the processing procedure and processing contents of the RPA scenario collection process of the server 1 in the first embodiment. FIG. 8 shows a typical example of the processing of step S13. Here, the control unit 11 of the server 1 operates as a scenario collection unit 113.
 先ず、制御部11は、シナリオ記憶部133に記憶されている収集済みシナリオ、つまり前回の処理動作時に記録した、RPAシナリオと拠点情報との組をクリアする(ステップS131)。 First, the control unit 11 clears the collected scenarios stored in the scenario storage unit 133, that is, the pairs of RPA scenarios and base information recorded during the previous processing operation (step S131).
 その後、制御部11は、シナリオ記憶部133を参照して、RPAシナリオを未収集の拠点Bが有るか否か判断する(ステップS132)。 Then, the control unit 11 refers to the scenario storage unit 133 to determine whether there is a location B for which an RPA scenario has not yet been collected (step S132).
 RPAシナリオ未収集の拠点Bが有ると判断した場合、制御部11は、未分類の拠点Bの内の一つに対して、通信インタフェース14によりネットワークNWを介して、当該拠点Bのコンピュータ2に導入されているRPAシナリオの送信を依頼するシナリオ要求を送信する(ステップS133)。 If it is determined that there is a location B for which an RPA scenario has not been collected, the control unit 11 sends a scenario request to one of the unclassified locations B via the communication interface 14 over the network NW, requesting the transmission of the RPA scenario installed in the computer 2 of that location B (step S133).
 そして、制御部11は、このシナリオ要求に応答して当該拠点Bのコンピュータ2からネットワークNWを介して返信されてくるRPAシナリオを通信インタフェース14により受信したか否か判断する(ステップS134)。RPAシナリオを受信していないと判断した場合、制御部11は、再度、このステップS134の処理を繰り返す。こうして、制御部11は、RPAシナリオを受信するのを待つ。 Then, the control unit 11 determines whether or not an RPA scenario returned from the computer 2 at site B via the network NW in response to this scenario request has been received by the communication interface 14 (step S134). If it is determined that an RPA scenario has not been received, the control unit 11 repeats the process of step S134 again. In this way, the control unit 11 waits to receive an RPA scenario.
 拠点Bのコンピュータ2では、シナリオ出力部213がネットワークNWを介して送られてきたシナリオ要求を受信すると、シナリオ出力部213は、シナリオ記憶部231に記憶されている、導入済みのRPAシナリオを読み出して、ネットワークNWを介してサーバ1へ送信する。なお、導入済みのRPAシナリオが無い場合には、シナリオ出力部213は、シナリオ無しを返信することができる。 In the computer 2 at site B, when the scenario output unit 213 receives a scenario request sent via the network NW, the scenario output unit 213 reads out the implemented RPA scenario stored in the scenario storage unit 231 and transmits it to the server 1 via the network NW. Note that if there is no implemented RPA scenario, the scenario output unit 213 can return a message that there is no scenario.
 こうして拠点Bのコンピュータ2から送信されてくるRPAシナリオを受信したと判断した場合、制御部11は、その受信したRPAシナリオと、その送信元を示す拠点情報との組を、シナリオ記憶部133に記録する(ステップS135)。拠点情報は、前述したように、拠点Bのそれぞれに一意に割り当てられた拠点IDであることができる。なお、シナリオ無しを受信した場合には、制御部11は、シナリオ記憶部133に、送信元の拠点情報とRPAシナリオ無し情報との組を記録することができる。その後、制御部11は、上記ステップS132の処理に移行する。 When it is determined that an RPA scenario transmitted from the computer 2 at base B has been received, the control unit 11 records a pair of the received RPA scenario and base information indicating its sender in the scenario storage unit 133 (step S135). The base information can be a base ID uniquely assigned to each base B, as described above. Note that when no scenario is received, the control unit 11 can record a pair of the sender's base information and no RPA scenario information in the scenario storage unit 133. The control unit 11 then proceeds to the processing of step S132 above.
 そして、上記ステップS132において、RPAシナリオ未収集の拠点Bが無いと判断すると、制御部11は、上記ステップS14の提案RPAシナリオ決定処理へ移行する。 If it is determined in step S132 that there is no location B for which RPA scenarios have not been collected, the control unit 11 proceeds to the proposed RPA scenario determination process in step S14.
 図9は、第1の実施形態におけるサーバ1の提案RPAシナリオ決定処理の処理手順と処理内容を示すフローチャートである。図9は、ステップS14の処理の典型例を示す。ここでは、サーバ1の制御部11は、一致度算出部114及び組み合わせ抽出部115として動作する。 FIG. 9 is a flowchart showing the procedure and content of the proposed RPA scenario determination process of the server 1 in the first embodiment. FIG. 9 shows a typical example of the process of step S14. Here, the control unit 11 of the server 1 operates as a coincidence calculation unit 114 and a combination extraction unit 115.
 制御部11は、分類結果記憶部132を参照して、RPAシナリオとの一致度を比較していない未比較の作業操作ログが有るか否か判断する(ステップS141)。 The control unit 11 refers to the classification result storage unit 132 and determines whether there are any work operation logs that have not been compared for their degree of consistency with the RPA scenario (step S141).
 未比較の作業操作ログが有ると判断した場合、制御部11は、分類結果記憶部132から未比較の作業操作ログを一つ読み出す(ステップS142)。 If it is determined that there is an uncompared work operation log, the control unit 11 reads one uncompared work operation log from the classification result storage unit 132 (step S142).
 ここで、制御部11は、シナリオ記憶部133を参照して、読み出した作業操作ログとの一致度を比較していない未比較のRPAシナリオが有るか否か判断する(ステップS143)。 Here, the control unit 11 refers to the scenario storage unit 133 to determine whether there is an RPA scenario that has not been compared for the degree of consistency with the read work operation log (step S143).
 未比較のRPAシナリオが有ると判断した場合、制御部11は、シナリオ記憶部133から未比較のRPAシナリオを一つ読み出す(ステップS144)。 If it is determined that there is an uncompared RPA scenario, the control unit 11 reads out one uncompared RPA scenario from the scenario storage unit 133 (step S144).
 そして、制御部11は、それら読み出した作業操作ログと読み出したRPAシナリオとを比較する(ステップS145)。この比較の手法は、特に限定しない。一例としては、コサイン類似度を利用して比較することができる。 Then, the control unit 11 compares the read work operation logs with the read RPA scenario (step S145). The method of this comparison is not particularly limited. As an example, the comparison can be made using cosine similarity.
 例えば、コサイン類似度を用いて作業操作ログとRPAシナリオの一致度を算出する場合、制御部11は、操作ログ中の操作(各行)とRPAシナリオ中の各操作(ノード)の中で、同一の操作を判別し、その後、各操作のベクトルを作成して、類似度を算出する。 For example, when calculating the degree of match between a work operation log and an RPA scenario using cosine similarity, the control unit 11 identifies identical operations among the operations (each row) in the operation log and each operation (node) in the RPA scenario, then creates a vector for each operation and calculates the similarity.
 ここで、操作ログとシナリオ間での同一の操作を判別する方法として、例えば、シナリオ中の操作箇所とログ中の操作箇所が同一、且つ、入力文字列等が同じものを、同一の操作として見做す方法がある。図10は、操作ログLOG中の操作とRPAシナリオ中の操作との対応の一例を示す図である。制御部11は、例えば、操作ログLOG中の「win_title」の項目とRPAシナリオのノード詳細画面NDS中の操作対象のウィンドウタイトル等から同一性を判定することができる(双方向矢印AR1)。図11は、操作ログとして取得できる項目の例を示す図である。また、制御部11は、例えば、操作対象のGUI部品の属性度名から同一性を判定することができる(双方向矢印AR2)。 Here, one method of determining whether an operation is the same between an operation log and a scenario is to regard operations as the same if the operation location in the scenario and the operation location in the log are the same and the input strings, etc. are the same. Figure 10 is a diagram showing an example of the correspondence between operations in the operation log LOG and operations in an RPA scenario. The control unit 11 can determine identity, for example, from the "win_title" item in the operation log LOG and the window title of the operation target in the node details screen NDS of the RPA scenario (bidirectional arrow AR1). Figure 11 is a diagram showing examples of items that can be acquired as an operation log. The control unit 11 can also determine identity, for example, from the attribute name of the GUI part of the operation target (bidirectional arrow AR2).
 こうして同一の操作が判定でされたならば、制御部11は、例えば以下のようにして、各操作のベクトルを作成して、類似度を算出する。
 (1) 制御部11は、Bag of Word(BoW)を用いて作業操作ログ中の各操作(行)のベクトル及びRPAシナリオ中の各操作(ノード)のベクトルを作成する。図12は、作成された、一つの作業単位の作業操作ログ又はRPAシナリオに含まれる各操作のベクトルの一例を示す図である。制御部11は、このような作成したベクトルを、自身が備えるRAMに記憶しておくことができる。
 (2) 制御部11は、コサイン類似度を計算する。作業操作ログtnのベクトルとRPAシナリオsmのベクトルのコサイン類似度は以下の式で表される。
If it is determined that the same operation has been performed in this manner, the control unit 11 creates a vector of each operation and calculates the similarity, for example, in the following manner.
(1) The control unit 11 uses a Bag of Word (BoW) to create vectors of each operation (row) in the work operation log and vectors of each operation (node) in the RPA scenario. Fig. 12 is a diagram showing an example of the created vectors of each operation included in the work operation log or RPA scenario of one work unit. The control unit 11 can store such created vectors in its own RAM.
(2) The control unit 11 calculates the cosine similarity. The cosine similarity between the vector of the work operation log t n and the vector of the RPA scenario s m is expressed by the following formula.
Figure JPOXMLDOC01-appb-M000001
Figure JPOXMLDOC01-appb-M000001
 制御部11は、作業操作ログとRPAシナリオの一致度、例えばコサイン類似度、が予め定めた一定値以上であるか否か判断する(ステップS146)。ここで、一致度が一定値以上でないと判断した場合、制御部11は、上記ステップS143の処理に移行する。こうして、上記ステップS142で読み出した作業操作ログを、シナリオ記憶部133に記憶されている各RPAシナリオと比較していく。そして、全てのRPAシナリオとの比較が行われたならば、制御部11は、上記ステップS143において未比較のRPAシナリオが無いと判断し、上記ステップS141の処理に移行する。これにより、制御部11は、分類結果記憶部132に記憶されている次の未比較の作業操作ログに対して、RPAシナリオとの比較処理へと進むことができる。 The control unit 11 determines whether the degree of match between the work operation log and the RPA scenario, for example, cosine similarity, is equal to or greater than a predetermined value (step S146). If the control unit 11 determines that the degree of match is not equal to or greater than the predetermined value, it proceeds to the processing of step S143. In this way, the work operation log read out in step S142 is compared with each RPA scenario stored in the scenario storage unit 133. Then, when comparison with all RPA scenarios has been performed, the control unit 11 determines in step S143 that there is no uncompared RPA scenario, and proceeds to the processing of step S141. This allows the control unit 11 to proceed to the comparison processing with the RPA scenario for the next uncompared work operation log stored in the classification result storage unit 132.
 上記ステップS146において、作業操作ログとRPAシナリオの一致度が一定値以上であると判断した場合、制御部11は、その作業操作ログの拠点Bにおける作業は、そのRPAシナリオが導入済みの作業であるか否か判断する(ステップS147)。前述したように、シナリオ記憶部133は、RPAシナリオと拠点情報の組を記憶している。従って、制御部11は、分類結果記憶部132を参照して、その作業操作ログがどの拠点Bのものであるのか確認し、シナリオ記憶部133より、当該拠点Bに、その一致度が一定値以上であると判断されたRPAシナリオが導入済みであるかどうかを判断することができる。ここで、RPAシナリオ導入済み作業であると判断した場合、制御部11は、上記ステップS143の処理に移行する。 If it is determined in step S146 above that the degree of match between the work operation log and the RPA scenario is equal to or greater than a certain value, the control unit 11 determines whether the work at base B in the work operation log is a work for which the RPA scenario has already been introduced (step S147). As described above, the scenario storage unit 133 stores a pair of an RPA scenario and base information. Therefore, the control unit 11 can refer to the classification result storage unit 132 to confirm which base B the work operation log belongs to, and determine from the scenario storage unit 133 whether the RPA scenario whose degree of match is determined to be equal to or greater than a certain value has already been introduced at that base B. Here, if it is determined that the RPA scenario is an introduced work, the control unit 11 proceeds to the processing of step S143 above.
 これに対して、RPAシナリオ導入済み作業ではないと判断した場合、制御部11は、その作業操作ログの作業とRPAシナリオの組を、その拠点Bに対する提案として、提案記憶部134に記録する(ステップS148)。このようにして、制御部11は、一致度が一定値以上の作業操作ログとRPAシナリオの組み合わせを抽出することができる。その後、制御部11は、上記ステップS143の処理に移行する。 In contrast, if it is determined that the work is not one for which an RPA scenario has already been introduced, the control unit 11 records the pair of the work in the work operation log and the RPA scenario as a proposal for base B in the proposal storage unit 134 (step S148). In this way, the control unit 11 can extract combinations of work operation logs and RPA scenarios whose degree of matching is equal to or greater than a certain value. Thereafter, the control unit 11 proceeds to the processing of step S143 described above.
 以上のようにして、制御部11は、分類結果記憶部132に記憶された各分類された作業の作業操作ログについて、導入を提案できるRPAシナリオを判別していくことができる。そして、上記ステップS141において、未比較の作業操作ログが無いと判断すると、制御部11は、上記ステップS11の操作ログ収集・RPAシナリオ提案処理へ移行する。 In this way, the control unit 11 can determine the RPA scenarios that can be proposed for introduction for the work operation logs of each classified work stored in the classification result storage unit 132. Then, in the above step S141, if it is determined that there are no uncompared work operation logs, the control unit 11 proceeds to the operation log collection/RPA scenario proposal process of the above step S11.
 図6の説明に戻る。ここでは、シナリオ提案部116に係わる処理の説明となる。提案RPAシナリオ決定処理からこの操作ログ収集・RPAシナリオ提案処理へ移行してきたときとは、一旦、全拠点Bのコンピュータ2での作業が終了した後であり、各拠点Bについての操作情報レコード111Rの送信済みフラグは、「0」にリセットされている。そのため、上記ステップS111で受信したと判断される操作情報は、何れかの拠点Bのコンピュータ2にける電源投入の操作を示す操作情報の場合が有る。この場合、その送信元拠点Bの操作情報レコード111Rの送信済みフラグが「0」にリセットされていることで、制御部11は、上記ステップS114において、当該送信元拠点Bへ、RPAシナリオの導入提案を送信済みではないと判断することとなる。 Returning to the explanation of FIG. 6, here is an explanation of the processing related to the scenario proposal unit 116. The transition from the proposed RPA scenario determination processing to this operation log collection/RPA scenario proposal processing occurs once work has been completed on the computers 2 of all bases B, and the transmission flag of the operation information record 111R for each base B has been reset to "0". Therefore, the operation information determined to have been received in the above step S111 may be operation information indicating a power-on operation on the computer 2 of one of the bases B. In this case, because the transmission flag of the operation information record 111R of the sending base B has been reset to "0", the control unit 11 determines in the above step S114 that the proposal to introduce the RPA scenario has not been sent to the sending base B.
 このように送信元拠点BへRPAシナリオの導入提案を送信済みでないと判断した場合、制御部11は、その送信元拠点Bに対する提案が有るか否かを判断する(ステップS118)。具体的には、制御部11は、提案記憶部134に、その送信元拠点Bに対する提案として、作業とRPAシナリオの組が記憶されているか否か判断する。 If it is determined that the proposal to introduce the RPA scenario has not been sent to the source location B, the control unit 11 determines whether or not there is a proposal for the source location B (step S118). Specifically, the control unit 11 determines whether or not a pair of an operation and an RPA scenario is stored in the proposal storage unit 134 as a proposal for the source location B.
 送信元拠点Bに対する提案が有ると判断した場合、制御部11は、その送信元拠点Bに、RPAシナリオ導入提案を、通信インタフェース14によりネットワークNWを介して送信する(ステップS119)。即ち、制御部11は、提案記憶部134にその送信元拠点Bに対する提案として記憶されている作業とRPAシナリオの組に基づいて、当該作業を実行するのに適したRPAシナリオを導入することを提案する導入提案を作成し、それを送信元拠点Bへ送信する。 If it is determined that there is a proposal for the source location B, the control unit 11 transmits an RPA scenario introduction proposal to the source location B via the network NW using the communication interface 14 (step S119). That is, based on the pair of task and RPA scenario stored in the proposal storage unit 134 as a proposal for the source location B, the control unit 11 creates an introduction proposal proposing the introduction of an RPA scenario suitable for executing the task, and transmits it to the source location B.
 そして、制御部11は、その導入提案を送信した拠点Bに対応する操作情報レコード111Rの送信済みフラグをセット、即ち「1」を記録する(ステップS1110)。その後、制御部11は、上記ステップS116の処理に移行して、操作ログ記憶部131における当該拠点Bのコンピュータ2の操作ログに、電源投入の操作を示す操作情報及び受信時刻を追加記憶させることとなる。 Then, the control unit 11 sets the transmitted flag of the operation information record 111R corresponding to the base B that transmitted the introduction proposal, i.e., records "1" (step S1110). After that, the control unit 11 proceeds to the process of step S116, and additionally stores the operation information indicating the power-on operation and the reception time in the operation log of the computer 2 of the base B in the operation log storage unit 131.
 なお、上記ステップS118において、送信元拠点Bに対する提案が無いと判断した場合、制御部11は、上記ステップS1110の処理に移行して、導入案を送信してはいないが、拠点Bに対応する操作情報レコード111Rの送信済みフラグをセット、即ち「1」を記録する。 If it is determined in step S118 that there is no proposal for the source location B, the control unit 11 proceeds to the process of step S1110, where the control unit 11 sets the transmitted flag of the operation information record 111R corresponding to location B, i.e., records "1", although no introduction proposal has been transmitted.
 拠点Bのコンピュータ2では、提案取得部214がネットワークNWを介して送られてきた導入提案を受信すると、提案取得部214は、出力装置202により、提案された作業とその作業に導入可能なRPAシナリオとを提示する。この提示に対して、入力装置201により、その提案を受諾する操作が行われると、操作情報送信部212により、導入提案を受諾する操作の操作情報が、ネットワークNWを介してサーバ1に送信される。 In the computer 2 at site B, when the proposal acquisition unit 214 receives the introduction proposal sent via the network NW, the proposal acquisition unit 214 presents the proposed work and an RPA scenario that can be introduced into that work via the output device 202. When an operation to accept the proposal is performed via the input device 201 in response to this presentation, the operation information transmission unit 212 transmits operation information of the operation to accept the introduction proposal to the server 1 via the network NW.
 制御部11は、上記ステップS115において、受信した操作情報が導入提案を受諾する操作である判断した場合、その導入を提案したRPAシナリオをシナリオ記憶部133から読み出して、通信インタフェース14によりネットワークNWを介して当該拠点Bのコンピュータ2へ送信する(ステップS1111)。その後、制御部11は、上記ステップS116の処理に移行して、操作ログ記憶部131における当該拠点Bのコンピュータ2の操作ログに、提案受諾の操作を示す操作情報及び受信時刻を追加記憶させることとなる。 If the control unit 11 determines in step S115 that the received operation information is an operation to accept the introduction proposal, it reads out the RPA scenario proposed for introduction from the scenario storage unit 133 and transmits it to the computer 2 at site B via the network NW via the communication interface 14 (step S1111). Thereafter, the control unit 11 proceeds to the processing of step S116, and additionally stores the operation information indicating the operation of accepting the proposal and the reception time in the operation log of the computer 2 at site B in the operation log storage unit 131.
 拠点Bのコンピュータ2では、提案取得部214がネットワークNWを介して送られてきたRPAシナリオを受信すると、提案取得部214は、そのRPAシナリオをシナリオ記憶部231に記憶させる。そして、以降のRPAシナリオを使用可能な作業を実行する際には、そのRPAシナリオを使用して、当該作業を実行していくこととなる。 In the computer 2 at site B, when the proposal acquisition unit 214 receives the RPA scenario sent via the network NW, the proposal acquisition unit 214 stores the RPA scenario in the scenario storage unit 231. Then, when performing subsequent work that can use the RPA scenario, the RPA scenario is used to perform the work.
 以上のようにして、各拠点Bで運用されているRPAシナリオと作業操作ログの一致度を求めることでマッチングし、一致度の高い組み合わせのうちRPAシナリオ未導入である拠点Bの作業に対し、類似する作業に対してRPAシナリオを導入済みの拠点BのRPAを、未導入拠点Bに提案することで水平展開を支援することができる。 In this way, matching is performed by determining the degree of agreement between the RPA scenarios and work operation logs being used at each base B, and for combinations with a high degree of agreement, RPA from base B that has already implemented an RPA scenario for similar work can be proposed to base B that has not implemented the scenario, thereby supporting horizontal expansion.
 以下に、具体例を記す。図13乃至図16は、提案RPAシナリオ決定処理における各作業ログと各RPAシナリオの比較の一例を示す図である。この例では、支店A,B,Cの3つの拠点Bが存在する。ここで、支店Aについては、操作ログ収集・RPAシナリオ提案処理及び操作ログ分類処理により、分類結果記憶部132に、当該支店Aでの作業操作ログとして、作業w1の作業操作ログt1,作業w2の作業操作ログt2,作業w3の作業操作ログt3が記憶され、RPAシナリオ収集処理により、シナリオ記憶部133に、当該支店AとRPAシナリオs1の組が記憶されている。また、支店Bについては、操作ログ収集・RPAシナリオ提案処理及び操作ログ分類処理により、分類結果記憶部132に、当該支店Bでの作業操作ログとして、作業w4の作業操作ログt4,作業w5の作業操作ログt5,作業w6の作業操作ログt6が記憶され、RPAシナリオ収集処理により、シナリオ記憶部133に、当該支店BとRPAシナリオs2の組及び当該支店BとRPAシナリオs3の組が記憶されている。そして、支店Cについては、操作ログ収集・RPAシナリオ提案処理及び操作ログ分類処理により、分類結果記憶部132に、当該支店Cでの作業操作ログとして、作業w7の作業操作ログt7,作業w8の作業操作ログt8,作業w9の作業操作ログt9が記憶されている。 A specific example is described below. Figures 13 to 16 are diagrams showing an example of a comparison between each operation log and each RPA scenario in the proposed RPA scenario determination process. In this example, there are three bases B, namely, branches A, B, and C. Here, for branch A, the operation log t1 of operation w1 , the operation log t2 of operation w2 , and the operation log t3 of operation w3 are stored as operation logs at branch A in the classification result storage unit 132 by the operation log collection/RPA scenario proposal process and the operation log classification process, and a pair of branch A and RPA scenario s1 is stored in the scenario storage unit 133 by the RPA scenario collection process. For branch B, the operation log t4 for operation w4 , the operation log t5 for operation w5, and the operation log t6 for operation w6 are stored in the classification result storage unit 132 as work operation logs for branch B by the operation log collection/RPA scenario proposal process and the operation log classification process, and a pair of branch B and RPA scenario s2 and a pair of branch B and RPA scenario s3 are stored in the scenario storage unit 133 by the RPA scenario collection process. For branch C, the operation log t7 for operation w7 , the work operation log t8 for operation w8, and the work operation log t9 for operation w9 are stored in the classification result storage unit 132 as work operation logs for branch C by the operation log collection / RPA scenario proposal process and the operation log classification process.
 この場合、提案RPAシナリオ決定処理では、支店A,B,Cで行われている作業w1,w2,…,w9についての9通りの作業操作ログt1,t2,…,t9と、RPAシナリオs1,s2,s3それぞれの一致度を算出して、一致度が高い(一定値以上の)組み合わせを抽出する。 In this case, the proposed RPA scenario determination process calculates the degree of similarity between nine work operation logs t1 , t2 , ..., t9 for work w1 , w2 , ..., w9 being performed at branches A , B, and C and RPA scenarios s1 , s2 , and s3 , and extracts combinations with a high degree of similarity (above a certain value).
 そこで、図13に示すように、先ず、作業操作ログt1についてRPAシナリオs1との一致度が判断される。ここで、一致度が低いと判断されると、続けてRPAシナリオs2、s3と比較されていく。何れも一致度が低いと、次に、作業操作ログt2について、RPAシナリオs1、s2、s3との比較が行われていき、ここでも何れも一致度が低いと判断されると、次の作業操作ログt3についての比較が行われる。 13, first, the degree of match between the work operation log t1 and the RPA scenario s1 is judged. If the degree of match is judged to be low, it is compared with the RPA scenarios s2 and s3 . If the degree of match is low, the work operation log t2 is compared with the RPA scenarios s1 , s2 , and s3 . If the degree of match is also low, the next comparison is made with the work operation log t3 .
 そして、図14に示すように、作業操作ログt3とRPAシナリオs1の一致度が高いと判断されたとする。例えば、支店Aにおいて、作業操作ログt3の作業w3に対してRPAシナリオs1が導入されていたとすると、この一致度が高いのは必然である。この場合、上記ステップS147で、当該拠点B(支店A)に、その一致度が一定値以上であると判断されたRPAシナリオs1が導入済みであると判断されるので、支店Aに対してこのRPAシナリオs1の導入提案は行われないこととなる。よって、作業操作ログt3について、次のRPAシナリオs2との比較へと進んでいく。 14, it is assumed that the degree of match between the work operation log t3 and the RPA scenario s1 is high. For example, if RPA scenario s1 has been introduced to the work w3 in the work operation log t3 at branch A, it is inevitable that the degree of match will be high. In this case, since it is determined in step S147 that the RPA scenario s1 , whose degree of match is determined to be equal to or greater than a certain value, has already been introduced at the base B (branch A), the introduction of this RPA scenario s1 is not proposed to branch A. Therefore, the work operation log t3 is compared with the next RPA scenario s2 .
 即ち、図15に示すように、以下、同様にして、作業操作ログt3とRPAシナリオs2、s3との比較、支店Bの作業操作ログt4とRPAシナリオs1、s2、s3との比較、作業操作ログt5とRPAシナリオs1、s2、s3との比較と進む。この場合、作業操作ログt4とRPAシナリオs2及び作業操作ログt5とRPAシナリオs3の一致度が高いと判断されるが、支店BにそれらRPAシナリオs2,s3が導入済みとして、導入提案は行われない。 15, the process similarly proceeds to comparing the work operation log t3 with the RPA scenarios s2 and s3 , comparing the work operation log t4 of branch B with the RPA scenarios s1 , s2 , and s3 , and comparing the work operation log t5 with the RPA scenarios s1 , s2 , and s3 . In this case, it is determined that there is a high degree of agreement between the work operation log t4 and the RPA scenario s2 , and between the work operation log t5 and the RPA scenario s3 , but since the RPA scenarios s2 and s3 have already been introduced in branch B, no introduction proposal is made.
 ここで、作業操作ログt6とRPAシナリオs1とを比較した際、一致度が高いと判断されたとする。この場合、上記ステップS147で、当該拠点B(支店B)に、その一致度が一定値以上であると判断されたRPAシナリオs1は導入済みではないと判断される。よって、支店Bに対して作業操作ログt6の作業である作業w6にRPAシナリオs1を導入することを提案するために、作業w6とRPAシナリオs1の組が、提案記憶部134に記憶される。 Here, when the work operation log t6 and the RPA scenario s1 are compared, it is assumed that the degree of match is high. In this case, it is determined in step S147 that the RPA scenario s1 , whose degree of match is determined to be equal to or greater than a certain value, has not been introduced to the base B (branch B). Therefore, in order to propose to branch B that the RPA scenario s1 be introduced to the work w6 , which is the work of the work operation log t6 , the pair of the work w6 and the RPA scenario s1 is stored in the proposal storage unit 134.
 その後、図16に示すように、作業操作ログt6とRPAシナリオs2、s3との比較、支店Cの作業操作ログt7とRPAシナリオs1、s2、s3との比較が行われて、この提案RPAシナリオ決定処理が終了される。図16の例では、更に、作業操作ログt8とRPAシナリオs3との一致度が高いと判断されたことで、支店Cに対して作業操作ログt8の作業である作業w8にRPAシナリオs3を導入することを提案するために、作業w8とRPAシナリオs3の組が、提案記憶部134に記憶されている。 16, the work operation log t6 is compared with the RPA scenarios s2 and s3 , and the work operation log t7 of branch C is compared with the RPA scenarios s1 , s2 , and s3 , and the proposed RPA scenario determination process is terminated. In the example of FIG. 16, the work operation log t8 is further determined to have a high degree of agreement with the RPA scenario s3 , and therefore the pair of the work w8 and the RPA scenario s3 is stored in the proposal storage unit 134 in order to propose to branch C that the RPA scenario s3 be introduced into the work w8 , which is the work of the work operation log t8 .
 そして、操作ログ収集・RPAシナリオ提案処理において、電源投入されたコンピュータ2の拠点Bについて、提案するRPAシナリオが提案記憶部134に記憶されていれば、それを提案していくこととなる。 Then, in the operation log collection/RPA scenario proposal process, if the proposed RPA scenario for site B of the powered-on computer 2 is stored in the proposal storage unit 134, it will be proposed.
 (効果)
 以上述べたように第1の実施形態では、サーバ1は、それぞれ、作業手順を記述したRPAシナリオを使用した作業とRPAシナリオを使用しない作業との少なくとも一方の作業を少なくとも一つ実行する、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、コンピュータ2に対する操作の操作ログを収集し、収集した操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成すると共に、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、各拠点Bに導入されているRPAシナリオを収集する。そして、サーバ1は、生成した作業操作ログの内、収集したRPAシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点Bのコンピュータ2へ、ネットワークNWを介して、RPAシナリオの導入提案を送信する。このように、サーバ1は、収集したRPAシナリオと各拠点Bでの作業の作業操作ログとをマッチングすることで、RPAシナリオ未導入の作業を実行する拠点Bのコンピュータ2に対して、RPAシナリオの導入を提案する。よって、各拠点Bでは、他拠点Bにおいて類似したRPAシナリオが存在していることが分かり、他拠点BのRPAシナリオを利用するか検討することができる。従って、属人性低く、他拠点のRPAシナリオを利用できるようになるので、RPAシナリオの作成・運用稼働の削減が可能となる。
(effect)
As described above, in the first embodiment, the server 1 collects operation logs of operations on the computers 2 via the network NW from the computers 2 at multiple bases B, each of which performs at least one task using an RPA scenario that describes a task procedure and one that does not use an RPA scenario, divides and classifies the collected operation logs to generate task operation logs that are operation logs for each task, and collects the RPA scenarios introduced at each base B from the computers 2 at multiple bases B via the network NW. Then, the server 1 transmits a proposal for introducing the RPA scenario via the network NW to the computers 2 at the base B that perform tasks for task operation logs that have a degree of agreement with the collected RPA scenario among the generated task operation logs. In this way, the server 1 matches the collected RPA scenario with the task operation logs of the tasks at each base B to propose the introduction of the RPA scenario to the computers 2 at the base B that perform tasks for which an RPA scenario has not been introduced. Thus, each base B can know that a similar RPA scenario exists at the other bases B, and can consider whether to use the RPA scenario at the other bases B. Therefore, since it is less dependent on individuals and it becomes possible to use RPA scenarios from other locations, it is possible to reduce the amount of work required to create and operate RPA scenarios.
 ここで、サーバ1は、生成した作業操作ログと収集したRPAシナリオとの一致度を全ての組み合わせについて算出して、一致度が一定値以上の組み合わせを抽出し、抽出した組み合わせにおける作業を実行する拠点Bのコンピュータ2へ、抽出した組み合わせにおけるRPAシナリオの導入を提案する導入提案を、ネットワークNWを介して送信する。従って、一致度を利用することで、各拠点Bで実行しているそれぞれの作業について、余すことなく且つ容易に、RPAシナリオ導入可能か否かを判別することができる。 Here, the server 1 calculates the degree of match between the generated work operation logs and the collected RPA scenarios for all combinations, extracts combinations for which the degree of match is a certain value or higher, and transmits an introduction proposal proposing the introduction of an RPA scenario for the extracted combination via the network NW to the computer 2 at the site B that performs the work for the extracted combination. Therefore, by using the degree of match, it is possible to thoroughly and easily determine whether an RPA scenario can be introduced for each work being performed at each site B.
 なお、サーバ1は、一致度が一定値以上であるRPAシナリオを使用して作業を実行していない拠点Bのコンピュータ2に対してのみ、RPAシナリオの導入提案を送信する。よって、既にRPAシナリオを導入しているコンピュータ2に対する通信リソースの無駄使いを防止することができる。 Note that the server 1 only sends a proposal to introduce an RPA scenario to the computer 2 at site B that is not executing work using an RPA scenario with a degree of similarity equal to or greater than a certain value. This makes it possible to prevent the waste of communication resources for the computer 2 that has already introduced the RPA scenario.
 なお、サーバ1は、拠点Bのコンピュータ2からネットワークNWを介して送信されてくる操作情報から操作ログを生成すると共に、操作情報に基づく、拠点Bのコンピュータ2による作業の終了の検出に応じて、収集した操作ログの分類以降の動作を開始させ、また、操作情報に基づく、拠点Bのコンピュータ2による作業の開始の検出に応じて、RPAシナリオの導入提案を送信する。このように、サーバ1は、各拠点Bでの操作の都度、操作ログを収集し、例えば1日の終わり等の拠点Bでの作業終了時に導入提案を作成し、翌日の各拠点Bの作業開始時に導入提案を送信する。従って、拠点Bにおける作業の実行中に導入提案が提示されてしまうことを防止することができる。 The server 1 generates an operation log from the operation information transmitted from the computer 2 at base B via the network NW, and starts operations subsequent to classifying the collected operation log in response to detection of the end of work by the computer 2 at base B based on the operation information, and transmits an introduction proposal for an RPA scenario in response to detection of the start of work by the computer 2 at base B based on the operation information. In this way, the server 1 collects operation logs for each operation at each base B, creates an introduction proposal when work at base B ends, such as at the end of the day, and transmits the introduction proposal when work at each base B starts the next day. This makes it possible to prevent an introduction proposal from being presented while work is being performed at base B.
 そして、サーバ1は、RPAシナリオの導入提案を受信した拠点Bのコンピュータ2からネットワークNWを介して提案受諾を受信したとき、当該コンピュータ2へネットワークNWを介して、導入提案を行ったRPAシナリオを送信する。従って、提案受諾を行ったコンピュータ2対して直ちにRPAシナリオを送信することで、拠点BのコンピュータでのRPAシナリオの導入作業を素早く実施することができる。 Then, when the server 1 receives an acceptance of the proposal via the network NW from the computer 2 at site B that received the proposal to introduce the RPA scenario, it transmits the proposed RPA scenario to the computer 2 via the network NW. Therefore, by immediately transmitting the RPA scenario to the computer 2 that accepted the proposal, the introduction work of the RPA scenario on the computer at site B can be quickly carried out.
 [第2の実施形態]
 次に、第2の実施形態を説明する。第1の実施形態と同様の構成及び処理には第1の実施形態と同様の参照符号を付すことでその説明を省略し、第1の実施形態とは異なる部分について説明する。
Second Embodiment
Next, a second embodiment will be described. The same configurations and processes as those in the first embodiment are denoted by the same reference numerals as those in the first embodiment, and the description thereof will be omitted, and only the parts different from the first embodiment will be described.
 (構成例)
 図17は、第2の実施形態に係るシナリオ提案装置としてのサーバ1のソフトウェア構成の一例を示すブロック図である。本実施形態における本部Hのサーバ1の制御部11は、機能部として、操作ログ収集部111及びシナリオ提案部116に代えて操作ログ収集部117及びシナリオ提案部118を備える。また、データ記憶部13に提案記憶部134を有さない。
(Configuration example)
17 is a block diagram showing an example of the software configuration of the server 1 as a scenario proposal device according to the second embodiment. The control unit 11 of the server 1 in the headquarters H in this embodiment includes, as functional units, an operation log collection unit 117 and a scenario proposal unit 118 instead of the operation log collection unit 111 and the scenario proposal unit 116. In addition, the data storage unit 13 does not include the proposal storage unit 134.
 操作ログ収集部117は、任意のタイミングで、通信インタフェース14によりネットワークNWを介して各拠点Bのコンピュータ2へログ要求を送信し、このログ要求に応じてコンピュータ2から送信されてくる操作ログを受信して、操作ログ記憶部131に記憶させる。任意のタイミングは、例えば夜12時等の予め設定されたタイミングであっても良いし、入力装置101によるユーザからの操作ログ収集指示のタイミングであっても良い。操作ログ収集部117は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、コンピュータ2に対する操作の操作ログを収集する操作ログ収集部の一例である。 The operation log collection unit 117 transmits a log request to the computer 2 at each location B via the network NW using the communication interface 14 at any timing, receives the operation log transmitted from the computer 2 in response to this log request, and stores it in the operation log storage unit 131. The arbitrary timing may be a preset timing such as midnight, or may be the timing of an instruction to collect operation logs from the user via the input device 101. The operation log collection unit 117 is an example of an operation log collection unit that collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW.
 なお、ログ分類部112は、本実施形態では、操作ログ収集部117の動作とは無関係に、任意のタイミングで、操作ログ記憶部131に記憶された各拠点Bの操作ログを作業の単位に分割・分類して、作業単位の操作ログである作業操作ログを生成する動作を開始する。任意のタイミングは、例えば夜1時等の予め設定されたタイミングであっても良いし、入力装置101によるユーザからの作業操作ログ生成指示のタイミングであっても良い。 In this embodiment, the log classification unit 112 starts an operation of dividing and classifying the operation logs of each base B stored in the operation log storage unit 131 into task units at an arbitrary timing, regardless of the operation of the operation log collection unit 117, and generating a work operation log, which is an operation log for each task unit. The arbitrary timing may be a preset timing, such as 1:00 a.m., or may be the timing of a user's instruction to generate a work operation log via the input device 101.
 また、組み合わせ抽出部115は、抽出した組み合わせにおける作業操作ログの作業とRPAシナリオの組を、シナリオ提案部118に伝達する。 The combination extraction unit 115 also transmits the pair of the work in the work operation log and the RPA scenario in the extracted combination to the scenario suggestion unit 118.
 シナリオ提案部118は、組み合わせ抽出部115から作業とRPAシナリオの組を受けたとき、その作業とRPAシナリオの組に基づいて、当該作業を実行するのに適したRPAシナリオの導入を提案する導入提案を、当該作業を実行する拠点Bのコンピュータ2に対して、通信インタフェース14によりネットワークNWを介して送信する。そして、シナリオ提案部118は、この導入提案を受けた拠点Bのコンピュータ2からネットワークNWを介して送信されてくる、当該導入提案を受け入れる提案受諾を通信インタフェース14により受信したならば、シナリオ記憶部133に記憶されているそのRPAシナリオを、通信インタフェース14によりネットワークNWを介して当該拠点Bのコンピュータ2へ送信する。シナリオ提案部118は、組み合わせ抽出部が抽出した組み合わせにおける作業を実行する拠点Bのコンピュータ2へ、抽出した組み合わせにおけるシナリオの導入を提案する導入提案を、ネットワークNWを介して送信するシナリオ提案部の一例である。また、シナリオ提案部118は、シナリオの導入提案を受信した拠点Bのコンピュータ2からネットワークNWを介して提案受諾を受信したとき、当該コンピュータ2へネットワークNWを介して、導入提案を行ったシナリオを送信する提案部の一例である。 When the scenario proposal unit 118 receives a pair of an operation and an RPA scenario from the combination extraction unit 115, the scenario proposal unit 118 transmits an introduction proposal proposing the introduction of an RPA scenario suitable for executing the operation based on the pair of the operation and the RPA scenario to the computer 2 at the site B that executes the operation via the communication interface 14 and the network NW. Then, when the scenario proposal unit 118 receives a proposal acceptance that accepts the introduction proposal transmitted via the network NW from the computer 2 at the site B that received the introduction proposal via the communication interface 14, the scenario proposal unit 118 transmits the RPA scenario stored in the scenario storage unit 133 to the computer 2 at the site B via the communication interface 14 and the network NW. The scenario proposal unit 118 is an example of a scenario proposal unit that transmits an introduction proposal proposing the introduction of a scenario in the extracted combination via the network NW to the computer 2 at the site B that executes the operation in the combination extracted by the combination extraction unit. In addition, the scenario proposal unit 118 is an example of a proposal unit that, when it receives a proposal acceptance via the network NW from the computer 2 at site B that received the scenario introduction proposal, transmits the scenario proposed for introduction to the computer 2 via the network NW.
 図18は、第2の実施形態において拠点Bに配置されたコンピュータ2のソフトウェア構成の一例を示すブロック図である。本実施形態における拠点Bのコンピュータ2は、機能部として、操作情報送信部212に代えて操作ログ記録部215及びログ出力部216を備える。また、データ記憶部23は、更に、操作ログ記憶部232を有する。 FIG. 18 is a block diagram showing an example of the software configuration of the computer 2 arranged at the base B in the second embodiment. The computer 2 at the base B in this embodiment has, as functional units, an operation log recording unit 215 and a log output unit 216 instead of the operation information transmission unit 212. In addition, the data storage unit 23 further has an operation log storage unit 232.
 操作ログ記録部215は、作業実行部211から伝達された操作情報を、操作ログ記憶部232に記憶された操作ログに追加記録していくことで、操作ログを更新していく。操作ログは、操作情報の操作時刻を含んでも良い。 The operation log recording unit 215 updates the operation log stored in the operation log storage unit 232 by additionally recording the operation information transmitted from the task execution unit 211 to the operation log. The operation log may include the operation time of the operation information.
 ログ出力部216は、ネットワークNWを介してサーバ1からログ要求を受信したとき、操作ログ記憶部232に記憶されている操作ログを、ネットワークNWを介してサーバ1に送信する。 When the log output unit 216 receives a log request from the server 1 via the network NW, it transmits the operation log stored in the operation log storage unit 232 to the server 1 via the network NW.
 (動作例)
 図19は、第2の実施形態におけるサーバ1の処理手順と処理内容を示すフローチャートである。本第2の実施形態においては、各拠点Bで操作の都度、各拠点Bでログを記録しておき、サーバ1は、任意のタイミングで各拠点Bからログを収集して提案を作成するよう動作する。
(Example of operation)
19 is a flowchart showing the processing procedure and processing contents of the server 1 in the second embodiment. In the second embodiment, a log is recorded at each site B every time an operation is performed at each site B, and the server 1 operates to collect the logs from each site B at any timing and create a proposal.
 サーバ1の制御部11は、任意のタイミングで、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、当該コンピュータ2に対する操作の操作ログを収集する操作ログ収集処理を実行する(ステップS15)。この操作ログ収集処理の典型例については後述する。 The control unit 11 of the server 1 executes an operation log collection process to collect operation logs of operations on the computers 2 from the computers 2 at multiple locations B via the network NW at any timing (step S15). A typical example of this operation log collection process will be described later.
 次に、サーバ1の制御部11は、RPAシナリオの提案を実施するか否か判断する(ステップS16)。例えば、予め設定された時刻となったか否か、或いは、入力装置101によるユーザからの作業操作ログ生成指示が有ったか否かにより、制御部11は、これを判断することができる。RPAシナリオの提案を実施しないと判断した場合、制御部11は、上記ステップS15の処理に移行する。 The control unit 11 of the server 1 then determines whether or not to implement the proposed RPA scenario (step S16). For example, the control unit 11 can determine this based on whether or not a preset time has arrived, or whether or not a user has issued an instruction to generate a work operation log via the input device 101. If it is determined that the proposed RPA scenario will not be implemented, the control unit 11 proceeds to the processing of step S15 above.
 これに対して、RPAシナリオの提案を実施すると判断した場合、制御部11は、第1の実施形態と同様に、ステップS12の操作ログ分類処理及びステップS13のPAシナリオ収集処理を実行する。 In contrast, if it is determined that an RPA scenario should be proposed, the control unit 11 executes the operation log classification process of step S12 and the PA scenario collection process of step S13, as in the first embodiment.
 その後、サーバ1の制御部11は、生成した作業操作ログの内、収集したシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点Bのコンピュータへ、ネットワークNWを介して、RPAシナリオの導入提案を送信するRPAシナリオ提案処理を実行する(ステップS17)。このRPAシナリオ提案処理の典型例については後述する。そして、サーバ1の制御部11は、上記ステップS15の操作ログ収集処理に移行する。 Then, the control unit 11 of the server 1 executes an RPA scenario proposal process to send an RPA scenario introduction proposal via the network NW to the computer at base B that executes the work of the work operation logs that have a degree of match with the collected scenario that is equal to or greater than a certain value among the generated work operation logs (step S17). A typical example of this RPA scenario proposal process will be described later. The control unit 11 of the server 1 then proceeds to the operation log collection process of step S15 above.
 また、サーバ1制御部11は、上記ステップS15,S16,S12,S13,S17の処理と併行して、提案を受諾した拠点Bのコンピュータ2へRPAシナリオをネットワークNWを介して送信するRPAシナリオ送信処理を実行する(ステップS18)。このRPAシナリオ送信処理の典型例については後述する。そして、サーバ1の制御部11は、上記ステップS15の操作ログ収集処理に移行する。 In addition, in parallel with the processes of steps S15, S16, S12, S13, and S17, the server 1 control unit 11 executes an RPA scenario transmission process to transmit the RPA scenario via the network NW to the computer 2 of site B that accepted the proposal (step S18). A typical example of this RPA scenario transmission process will be described later. Then, the control unit 11 of the server 1 proceeds to the operation log collection process of step S15.
 図20は、第2の実施形態におけるサーバ1の操作ログ収集処理の処理手順と処理内容を示すフローチャートである。図20は、ステップS15の処理の典型例を示す。ここでは、サーバ1の制御部11は、操作ログ収集部117として動作する。 FIG. 20 is a flowchart showing the procedure and content of the operation log collection process of the server 1 in the second embodiment. FIG. 20 shows a typical example of the process of step S15. Here, the control unit 11 of the server 1 operates as the operation log collection unit 117.
 制御部11は、任意タイミングである操作ログの収集タイミングであるか否か判断する(ステップS151)。ここで、収集タイミングでないと判断した場合、制御部11は、上記ステップS16の処理へ移行する。 The control unit 11 determines whether or not it is time to collect an operation log, which is an arbitrary timing (step S151). If it is determined that it is not time to collect the operation log, the control unit 11 proceeds to the process of step S16.
 これに対して、収集タイミングであると判断した場合、制御部11は、操作ログ記憶部131を参照して、操作ログを未収集の拠点Bが有るか否か判断する(ステップS152)。 In contrast, if it is determined that it is time to collect, the control unit 11 refers to the operation log storage unit 131 and determines whether there is a location B for which operation logs have not yet been collected (step S152).
 操作ログ未収集の拠点Bが有ると判断した場合、制御部11は、未収集の拠点Bの内の一つに対して、通信インタフェース14によりネットワークNWを介して、当該拠点Bのコンピュータ2で記憶している操作ログの送信を依頼するログ要求を送信する(ステップS153)。 If it is determined that there is a location B from which operation logs have not been collected, the control unit 11 sends a log request to one of the locations B from which operation logs have not been collected, via the communication interface 14 and the network NW, requesting the sending of the operation logs stored in the computer 2 of that location B (step S153).
 拠点Bのコンピュータ2では、ログ出力部216がネットワークNWを介して送られてきたログ要求を受信すると、ログ出力部216は、操作ログ記憶部232に記憶している操作ログを読み出して、ネットワークNWを介してサーバ1へ送信する。 When the log output unit 216 of the computer 2 at site B receives a log request sent via the network NW, the log output unit 216 reads out the operation log stored in the operation log memory unit 232 and transmits it to the server 1 via the network NW.
 制御部11は、このログ要求に応答して当該拠点Bのコンピュータ2からネットワークNWを介して返信されてくる操作ログを通信インタフェース14により受信する(ステップS154)。 The control unit 11 receives the operation log returned from the computer 2 at the site B via the network NW in response to the log request through the communication interface 14 (step S154).
 そして、制御部11は、その受信した操作ログと、その送信元を示す拠点情報との組を、操作ログ記憶部131に記録する(ステップS155)。拠点情報は、前述したように、拠点Bのそれぞれに一意に割り当てられた拠点IDであることができる。その後、制御部11は、上記ステップS152の処理に移行する。 Then, the control unit 11 records a pair of the received operation log and the base information indicating its sender in the operation log storage unit 131 (step S155). As described above, the base information can be a base ID uniquely assigned to each base B. Thereafter, the control unit 11 proceeds to the process of step S152.
 そして、上記ステップS152において、操作ログ未収集の拠点Bが無いと判断すると、制御部11は、上記ステップS16の処理へ移行する。 If it is determined in step S152 that there is no location B for which operation logs have not been collected, the control unit 11 proceeds to the processing of step S16.
 図21は、第2の実施形態におけるサーバ1のRPAシナリオ提案処理の処理手順と処理内容を示すフローチャートである。図21は、ステップS17の処理の典型例を示す。ここでは、サーバ1の制御部11は、一致度算出部114、組み合わせ抽出部115及びシナリオ提案部118として動作する。 FIG. 21 is a flowchart showing the processing procedure and processing contents of the RPA scenario proposal processing of the server 1 in the second embodiment. FIG. 21 shows a typical example of the processing of step S17. Here, the control unit 11 of the server 1 operates as a coincidence calculation unit 114, a combination extraction unit 115, and a scenario proposal unit 118.
 制御部11は、第1の実施形態における上記ステップS141と同様に、分類結果記憶部132を参照して、RPAシナリオとの一致度を比較していない未比較の作業操作ログが有るか否か判断する(ステップS171)。 Similar to step S141 in the first embodiment, the control unit 11 refers to the classification result storage unit 132 to determine whether there are any uncompared work operation logs that have not been compared for their degree of similarity with the RPA scenario (step S171).
 未比較の作業操作ログが有ると判断した場合、制御部11は、第1の実施形態における上記ステップS142と同様に、分類結果記憶部132から未比較の作業操作ログを一つ読み出す(ステップS172)。 If it is determined that there is an uncompared work operation log, the control unit 11 reads one uncompared work operation log from the classification result storage unit 132 (step S172), similar to step S142 in the first embodiment.
 ここで、制御部11は、第1の実施形態における上記ステップS143と同様に、シナリオ記憶部133を参照して、読み出した作業操作ログとの一致度を比較していない未比較のRPAシナリオが有るか否か判断する(ステップS173)。 Here, similar to step S143 in the first embodiment, the control unit 11 refers to the scenario storage unit 133 to determine whether there is an RPA scenario that has not been compared with the read work operation log for degree of similarity (step S173).
 未比較のRPAシナリオが有ると判断した場合、制御部11は、第1の実施形態における上記ステップS144と同様に、シナリオ記憶部133から未比較のRPAシナリオを一つ読み出す(ステップS174)。 If it is determined that there is an uncompared RPA scenario, the control unit 11 reads out one uncompared RPA scenario from the scenario storage unit 133 (step S174), similar to step S144 in the first embodiment.
 そして、制御部11は、第1の実施形態における上記ステップS145と同様に、それら読み出した作業操作ログと読み出したRPAシナリオとを比較する(ステップS175)。 Then, the control unit 11 compares the read work operation logs with the read RPA scenario (step S175), similar to step S145 in the first embodiment.
 ここで、制御部11は、第1の実施形態における上記ステップS146と同様に、作業操作ログとRPAシナリオの一致度、例えばコサイン類似度、が予め定めた一定値以上であるか否か判断する(ステップS176)。ここで、一致度が一定値以上でないと判断した場合、制御部11は、上記ステップS173の処理に移行する。 The control unit 11 then determines whether the degree of match between the work operation log and the RPA scenario, for example the cosine similarity, is equal to or greater than a predetermined value (step S176), similar to step S146 in the first embodiment. If the control unit 11 determines that the degree of match is not equal to or greater than the predetermined value, it proceeds to the process of step S173.
 これに対して、上記ステップS176において、作業操作ログとRPAシナリオの一致度が一定値以上であると判断した場合、制御部11は、第1の実施形態における上記ステップS147と同様に、その作業操作ログの拠点Bにおける作業は、そのRPAシナリオが導入済みの作業であるか否か判断する(ステップS177)。ここで、RPAシナリオ導入済み作業であると判断した場合、制御部11は、上記ステップS173の処理に移行する。 In contrast, if it is determined in step S176 that the degree of match between the work operation log and the RPA scenario is equal to or greater than a certain value, the control unit 11 determines whether the work at base B in the work operation log is a work for which the RPA scenario has already been introduced (step S177), similar to step S147 in the first embodiment. Here, if it is determined that the work is a work for which the RPA scenario has already been introduced, the control unit 11 proceeds to the processing of step S173.
 これに対して、RPAシナリオ導入済み作業ではないと判断した場合、制御部11は、その作業操作ログの作業とRPAシナリオの組に基づいてRPAシナリオの導入提案を作成し、それを通信インタフェース14によりネットワークNWを介して、当該作業を実行する拠点Bのコンピュータ2へ送信する(ステップS178)。その後、制御部11は、上記ステップS173の処理に移行する。 In contrast, if it is determined that the task does not have an RPA scenario introduced, the control unit 11 creates an RPA scenario introduction proposal based on the pair of the task and the RPA scenario in the task operation log, and transmits it via the communication interface 14 over the network NW to the computer 2 at site B that will execute the task (step S178). After that, the control unit 11 proceeds to the processing of step S173.
 以上のようにして、本第2の実施形態においても、第1の実施形態と同様、各拠点Bで運用されているRPAシナリオと作業操作ログの一致度を求めることでマッチングし、一致度の高い組み合わせのうちRPAシナリオ未導入である拠点Bの作業に対し、類似する作業に対してRPAシナリオを導入済みの拠点BのRPAを、未導入拠点Bに提案することで水平展開を支援することができる。 As described above, in this second embodiment, as in the first embodiment, matching is performed by determining the degree of agreement between the RPA scenarios and work operation logs operated at each base B, and for work at base B that has not yet introduced an RPA scenario among combinations with a high degree of agreement, horizontal expansion can be supported by proposing RPA from base B, which has already introduced an RPA scenario for similar work, to the base B that has not yet introduced an RPA scenario.
 図22は、第2の実施形態におけるサーバ1のRPAシナリオ送信処理の処理手順と処理内容を示すフローチャートである。図22は、ステップS18の処理の典型例を示す。ここでは、サーバ1の制御部11は、シナリオ提案部118として動作する。 FIG. 22 is a flowchart showing the procedure and content of the RPA scenario transmission process of the server 1 in the second embodiment. FIG. 22 shows a typical example of the process of step S18. Here, the control unit 11 of the server 1 operates as a scenario suggestion unit 118.
 制御部11は、何れかの拠点Bのコンピュータ2からネットワークNWを介して送信されてくる提案受諾を受信したか否か判断する(ステップS181)。提案受諾を受信していないと判断した場合、制御部11は、再度、このステップS18の処理に移行する。 The control unit 11 determines whether or not a proposal acceptance transmitted via the network NW has been received from the computer 2 at any of the locations B (step S181). If it is determined that a proposal acceptance has not been received, the control unit 11 transitions to the process of step S18 again.
 拠点Bのコンピュータ2では、RPAシナリオ提案処理の上記ステップS178においてネットワークNWを介して送信された導入提案を提案取得部214が受信すると、提案取得部214は、出力装置202により、提案された作業とその作業に導入可能なRPAシナリオとを提示する。この提示に対して、入力装置201により、その提案を受諾する操作が行われると、操作情報送信部212により、導入提案を受諾することを示す提案受諾をネットワークNWを介してサーバ1に送信する。 In the computer 2 at site B, when the proposal acquisition unit 214 receives the introduction proposal transmitted via the network NW in step S178 of the RPA scenario proposal process, the proposal acquisition unit 214 presents the proposed work and an RPA scenario that can be introduced into that work via the output device 202. When an operation to accept the proposal is performed via the input device 201 in response to this presentation, the operation information transmission unit 212 transmits a proposal acceptance indicating that the introduction proposal is accepted to the server 1 via the network NW.
 制御部11は、上記ステップS181において、何れかの拠点Bのコンピュータ2からの提案受諾を受信したと判断した場合、上記ステップS178でその拠点Bに対して導入を提案したRPAシナリオをシナリオ記憶部133から読み出して、通信インタフェース14によりネットワークNWを介して当該拠点Bのコンピュータ2へ送信する(ステップS182)。その後、制御部11は、再度、このステップS18の処理に移行する。 If the control unit 11 determines in step S181 that it has received a proposal acceptance from the computer 2 of one of the locations B, it reads out the RPA scenario proposed for introduction to that location B in step S178 from the scenario storage unit 133 and transmits it to the computer 2 of that location B via the network NW via the communication interface 14 (step S182). After that, the control unit 11 again proceeds to the processing of step S18.
 拠点Bのコンピュータ2では、提案取得部214がネットワークNWを介して送られてきたRPAシナリオを受信すると、提案取得部214は、そのRPAシナリオをシナリオ記憶部231に記憶させる。そして、以降のRPAシナリオを使用可能な作業を作業実行部211が実行する際には、作業実行部211は、そのRPAシナリオを使用して、当該作業を実行していくこととなる。 In the computer 2 at site B, when the proposal acquisition unit 214 receives the RPA scenario sent via the network NW, the proposal acquisition unit 214 stores the RPA scenario in the scenario storage unit 231. Then, when the work execution unit 211 executes a task that can use the RPA scenario thereafter, the work execution unit 211 uses the RPA scenario to execute the task.
 (効果)
 以上述べたように第2の実施形態においても、サーバ1は、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、コンピュータ2に対する操作の操作ログを収集し、任意のタイミングで、その収集した操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成すると共に、複数の拠点Bのコンピュータ2から、ネットワークNWを介して、各拠点Bに導入されているRPAシナリオを収集する。そして、サーバ1は、生成した作業操作ログの内、収集したRPAシナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点Bのコンピュータ2へ、ネットワークNWを介して、RPAシナリオの導入提案を送信する。従って、第2の実施形態においても、第1の実施形態と同様、属人性低く、他拠点のRPAシナリオを利用できるようになるので、RPAシナリオの作成・運用稼働の削減が可能となる。
(effect)
As described above, in the second embodiment, the server 1 also collects operation logs of operations on the computer 2 from the computers 2 at multiple locations B via the network NW, and at any timing divides and classifies the collected operation logs to generate work operation logs that are operation logs for each task, and collects RPA scenarios introduced at each location B from the computers 2 at multiple locations B via the network NW. Then, the server 1 transmits an introduction proposal for the RPA scenario via the network NW to the computers 2 at the location B that execute the work of the work operation logs that have a degree of agreement with the collected RPA scenario among the generated work operation logs. Therefore, in the second embodiment, as in the first embodiment, it is possible to use RPA scenarios at other locations with low dependency on individuals, and therefore it is possible to reduce the creation and operation of the RPA scenario.
 また、サーバ1は、拠点Bのコンピュータ2からネットワークNWを介して送信されてくる操作ログを受信し、操作ログの分類、シナリオの収集、及びシナリオの提案は、予め設定されたタイミングで又はユーザ指示に応じて行う。従って、常に各拠点Bのコンピュータ2から操作情報を取得する必要は無く、任意のタイミングで操作ログをまとめて終始有することができ、通信リソースを消費し続けることを防止することができる。また、収集した操作ログに基づく、シナリオ提案のための処理の開始タイミングも調整することが可能となる。 The server 1 also receives operation logs sent from the computer 2 at site B via the network NW, and classifies the operation logs, collects scenarios, and proposes scenarios at preset times or in response to user instructions. Therefore, there is no need to constantly obtain operation information from the computer 2 at each site B, and operation logs can be collected and kept at any time, preventing the continuous consumption of communication resources. It is also possible to adjust the start timing of processing for scenario proposal based on the collected operation logs.
 [第3の実施形態]
 次に、第3の実施形態を説明する。以下、第1の実施形態と異なる部分についてのみ説明する。第1の実施形態では、作業操作ログとRPAシナリオの一致度を一つずつ算出して、都度、RPAシナリオの提案を行うか否か判断している。これに対して、本第3の実施形態は、作業操作ログとRPAシナリオの一致度を全て算出して、それら全ての一致度の中から高い一致度の組み合わせについて、RPAシナリオの提案を行うか否か判断するようにしたものである。
[Third embodiment]
Next, a third embodiment will be described. Only the parts that differ from the first embodiment will be described below. In the first embodiment, the degree of match between the work operation log and the RPA scenario is calculated one by one, and it is determined whether or not to propose an RPA scenario each time. In contrast, in the third embodiment, all the degrees of match between the work operation log and the RPA scenario are calculated, and it is determined whether or not to propose an RPA scenario for the combination with the highest degree of match among all the degrees of match.
 図23は、第3の実施形態におけるサーバの提案拡張UI決定処理の処理手順と処理内容を示すフローチャートである。本第3の実施形態においては、ステップS145において作業操作ログとRPAシナリオを比較したならば、制御部11は、その比較によって得られた一致度を、自身が備えるRAMに保存する(ステップS149)。勿論、データ記憶部23に一致度記憶部を確保することで、そこに保存するようにしても良い。その後、制御部11は、上記ステップS143の処理に移行する。こうして、上記ステップS142で読み出した作業操作ログを、ステップS144で読み出したRPAシナリオと比較していく。そして、作業操作ログに対して全てのRPAシナリオの比較が行われたならば、制御部11は、上記ステップS143において未比較のRPAシナリオが無いと判断し、上記ステップS141の処理に移行する。これにより、制御部11は、分類結果記憶部132に記憶されている次の未比較の作業操作ログに対する各RPAシナリオとの比較処理へと進むことができる。このようにして、制御部11は、作業操作ログとRPAシナリオの全ての一致度を、保存することができる。 23 is a flowchart showing the processing procedure and processing contents of the proposed extended UI determination process of the server in the third embodiment. In this third embodiment, if the work operation log and the RPA scenario are compared in step S145, the control unit 11 stores the degree of agreement obtained by the comparison in its own RAM (step S149). Of course, it is also possible to store the degree of agreement in a memory unit by securing the degree of agreement in the data memory unit 23. After that, the control unit 11 proceeds to the processing of step S143. In this way, the work operation log read in step S142 is compared with the RPA scenario read in step S144. Then, when all the RPA scenarios have been compared with the work operation log, the control unit 11 determines in step S143 that there is no uncompared RPA scenario, and proceeds to the processing of step S141. As a result, the control unit 11 can proceed to the comparison processing of each RPA scenario with the next uncompared work operation log stored in the classification result memory unit 132. In this way, the control unit 11 can store all the degrees of agreement between the work operation log and the RPA scenario.
 そして、上記ステップS141において、未比較の作業操作ログが無いと判断すると、制御部11は、保存された全一致度の中から、一致度が一定値以上の作業操作ログとRPAシナリオの組を抽出する(ステップS1410)。 If it is determined in step S141 that there are no uncompared work operation logs, the control unit 11 extracts pairs of work operation logs and RPA scenarios whose degree of matching is equal to or greater than a certain value from all the stored degrees of matching (step S1410).
 更に、制御部11は、それら抽出した一致度が一定値以上の作業操作ログとRPAシナリオの組の中から、既に拠点Bにおける作業にRPAシナリオが導入済みの作業操作ログとRPAシナリオの組を除外する(ステップS1411)。 Furthermore, the control unit 11 excludes pairs of work operation logs and RPA scenarios in which an RPA scenario has already been introduced into work at site B from among the extracted pairs of work operation logs and RPA scenarios whose degree of match is equal to or greater than a certain value (step S1411).
 そして、制御部11は、ステップS148の処理に移行して、抽出した残りの作業操作ログとRPAシナリオの組それぞれに基づいて、該当する拠点BへのRPAシナリオの提案を提案記憶部134に記録することとなる。その後、制御部11は、上記ステップS11の操作ログ収集・拡張UI提案処理へ移行する。 Then, the control unit 11 proceeds to the process of step S148, and records a proposal for an RPA scenario for the relevant base B in the proposal storage unit 134 based on each of the remaining pairs of work operation logs and RPA scenarios that have been extracted. After that, the control unit 11 proceeds to the operation log collection and extended UI proposal process of step S11.
 このように、全ての作業操作ログとRPAシナリオの一致度を算出して、それら全ての一致度の中から高い一致度の組み合わせについて、RPAシナリオの提案を行うか否か判断するようにしても、前述した第1の実施形態と同様の効果を奏する。 In this way, the degree of match between all work operation logs and RPA scenarios is calculated, and a decision is made as to whether or not to propose an RPA scenario for the combination with the highest degree of match among all of the degrees of match, achieving the same effect as in the first embodiment described above.
 また、第2の実施形態においても、全ての作業操作ログとRPAシナリオの一致度を算出して、それら全ての一致度の中から高い一致度の組み合わせについて、RPAシナリオの提案を行うか否か判断するようにしても良いことは勿論である。 In addition, in the second embodiment, it is also possible to calculate the degree of match between all work operation logs and RPA scenarios, and then determine whether or not to propose an RPA scenario for the combination with the highest degree of match among all of those degrees of match.
 [その他の実施形態]
 各実施形態では、RPAシナリオの導入提案と実際のRPAシナリオの送信とは別の処理としているが、RPAシナリオの導入提案にRPAシナリオ自体を含んで送信するようにしても良い。拠点Bのコンピュータ2の提案取得部214は、このような導入提案を受信した場合、その提案を受諾するときのみ、RPAシナリオをシナリオ記憶部231に登録し、受諾しない場合は受信したRPAシナリオを破棄するようにすれば良い。
[Other embodiments]
In each embodiment, the proposal to introduce an RPA scenario and the transmission of an actual RPA scenario are separate processes, but the proposal to introduce an RPA scenario may include the RPA scenario itself and transmit it. When the proposal acquisition unit 214 of the computer 2 at site B receives such an introduction proposal, it registers the RPA scenario in the scenario storage unit 231 only when the proposal is accepted, and discards the received RPA scenario when the proposal is not accepted.
 また、フローチャートを参照して説明した各処理の流れは、説明した処理手順に限定されるものではない。例えば、ステップS114,S115の処理は、この順序とは異なる順序で行っても良いし、同時に併行して行っても良い。このように、幾つかのステップの順序が入れ替えられても良いし、幾つかのステップが同時併行で実施されても良い。更に、幾つかのステップの処理内容が修正されても良い。 Furthermore, the flow of each process described with reference to the flowchart is not limited to the process procedure described. For example, the processes of steps S114 and S115 may be performed in an order different from this order, or may be performed simultaneously in parallel. In this way, the order of some steps may be changed, or some steps may be performed simultaneously in parallel. Furthermore, the processing content of some steps may be modified.
 シナリオ提案装置は、上記の例で説明したように1つの装置で実現されても良いし、機能を分散させた複数の装置で実現されても良い。 The scenario proposal device may be realized as a single device as described in the above example, or may be realized as multiple devices with distributed functions.
 プログラムは、電子機器に記憶された状態で譲渡されて良いし、電子機器に記憶されていない状態で譲渡されても良い。後者の場合は、プログラムは、ネットワークを介して譲渡されて良いし、記録媒体に記録された状態で譲渡されても良い。記録媒体は、非一時的な有形の媒体である。記録媒体は、コンピュータ可読媒体である。記録媒体は、CD-ROM、メモリカード等のプログラムを記憶可能かつコンピュータで読取可能な媒体であれば良く、その形態は問わない。 The program may be transferred in a state where it is stored in an electronic device, or in a state where it is not stored in an electronic device. In the latter case, the program may be transferred via a network, or in a state where it is recorded on a recording medium. The recording medium is a non-transitory tangible medium. The recording medium is a computer-readable medium. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it is capable of storing the program and is computer-readable.
 以上、本発明の実施形態を詳細に説明してきたが、前述までの説明はあらゆる点において本発明の例示に過ぎない。本発明の範囲を逸脱することなく種々の改良や変形を行うことができることは言うまでもない。つまり、本発明の実施にあたって、実施形態に応じた具体的構成が適宜採用されても良い。 Although the embodiments of the present invention have been described in detail above, the above description is merely an example of the present invention in every respect. It goes without saying that various improvements and modifications can be made without departing from the scope of the present invention. In other words, when implementing the present invention, specific configurations according to the embodiments may be appropriately adopted.
 要するにこの発明は、上記実施形態そのままに限定されるものではなく、実施段階ではその要旨を逸脱しない範囲で構成要素を変形して具体化できる。また、上記実施形態に開示されている複数の構成要素の適宜な組み合わせにより種々の発明を形成できる。例えば、実施形態に示される全構成要素から幾つかの構成要素を削除しても良い。更に、異なる実施形態に亘る構成要素を適宜組み合せても良い。 In short, this invention is not limited to the above-described embodiment as it is, and in the implementation stage, the components can be modified and embodied without departing from the gist of the invention. Furthermore, various inventions can be formed by appropriate combinations of multiple components disclosed in the above-described embodiment. For example, some components may be deleted from all of the components shown in the embodiment. Furthermore, components from different embodiments may be appropriately combined.
 1…サーバ
 2…コンピュータ
 11,21…制御部
 12,22…プログラム記憶部
 13,23…データ記憶部
 14,24…通信インタフェース
 15,25…入出力インタフェース
 101,201…入力装置
 102,202…出力装置
 111,117…操作ログ収集部
 111R…操作情報レコード
 112…ログ分類部
 113…シナリオ収集部
 114…一致度算出部
 115…組み合わせ抽出部
 116,118…シナリオ提案部
 131,232…操作ログ記憶部
 132…分類結果記憶部
 133,231…シナリオ記憶部
 134…提案記憶部
 211…作業実行部
 212…操作情報送信部
 213…シナリオ出力部
 214…提案取得部
 215…操作ログ記録部
 216…ログ出力部
 B…拠点
 H…本部
 LOG…操作ログ
 NDS…ノード詳細画面
 NW…ネットワーク
 S…シナリオ提案システム
Reference Signs List 1: Server 2: Computer 11, 21: Control unit 12, 22: Program storage unit 13, 23: Data storage unit 14, 24: Communication interface 15, 25: Input/output interface 101, 201: Input device 102, 202: Output device 111, 117: Operation log collection unit 111R: Operation information record 112: Log classification unit 113: Scenario collection unit 114: Matching degree calculation unit 115: Combination extraction unit 116, 118: Scenario proposal unit 131, 232: Operation log storage unit 132: Classification result storage unit 133, 231: Scenario storage unit 134: Proposal storage unit 211: Work execution unit 212: Operation information transmission unit 213: Scenario output unit 214: Proposal acquisition unit 215: Operation log recording unit 216: Log output unit B: Base H: Headquarters LOG: Operation log NDS: Node details screen NW: Network S: Scenario proposal system

Claims (8)

  1.  それぞれ、作業手順を記述したシナリオを使用した作業と前記シナリオを使用しない作業との少なくとも一方の作業を少なくとも一つ実行する、複数の拠点のコンピュータから、ネットワークを介して、前記コンピュータに対する操作の操作ログを収集する操作ログ収集部と、
     前記操作ログ収集部が収集した前記操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成する分類部と、
     前記複数の拠点のコンピュータから、前記ネットワークを介して、各拠点に導入されている前記シナリオを収集するシナリオ収集部と、
     前記分類部が生成した前記作業操作ログの内、前記シナリオ収集部が収集した前記シナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点の前記コンピュータへ、前記ネットワークを介して、前記シナリオの導入提案を送信する提案部と、
     を具備するシナリオ提案装置。
    an operation log collection unit that collects, via a network, operation logs of operations performed on computers at a plurality of bases, each of which performs at least one task using a scenario describing a procedure and one task not using the scenario;
    a classification unit that divides and classifies the operation logs collected by the operation log collection unit to generate a work operation log that is an operation log for each work;
    a scenario collection unit that collects the scenarios introduced at each of the plurality of base locations from the computers at the plurality of base locations via the network;
    a proposal unit that transmits, via the network, a proposal for introducing the scenario to the computer at the base that executes work of a work operation log that has a degree of coincidence with the scenario collected by the scenario collecting unit that is equal to or greater than a certain value among the work operation logs generated by the classification unit;
    A scenario proposal device comprising:
  2.  前記提案部は、
      前記分類部が生成した前記作業操作ログと前記シナリオ収集部が収集した前記シナリオとの一致度を全ての組み合わせについて算出する一致度算出部と、
      前記一致度算出部が算出した前記一致度が前記一定値以上の組み合わせを抽出する組み合わせ抽出部と、
      前記組み合わせ抽出部が抽出した前記組み合わせにおける前記作業を実行する拠点の前記コンピュータへ、前記抽出した前記組み合わせにおける前記シナリオの導入を提案する前記導入提案を、前記ネットワークを介して送信するシナリオ提案部と、
    を含む、
     請求項1に記載のシナリオ提案装置。
    The suggestion unit,
    a coincidence calculation unit that calculates a coincidence between the work operation log generated by the classification unit and the scenario collected by the scenario collection unit for all combinations;
    a combination extraction unit that extracts combinations in which the degree of coincidence calculated by the degree of coincidence calculation unit is equal to or greater than the certain value;
    a scenario suggestion unit that transmits, via the network, the introduction proposal that proposes introduction of the scenario in the extracted combination to the computer at the base that performs the work in the combination extracted by the combination extraction unit;
    including,
    The scenario proposal device according to claim 1 .
  3.  前記提案部は、前記一致度が前記一定値以上である前記シナリオを使用して前記作業を実行していない拠点の前記コンピュータに対してのみ、前記シナリオの前記導入提案を送信する、
     請求項1又は2に記載のシナリオ提案装置。
    the proposal unit transmits the proposal to introduce the scenario only to the computers at the bases that have not executed the work using the scenario with the degree of coincidence equal to or greater than the certain value.
    The scenario proposal device according to claim 1 or 2.
  4.  前記操作ログ収集部は、
      前記拠点の前記コンピュータから前記ネットワークを介して送信されてくる操作情報から前記操作ログを生成すると共に、
      前記操作情報に基づく、前記拠点の前記コンピュータによる前記作業の終了の検出に応じて、前記分類部の動作を開始させ、
      前記操作情報に基づく、前記拠点の前記コンピュータによる前記作業の開始の検出に応じて、前記提案部による前記シナリオの前記導入提案の送信を行わせる、
     請求項3に記載のシナリオ提案装置。
    The operation log collection unit includes:
    generating the operation log from operation information transmitted from the computer at the base via the network;
    starting an operation of the classification unit in response to detection of completion of the work by the computer at the site based on the operation information;
    causing the proposal unit to transmit the introduction proposal of the scenario in response to detection of the start of the work by the computer at the base based on the operation information;
    The scenario proposing device according to claim 3 .
  5.  前記操作ログ収集部は、前記拠点の前記コンピュータから前記ネットワークを介して送信されてくる前記操作ログを受信し、
     前記分類部、前記シナリオ収集部及び前記提案部は、予め設定されたタイミングで又はユーザ指示に応じて動作を開始する、
     請求項3に記載のシナリオ提案装置。
    the operation log collection unit receives the operation log transmitted from the computer at the base via the network,
    the classification unit, the scenario collection unit, and the proposal unit start their operations at a preset timing or in response to a user instruction.
    The scenario proposing device according to claim 3 .
  6.  前記提案部は、前記シナリオの前記導入提案を受信した前記拠点の前記コンピュータから前記ネットワークを介して提案受諾を受信したとき、当該コンピュータへ前記ネットワークを介して、前記導入提案を行った前記シナリオを送信する、
     請求項3に記載のシナリオ提案装置。
    when the proposal unit receives a proposal acceptance via the network from the computer at the base that has received the introduction proposal of the scenario, the proposal unit transmits the scenario for which the introduction proposal was made to the computer via the network.
    The scenario proposing device according to claim 3 .
  7.  プロセッサとメモリとを備え、ネットワークを介して、それぞれ、作業手順を記述したシナリオを使用した作業と前記シナリオを使用しない作業との少なくとも一方の作業を少なくとも一つ実行する、複数の拠点のコンピュータに、何れかの拠点のコンピュータで使用されている前記シナリオの導入を提案するシナリオ提案装置が実行するシナリオ提案方法であって、
     前記プロセッサが、前記ネットワークを介して前記複数の拠点の前記コンピュータから、前記コンピュータに対する操作の操作ログを収集し、前記収集した前記操作ログを前記メモリに記憶させることと、
     前記プロセッサが、前記メモリに記憶された前記操作ログを分割及び分類して、作業単位の操作ログである作業操作ログを生成し、前記生成した作業操作ログを前記メモリに記憶させることと、
     前記プロセッサが、前記ネットワークを介して前記複数の拠点のコンピュータから、各拠点に導入されている前記シナリオを収集し、前記収集した前記シナリオを前記メモリに記憶させることと、
     前記プロセッサが、前記メモリに記憶された前記作業操作ログの内、前記メモリに記憶された前記シナリオとの一致度が一定値以上となる作業操作ログの作業を実行する拠点の前記コンピュータへ、前記ネットワークを介して、前記シナリオの導入提案を送信することと、
     を含むシナリオ提案方法。
    A scenario proposal method is executed by a scenario proposal device, which comprises a processor and a memory, and proposes to computers at a plurality of bases, each of which executes at least one task using a scenario describing a work procedure and at least one task not using the scenario, via a network, introduction of a scenario used in a computer at one of the bases, the scenario proposal device comprising:
    The processor collects operation logs of operations performed on the computers from the computers at the plurality of bases via the network, and stores the collected operation logs in the memory;
    The processor divides and classifies the operation log stored in the memory to generate a work operation log which is an operation log for each task, and stores the generated work operation log in the memory;
    the processor collects the scenarios introduced at each of the plurality of base locations from computers at the plurality of base locations via the network, and stores the collected scenarios in the memory;
    The processor transmits, via the network, a proposal to introduce the scenario to the computer at a base that executes work of a work operation log that has a degree of coincidence with the scenario stored in the memory equal to or greater than a certain value among the work operation logs stored in the memory;
    A scenario suggestion method including:
  8.  請求項1に記載のシナリオ提案装置の各部が行う処理を、前記シナリオ提案装置が備えるプロセッサに実行させるシナリオ提案プログラム。 A scenario proposal program that causes a processor provided in the scenario proposal device to execute the processing performed by each unit of the scenario proposal device described in claim 1.
PCT/JP2022/046413 2022-12-16 2022-12-16 Scenario proposing device, scenario proposing method, and scenario proposing program WO2024127637A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/046413 WO2024127637A1 (en) 2022-12-16 2022-12-16 Scenario proposing device, scenario proposing method, and scenario proposing program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/046413 WO2024127637A1 (en) 2022-12-16 2022-12-16 Scenario proposing device, scenario proposing method, and scenario proposing program

Publications (1)

Publication Number Publication Date
WO2024127637A1 true WO2024127637A1 (en) 2024-06-20

Family

ID=91484671

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/046413 WO2024127637A1 (en) 2022-12-16 2022-12-16 Scenario proposing device, scenario proposing method, and scenario proposing program

Country Status (1)

Country Link
WO (1) WO2024127637A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016212736A (en) * 2015-05-12 2016-12-15 日本電信電話株式会社 Operation assist device, operation assist program, and operation assist method
JP2020119394A (en) * 2019-01-25 2020-08-06 エヌ・ティ・ティ・アドバンステクノロジ株式会社 Scenario execution system, management device, scenario execution management method, and program
JP2021189780A (en) * 2020-05-29 2021-12-13 株式会社エヌ・ティ・ティ・データ Scenario retrieval device, scenario retrieval system, scenario retrieval method, and program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016212736A (en) * 2015-05-12 2016-12-15 日本電信電話株式会社 Operation assist device, operation assist program, and operation assist method
JP2020119394A (en) * 2019-01-25 2020-08-06 エヌ・ティ・ティ・アドバンステクノロジ株式会社 Scenario execution system, management device, scenario execution management method, and program
JP2021189780A (en) * 2020-05-29 2021-12-13 株式会社エヌ・ティ・ティ・データ Scenario retrieval device, scenario retrieval system, scenario retrieval method, and program

Similar Documents

Publication Publication Date Title
CN112118565B (en) Multi-tenant service gray level publishing method, device, computer equipment and storage medium
US11177999B2 (en) Correlating computing network events
CN106970880A (en) A kind of distributed automatization method for testing software and system
CN113867782A (en) Gray scale distribution method and device, computer equipment and storage medium
WO2024127637A1 (en) Scenario proposing device, scenario proposing method, and scenario proposing program
US20200202233A1 (en) Future scenario generating device and method, and computer program
WO2024127638A1 (en) Extended ui proposal apparatus, extended ui proposal method, and extended ui proposal program
US20220365789A1 (en) Storage medium, information processing method, and information processing apparatus
CN110585724A (en) Table data updating method and device in game client
CN114401239B (en) Metadata transmission method, apparatus, computer device and storage medium
WO2022249390A1 (en) Information processing device, information processing system, information processing method and program
CN115269117A (en) Resource creating method and device, computer equipment and storage medium
US20130262487A1 (en) Log management method, log management system, and information processing apparatus
US8836466B2 (en) Monitoring system, device, monitoring method, and monitoring program
CN114143079A (en) Verification device and method for packet filtering strategy
JP5353427B2 (en) Image processing apparatus, program, and image processing system
CN114968491B (en) Virtual resource testing method and device, electronic equipment and storage medium
JP5387827B2 (en) Network management device, network management system, network management method, and program
US10180830B2 (en) Information processing device, deployment method, and recording medium
CN114090962B (en) Intelligent publishing system and method based on big data
CN117056068B (en) JobEngine task splitting method in ETL
WO2023242908A1 (en) Event information generating device, event information generating method, and event information generating program
CN111913737B (en) Method, device, equipment and storage medium for constructing data service interface
US11061747B2 (en) API coordination device, API coordination method and API coordination program
CN116302213A (en) Flow template management method and electronic equipment