WO2024127637A1 - Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario - Google Patents

Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario 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
English (en)
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/fr
Publication of WO2024127637A1 publication Critical patent/WO2024127637A1/fr

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

Dans un mode de réalisation de la présente invention, un dispositif de proposition de scénario comprend une unité de collecte de journal d'opération, une unité de classification, une unité de collecte de scénario et une unité de proposition. L'unité de collecte de journal d'opération collecte, par l'intermédiaire du réseau, des journaux d'opérations d'opérations sur des ordinateurs à partir d'ordinateurs à une pluralité d'emplacements, chaque ordinateur effectuant une ou plusieurs tâches utilisant un scénario décrivant une procédure de tâche et/ou une ou plusieurs tâches n'utilisant pas un scénario. L'unité de classification divise et classe les journaux d'opération collectés par l'unité de collecte de journal d'opération pour générer des journaux d'opération de tâche, qui sont des journaux d'opération dans des unités de tâches. L'unité de collecte de scénario collecte, à partir des ordinateurs à une pluralité d'emplacements par l'intermédiaire du réseau, des scénarios adoptés à chaque emplacement. L'unité de proposition transmet, par l'intermédiaire du réseau, une proposition d'adoption de scénario à un ordinateur à un emplacement qui exécute les tâches de journaux d'opération de tâche pour lesquels le degré de correspondance avec un scénario collecté par l'unité de collecte de scénario est une certaine valeur ou plus parmi les journaux d'opération de tâche générés par l'unité de classification.
PCT/JP2022/046413 2022-12-16 2022-12-16 Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario WO2024127637A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/046413 WO2024127637A1 (fr) 2022-12-16 2022-12-16 Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/046413 WO2024127637A1 (fr) 2022-12-16 2022-12-16 Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario

Publications (1)

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

Family

ID=91484671

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/046413 WO2024127637A1 (fr) 2022-12-16 2022-12-16 Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario

Country Status (1)

Country Link
WO (1) WO2024127637A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016212736A (ja) * 2015-05-12 2016-12-15 日本電信電話株式会社 操作支援装置、操作支援プログラムおよび操作支援方法
JP2020119394A (ja) * 2019-01-25 2020-08-06 エヌ・ティ・ティ・アドバンステクノロジ株式会社 シナリオ実行システム、管理装置、シナリオ実行管理方法及びプログラム
JP2021189780A (ja) * 2020-05-29 2021-12-13 株式会社エヌ・ティ・ティ・データ シナリオ検索装置、シナリオ検索システム、シナリオ検索方法、及びプログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016212736A (ja) * 2015-05-12 2016-12-15 日本電信電話株式会社 操作支援装置、操作支援プログラムおよび操作支援方法
JP2020119394A (ja) * 2019-01-25 2020-08-06 エヌ・ティ・ティ・アドバンステクノロジ株式会社 シナリオ実行システム、管理装置、シナリオ実行管理方法及びプログラム
JP2021189780A (ja) * 2020-05-29 2021-12-13 株式会社エヌ・ティ・ティ・データ シナリオ検索装置、シナリオ検索システム、シナリオ検索方法、及びプログラム

Similar Documents

Publication Publication Date Title
CN112118565B (zh) 多租户服务灰度发布方法、装置、计算机设备和存储介质
US11177999B2 (en) Correlating computing network events
CN106970880A (zh) 一种分布式自动化软件测试方法及系统
CN113867782A (zh) 灰度发布方法、装置、计算机设备和存储介质
WO2024127637A1 (fr) Dispositif de proposition de scénario, procédé de proposition de scénario et programme de proposition de scénario
US20200202233A1 (en) Future scenario generating device and method, and computer program
WO2024127638A1 (fr) Appareil de proposition d'interface ui étendue, procédé de proposition d'interface ui étendue et programme de proposition d'interface ui étendue
US20220365789A1 (en) Storage medium, information processing method, and information processing apparatus
CN110585724A (zh) 游戏客户端中的表格数据更新方法、装置
CN114401239B (zh) 元数据传输方法、装置、计算机设备和存储介质
WO2022249390A1 (fr) Dispositif de traitement d'informations, système de traitement d'informations, procédé de traitement d'informations et programme
CN115269117A (zh) 一种资源创建方法、装置、计算机设备及存储介质
US20130262487A1 (en) Log management method, log management system, and information processing apparatus
US8836466B2 (en) Monitoring system, device, monitoring method, and monitoring program
CN114143079A (zh) 包过滤策略的验证装置及方法
JP5353427B2 (ja) 画像処理装置、プログラム及び画像処理システム
CN114968491B (zh) 虚拟资源测试方法、装置、电子设备及存储介质
JP5387827B2 (ja) ネットワーク管理装置、ネットワーク管理システム、ネットワーク管理方法、及びプログラム
US10180830B2 (en) Information processing device, deployment method, and recording medium
CN114090962B (zh) 一种基于大数据的智能出版系统及方法
CN117056068B (zh) ETL中JobEngine任务拆分方法
WO2023242908A1 (fr) Dispositif, procédé et programme de génération d'informations sur un événement
CN111913737B (zh) 一种数据服务接口的构建方法、装置、设备及存储介质
US11061747B2 (en) API coordination device, API coordination method and API coordination program
CN116302213A (zh) 流程模板管理方法及电子设备