JP7171458B2 - Scenario execution system, management device, scenario execution management method and program - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Law 1. Website (1) Address https://www. ntt-at. co. jp/news/2018/detail/release180627. html (2) Posting date of the website June 27, 2018 2. Meeting (explanatory meeting) (1) Meeting name: WinActor agency briefing meeting (2) Date: September 14, 2018 3. Meeting (Conference) (1) Meeting name: WinActor User Conference (Tokyo) (2) Date: October 10, 2018 4. Website (1) Address https://www. ntt-at. co. jp/news/2018/detail/release181023-2. html (2) Posting date of the website October 23, 2018 5. Meeting (Exhibition) (1) Name of Meeting: AI/Business Automation Exhibition [Autumn] (2) Date: October 24, 2018 to October 26, 2018 6. Meeting (conference) (1) Meeting name: WinActor User Conference (Osaka) (2) Date: November 6, 2018 7. Meeting (seminar) (1) Name of meeting RPA introduction case study seminar (Tokyo) (2) Date November 14, 2018 8. Meeting (forum) (1) Meeting name NTT R&D Forum 2018 (Autumn) (2) Date November 28, 2018 to November 30, 2018 9. Meeting (seminar) (1) Meeting name: RPA introduction support seminar (Osaka) (2) Date: November 28, 2018 10. Meeting (Seminar) (1) Name of Meeting: “WinActor Manager on Cloud” Introduction Seminar (2) Date: December 5, 2018 11. Meeting (Conference) (1) Meeting name “Licensing Live! Japan 2018” (2) Date December 7, 2018 12. Meeting (conference) (1) Meeting name: WinActor User Conference (Nagoya) (2) Date: December 7, 2018 13. Website (1) Address https://winactor. biz/product/manageroncloud. html (2) Posting date of website December 17, 2018 14. Sales (Delivery) (1) Seller Brain Gate Co., Ltd. (2) Sales date January 7, 2019

The present invention relates to a scenario execution system, a management device, a scenario execution management method, and a program.

RPA (Robotic Process Automation) is a technology capable of automatically executing routine work that has been done manually using an information processing device such as a PC (Personal Computer). For example, a scenario describing a work procedure is created (see, for example, Patent Document 1), and a PC executes the scenario to reproduce the work previously performed manually (see, for example, Patent Document 2). RPA can also reduce time costs, human costs, and work errors.

Japanese Patent No. 5026451 Japanese Patent No. 4883638

There have been requests from companies and organizations to manage the execution of scenarios, such as the execution time of scenarios and the information processing devices that execute the scenarios, in order to improve the efficiency of operations as a whole.

In view of the above circumstances, it is an object of the present invention to provide a scenario execution system, a management device, a scenario execution management method, and a program capable of managing scenario execution in an information processing device.

One aspect of the present invention is a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device, wherein the administrator terminal includes a scenario, which is data indicating a processing procedure, and the scenario for executing the scenario. a scenario registration unit for registering, in the management apparatus, scenario information indicating the attributes of the execution terminal; and a schedule registration unit for registering schedule information indicating execution timing of the scenario in the management apparatus. a notification unit for notifying the management device of the state of the terminal at predetermined time intervals; an instruction reception unit for receiving the scenario and the scenario execution instruction from the management device; a scenario execution unit for executing a scenario; and an execution result notification unit for notifying the management device of execution results of the scenario by the scenario execution unit. a storage unit for storing the scenario information and the schedule information received from the administrator terminal in the storage unit; and state management information indicating the state notified from the scenario execution terminal to the a state management unit that writes to a storage unit; and among the scenario execution terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information at the execution timing of the scenario indicated by the schedule information. selects the scenario execution terminal whose state management information indicates that the scenario can be executed as a task allocation destination, and transmits the scenario and the scenario execution instruction to the selected task allocation destination. and an execution result receiving unit for receiving the execution result of the scenario from the scenario execution terminal.

One aspect of the present invention is the scenario execution system described above, wherein the scenario execution terminal further includes a scenario execution permitting unit that controls whether or not execution of a scenario other than the scenario received from the management device is permitted. Prepare.

One aspect of the present invention is the scenario execution system described above, wherein the management device is connected to the administrator terminal and the scenario execution terminal of each of a plurality of clients, the scenario management unit, the state management unit and the The processing of the task management unit is executed by a container that is an execution environment for the processing divided for each client, each client has the storage unit, and the container corresponds to the same client as the container. is accessible to the storage unit for

One aspect of the present invention is the scenario execution system described above, wherein the management device has an application program interface for receiving the schedule information from a terminal implementing arbitrary functions instead of the administrator terminal. Then, the terminal generates the schedule information using information obtained by executing any of the functions, and transmits the generated schedule information to the management device using the application program interface.

According to one aspect of the present invention, there is provided a storage unit that stores terminal management information indicating attributes of a scenario execution terminal, a scenario that is data indicating a processing procedure, and scenario information that indicates attributes of the scenario execution terminal that executes the scenario. and a scenario management unit that receives schedule information indicating execution timing of the scenario from the administrator terminal and registers it in the storage unit; a state management unit that writes state management information indicating a state into the storage unit; and at the execution timing of the scenario indicated by the schedule information, the attribute set in the scenario information of the scenario is set in the terminal management information. among the scenario execution terminals, the scenario execution terminal indicated by the state management information that the scenario can be executed is selected as a task allocation destination, and the selected task allocation destination is the scenario execution terminal. and a scenario execution instruction; and an execution result reception section for receiving the execution result of the scenario from the scenario execution terminal.

An aspect of the present invention is the management device described above, wherein the attribute is any of an organization to which the scenario execution terminal belongs, a function possessed by the scenario execution terminal, and an execution environment of the function in the scenario execution terminal. including at least

An aspect of the present invention is the management device described above, wherein the status notified from the scenario execution terminal to which the task is assigned includes information on the execution status of the scenario.

An aspect of the present invention is the management device described above, further comprising a statistics calculation unit that calculates statistics regarding the state of the scenario execution terminal.

An aspect of the present invention is the management apparatus described above, wherein the storage unit further stores managed object information indicating the scenario execution terminals to be managed by an administrator, and the scenario information includes administrator information. wherein, at the execution timing of the scenario indicated by the schedule information, the attribute set in the scenario information of the scenario is set in the terminal management information and included in the scenario information. Among the scenario execution terminals indicated by the managed object information that they are managed by the administrator indicated by the information, the scenario execution terminals indicated by the state management information that a scenario can be executed. as the task assignee.

An aspect of the present invention is the management device described above, wherein the scenario information includes information specifying other scenario information in which the scenario before update is set.

One aspect of the present invention is a scenario execution management method in a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device, wherein the administrator terminal is a scenario that is data indicating a processing procedure; a scenario registration step of registering, in the management device, scenario information indicating the attributes of the scenario execution terminal that executes the scenario; a schedule registration step of registering, in the management device, schedule information indicating execution timing of the scenario; a notification step in which the terminal notifies the management device of its own state at predetermined intervals; an instruction reception step in which the terminal receives the scenario and the scenario execution instruction from the management device; and in response to receiving the scenario execution instruction, a scenario execution step of executing the received scenario; an execution result notification step of notifying the management apparatus of execution results of the scenario by the scenario execution step; and terminal management in which the management apparatus indicates attributes of the scenario execution terminal. a scenario management step of registering the scenario information and the schedule information received from the administrator terminal in a storage unit for storing information; and storing state management information indicating the state notified from the scenario execution terminal in the storage unit. and at the execution timing of the scenario indicated by the schedule information, among the scenario execution terminals for which the attributes set in the scenario information of the scenario are set in the terminal management information, the state A task assignment that selects the scenario execution terminal whose management information indicates that the scenario can be executed as a task assignment destination, and transmits the scenario and the scenario execution instruction to the selected task assignment destination. and an execution result receiving step of receiving the execution result of the scenario from the scenario execution terminal.

One aspect of the present invention is a scenario execution management method in a management device of a scenario execution system having a manager terminal, a scenario execution terminal, and a management device, comprising a scenario, which is data indicating a processing procedure, and executing the scenario. A storage unit for receiving, from the manager terminal, scenario information indicating the attributes of the scenario execution terminal to be executed, and schedule information indicating the execution timing of the scenario, and storing terminal management information indicating the attributes of the scenario execution terminal. a state management step of receiving notification of a state from the scenario execution terminal at predetermined time intervals and writing state management information indicating the notified state into the storage unit; At the execution timing of the scenario, among the scenario executing terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information, the state management information indicates that the scenario can be executed. a task management step of selecting the scenario execution terminal indicated as a task allocation destination, transmitting the scenario and a scenario execution instruction to the selected task allocation destination; and executing the scenario from the scenario execution terminal. and an execution result receiving step for receiving the scenario execution management method.

One aspect of the present invention is a program for causing a computer to function as the management apparatus described above.

According to the present invention, it is possible to manage execution of scenarios in an information processing apparatus.

1 is a configuration diagram of a scenario execution system according to one embodiment of the present invention; FIG. It is a functional block diagram which shows the structure of the management apparatus by the same embodiment. It is a functional block diagram which shows the structure of the administrator terminal by the same embodiment. 4 is a functional block diagram showing the configuration of a scenario execution terminal according to the same embodiment; FIG. It is a figure which shows the example of the administrator information by the same embodiment. It is a figure which shows the example of the terminal management information by the same embodiment. FIG. 5 is a diagram showing an example of scenario information according to the same embodiment; It is a figure which shows the example of the schedule information by the same embodiment. It is a figure which shows the example of the state management information by the same embodiment. It is a figure which shows the example of the log data by the same embodiment. FIG. 4 is a diagram showing sequences of scenario registration processing and schedule registration processing in the scenario execution system according to the same embodiment; FIG. 4 is a diagram showing the sequence of task allocation processing in the scenario execution system according to the same embodiment; FIG. 10 is a diagram showing an example of a scenario new registration screen according to the same embodiment; It is a figure which shows the example of the scenario update screen by the same embodiment. FIG. 10 is a diagram showing an example of a scenario history display screen according to the same embodiment; It is a figure which shows the example of the schedule registration screen by the same embodiment. It is a figure which shows the example of the dashboard screen by the same embodiment. It is a figure which shows the structure of the management apparatus using the public cloud by the same embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a configuration diagram of a scenario execution system 1 according to one embodiment of the present invention. A scenario execution system 1 includes a management device 2 , an administrator terminal 3 , and a scenario execution terminal 4 . The management device 2 is connected to the administrator terminal 3 and the scenario execution terminal 4 of the client α via a network 7 such as the Internet. The management device 2 further manages each client (not shown) such as the administrator terminal 3 and the scenario execution terminal 4 of the client β, the administrator terminal 3 and the scenario execution terminal 4 of the client γ, . . . It is connected to the user terminal 3 and the scenario execution terminal 4 . For simplicity, the functions and operations of the scenario execution system 1 will be described below using one client α as an example. The operations and functions of the scenario execution system 1 are the same for each of the other clients β, γ, .

The client α has one or more administrator terminals 3 and one or more scenario execution terminals 4 . The administrator terminal 3 and scenario execution terminal 4 are, for example, PCs. A single PC may operate as the administrator terminal 3 and the scenario execution terminal 4 . The administrator terminal 3 is operated by, for example, an administrator of the client α. The scenario execution terminal 4 executes an RPA (Robotic Process Automation) scenario generated by the administrator terminal 3 and instructed to execute. The scenario execution terminals 4 can be divided into groups according to the organization of the client α. In the figure, Group A is the personnel department, Group B is the accounting department, and Group C is the general affairs department. Depending on the group to which the administrator who operates the administrator terminal 3 belongs, it is possible to limit the groups that can create scenarios and give execution instructions.

FIG. 2 is a functional block diagram showing the configuration of the management device 2. As shown in FIG. The management device 2 is implemented by, for example, one or more information processing devices (for example, computer servers) on the cloud. When the management device 2 is implemented using a plurality of information processing devices that are communicably connected via the network 7, each functional unit included in the management device 2 is distributed and implemented in the plurality of information processing devices. may be It is possible to arbitrarily decide which information processing device implements each functional unit of the management device 2 . Also, the same functional unit may be realized by a plurality of information processing apparatuses.

The management device 2 has a communication section 21 , a distribution section 22 , a processing section 23 and a storage section 24 . The communication unit 21 transmits and receives data to and from the administrator terminal 3 and the scenario execution terminal 4 via the network 7 . The distribution unit 22 distributes accesses from the administrator terminal 3 and the scenario execution terminal 4 to the container processing units 23 corresponding to the clients. The processing unit 23 is implemented in a different container for each client. The storage unit 24 is implemented using a storage area that differs for each client, or is implemented in a database device that differs for each client.

The storage unit 24 stores various types of information such as administrator information, terminal management information, scenario information, schedule information, state management information, log data, scenario execution results, and the number of simultaneous use licenses.

The administrator information includes identification information and authority of each administrator, and information on the scenario execution terminals 4 to be managed. The administrator's identification information may be, for example, an ID given to the administrator, an address of the administrator's terminal 3, or the like. Privileges indicate administrative functions that an administrator can use. The scenario execution terminal 4 to be managed can be indicated by the group (organization) to which the administrator belongs. For example, the manager of group A (personnel department) manages the scenario execution terminals 4 of group A (personnel department), and the manager of group D (information system department) manages groups A, B, and C (personnel department). , accounting department, and general affairs department) are managed. Note that the management target may be indicated by identification information, attributes, groups, etc. of the scenario execution terminal 4 . Note that one administrator may belong to a plurality of groups.

The terminal management information includes identification information, license expiration date, address, and attribute information of the scenario execution terminal 4 . The identification information of the scenario execution terminal 4 is an ID assigned to a device capable of executing a function related to scenario execution (hereinafter referred to as "scenario execution function"). Identification information may be used. The license expiration date indicates the expiration date of the license that permits the scenario execution terminal 4 to use the scenario execution function. The attributes indicate the group (organization) to which the scenario execution terminal 4 belongs, the function that the scenario execution terminal 4 has, the version of the application that executes the function, the execution environment of the function in the scenario execution terminal 4, and the like. Note that one scenario execution terminal 4 may belong to two or more organizations. Also, the functions possessed by the scenario execution terminal 4 can be indicated by, for example, an OS (Operation System) name or the name and type of an application installed in the scenario execution terminal 4 . Version information may be added to the OS name and application name.

The scenario information includes identification information of the scenario information, a name of the scenario, a file describing the scenario, update information, attributes of the scenario execution terminal 4 that executes the scenario, and identification information of the administrator who created the scenario. A scenario is data indicating a processing procedure to be executed by the scenario execution terminal 4 . The update information includes the date and time when the scenario was created and information specifying other scenario information in which the scenario before update is set. Further, the scenario information includes the data format of input parameters during scenario execution and the data format of output parameters at the end of scenario execution.

The schedule information includes identification information of the schedule information, identification information of the scenario to be executed by the scenario execution terminal 4, execution timing, information of the scenario execution terminal 4 to be executed, and identification information of the administrator who created the schedule information. In addition, the schedule information includes values for input parameters.

The state management information indicates the state of the scenario execution terminal 4 at each time. The log data indicates an event that occurred in the administrator terminal 3 or the scenario execution terminal 4 and the date and time of the occurrence. Events include administrator login/logout, scenario information registration/update, schedule information registration/update/deletion, enablement/disablement, task execution opportunity and execution results, and the like. The number of simultaneous use licenses is set when the client α uses a floating license, and indicates the number of scenario execution terminals 4 that can simultaneously execute tasks. A floating license is a service that determines the upper limit of the number of licensed scenario execution terminals 4 that simultaneously execute a scenario.

The processing unit 23 includes an information registration unit 231, a scenario management unit 232, a schedule management unit 233, a state management unit 234, a task management unit 235, an execution result reception unit 236, a log generation unit 237, and a management information provision unit 238. , and a storage control unit 239 .

The information registration unit 231 registers, updates, and deletes administrator information, terminal management information, and the like. The scenario management unit 232 registers and updates scenario information. The schedule management unit 233 registers, updates, and deletes schedule information. The state management unit 234 receives a state notification from the scenario execution terminal 4 at predetermined time intervals, generates state management information indicating the notified state, and writes it to the storage unit 24 .

At the execution timing of the scenario indicated by the schedule information, the task management unit 235 checks the state management information among the scenario execution terminals 4 whose terminal management information indicates that they are the execution terminals set in the scenario information of the scenario. Scenario execution terminals 4 shown in , which are ready to execute the scenario, are selected as task assignment destinations. The task management unit 235 transmits the file describing the scenario and the scenario execution instruction to the scenario execution terminal 4 to which the selected task is assigned.

The execution result receiving unit 236 receives the scenario execution result from the scenario execution terminal 4 and registers the execution result in the storage unit 24 . The log generation unit 237 detects the occurrence of events at the administrator terminal 3 and the scenario execution terminal 4 , generates log data of the detected events, and registers the log data in the storage unit 24 . The management information providing unit 238 is an example of a statistics calculating unit that calculates statistics regarding the state of the scenario execution terminal 4 and the task state. The management information providing unit 238 transmits screen data showing the result of statistical calculation to the administrator terminal 3 for display. The storage control unit 239 controls access to the storage unit 24 corresponding to the same client as the processing unit 23 . That is, the processing unit 23 can access the storage unit 24 corresponding to the client via the storage control unit 239 .

FIG. 3 is a functional block diagram showing the configuration of the administrator terminal 3. As shown in FIG. The administrator terminal 3 includes a control section 31 , a communication section 32 , a storage section 33 , a processing section 34 , an input section 35 and a display section 36 . The control unit 31 includes a CPU and various memories, and controls each unit. The communication unit 32 transmits and receives data to and from the management device 2 via the network 7 . The storage unit 33 stores various information such as created scenarios.

The processing unit 34 includes a scenario creation unit 341 , a scenario registration unit 342 , a schedule registration unit 343 and a display control unit 344 . The scenario creating unit 341 creates a scenario in response to the administrator's input from the input unit 35 . The scenario registration unit 342 receives the administrator's input from the input unit 35 and transmits scenario information in which the file of the created scenario is set to the management device 2 . The schedule registration unit 343 receives the administrator's input from the input unit 35 , generates schedule information, and transmits the schedule information to the management device 2 . The display control unit 344 displays the screen data received from the management device 2 on the display unit 36 .

The input unit 35 is configured using existing input devices such as a keyboard, pointing device (mouse, tablet, etc.), buttons, touch panel, and the like. The input unit 35 is operated by the user when inputting user instructions to the administrator terminal 3 . The display unit 36 is an image display device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, an organic EL (Electro Luminescence) display, or the like.

FIG. 4 is a functional block diagram showing the configuration of the scenario execution terminal 4. As shown in FIG. The scenario execution terminal 4 includes a control section 41 , a communication section 42 , a storage section 43 , a processing section 44 , an input section 45 and a display section 46 .

The control unit 41 includes a CPU (central processing unit) and various memories, and controls each unit. The communication unit 42 transmits and receives data to and from the management device 2 via the network 7 . The storage unit 43 stores various types of information such as license information, setting information, scenarios received from the management device 2, and scenario execution results. The license information stores license information for enabling the scenario execution function. The setting information indicates a setting as to whether or not execution of a scenario other than the scenario received from the management device 2 is permitted.

The processing section 44 includes a scenario execution function section 440 and a function X execution section 446 . The scenario execution function unit 440 performs processing related to the scenario execution function. Scenario execution function unit 440 includes notification unit 441 , instruction reception unit 442 , scenario execution unit 443 , execution result notification unit 444 , and scenario execution permission unit 445 .

The notification unit 441 notifies the management device 2 of the state of the own terminal at intervals of several tens of seconds to several minutes, such as every 30 seconds. The instruction receiving unit 442 receives a scenario and a scenario execution instruction from the management device 2 . Scenario execution unit 443 executes a scenario in response to receiving a scenario execution instruction. The execution result notification unit 444 notifies the management device 2 of the scenario execution result by the scenario execution unit 443 . The scenario execution permission unit 445 controls whether execution of scenarios other than the scenario received from the management device 2 is permitted based on the setting information stored in the storage unit 43 .

A function X execution unit 446 executes a function X application. Function X is a function that can be used to execute a scenario, and can be any function implemented in a PC, such as e-mail transmission/reception, spreadsheet calculation, document editing, postcard creation, graphic drawing, and web browser. In the figure, a function X execution unit 446 (X=A, B, C) that executes applications of functions A, B, and C is divided into a function A execution unit 446a, a function B execution unit 446b, and a function C execution unit 446c. described.

The input unit 45 is configured using existing input devices such as a keyboard, pointing device, and touch panel. The input unit 45 is operated by the user when inputting user instructions to the scenario execution terminal 4 . The display unit 46 is an image display device such as a CRT display, liquid crystal display, or organic EL display.

Next, an example of each information stored in the storage unit 24 of the management device 2 will be described.
FIG. 5 is a diagram showing an example of administrator information. The administrator information includes user ID, user name, affiliation and authority information. A user ID is identification information that identifies an administrator. Username is the name of the administrator. Affiliation indicates the organization to which the administrator belongs. The organization may be hierarchical. Also, one administrator may belong to two or more organizations. The affiliation is used by the administrator as management target information indicating the scenario execution terminal 4 to be managed. In other words, the manager's affiliation indicates which scenario execution terminal 4 he or she belongs to. The authority indicates, for example, whether or not scenario registration, schedule registration, and status display viewing are permitted.

FIG. 6 is a diagram showing an example of terminal management information. The terminal management information includes scenario execution function ID, license expiration date, PC name, IP address, and attribute information. The scenario execution function ID is identification information assigned to each scenario execution terminal 4 for the scenario execution function. The license expiration date indicates the expiration date of the license of the application software that enables the scenario execution terminal 4 to implement the scenario execution function. The PC name is the name of the PC used as the scenario execution terminal 4 . The IP address is the IP address of the scenario execution terminal 4 . The attributes indicate OS name, screen size, affiliation, function tag, and the like. The OS name is the name of the OS installed in the scenario execution terminal 4. FIG. The screen size is the size of the display (display unit 46) of the scenario execution terminal 4. FIG. Affiliation indicates the organization to which the scenario execution terminal 4 belongs. A function tag indicates a function that the scenario execution terminal 4 has. The function can be the name, type, version, etc. of an application installed in the scenario execution terminal 4 (for example, accounting software, mail sending/receiving software, etc.).

FIG. 7 is a diagram showing an example of scenario information. Scenario information includes information such as scenario ID, creator, parent scenario ID, scenario name, scenario file, input parameter, output parameter, timeout, attribute, memo, scenario tag, modification content, creation date and time, and update date and time. . A scenario ID is information that uniquely identifies a scenario. Creator indicates the administrator who created the scenario information, and for example, a user ID is used. The parent scenario ID indicates the scenario ID of the original scenario when the scenario is created by updating an already generated scenario. The scenario name indicates the name of the scenario.

A scenario file indicates a file describing a scenario or a storage location of the file in the storage unit 24 . The input parameter defines the data format of the parameter to be input when executing the scenario. The output parameter defines the data format of the parameter in which the scenario execution result is set. The timeout indicates the time to wait until it is determined that the scenario execution is an error when the execution of the scenario stops halfway. The attribute indicates the attribute of the scenario execution terminal 4 on which the scenario is to be executed. Attributes are indicated by OS name, screen size, affiliation, function tag, and the like. The memo is an explanation or the like regarding the scenario. A scenario tag is a tag given to a scenario. Modified content indicates what has been changed from the parent scenario. The date and time of generation indicates the date and time of generation of the scenario information. The update date and time indicates the update date and time of the scenario information.

FIG. 8 is a diagram showing an example of schedule information. The schedule information includes schedule ID, creator, schedule name, affiliation, execution scenario, execution terminal, input parameter values, execution timing, and information on operation when an abnormality occurs. The schedule ID is information that uniquely identifies schedule information. Creator indicates the administrator who created the scenario information, and for example, a user ID is used. The affiliation indicates the affiliation of the schedule information, and the scenario execution terminal 4 having the same affiliation can be caused to execute the scenario. The execution scenario is the scenario ID of the scenario to be executed.

The execution terminal indicates the scenario execution terminal 4 on which the scenario is to be executed (hereinafter also referred to as "execution target terminal") and the number of execution terminals. The number of executions is limited to the number of licenses for concurrent use. If the execution target terminal is selected based on the attributes set in the scenario information, the execution terminal need not be set. When the execution target terminal is selected according to a predetermined condition in addition to the attribute set in the scenario information, the condition is set in the execution terminal. Attributes of the scenario execution terminal 4 (affiliation or function tag), scenario execution function ID, PC name, status, etc. can be used for the execution terminal. If attributes, status, etc. are set without specifying a specific scenario execution terminal 4 such as a scenario execution function ID or PC name, the number of scenario execution terminals 4 to be executed is selected from among the scenario execution terminals 4 that satisfy the attributes. can run the scenario.

The input parameter value indicates the parameter value to be input to the scenario execution terminal 4 when the scenario is executed. The execution timing indicates the timing for executing the scenario. The execution timing is indicated by immediate, a predetermined date and time, every day and time, a predetermined day and time of every month, a predetermined day and time of every week, the end of the month or a predetermined day before and after the end of the month, and the like. The operation at the time of occurrence of an abnormality indicates an operation to be performed when an abnormality occurs while the scenario execution terminal 4 is executing the scenario.

FIG. 9 is a diagram showing an example of state management information. The state management information includes scenario execution function ID, time, scenario execution function state, and task state information. The scenario execution function state indicates the state of the scenario execution function specified by the scenario execution function ID. The states include stopping, restarting, starting, license expiration, starting, user operation, scenario execution, scenario execution abnormal stop, preparation for next scenario execution, and communication interruption. The suspended state is a state in which an instruction to suspend the scenario execution function has been issued or the scenario execution function is in the process of being suspended. During restart, the restart is instructed to the scenario execution function. During launching is the state in which the scenario execution function is being launched. License revocation is a state in which the license for the scenario execution function is revoked. During startup, the scenario execution function has started normally and is waiting for execution of the scenario. During user operation, the scenario execution function is recording the scenario, and the next scenario cannot be executed until this state changes. During scenario execution is a state in which the scenario for which the scenario execution function is instructed is being executed. During scenario execution abnormal stop, the scenario execution function is in a state of being stopped due to some problem occurring during execution of the scenario for which the scenario execution function is instructed. During the preparation for execution of the next scenario, the scenario execution function is in a state of deleting or rewriting data so that the next scenario can be executed. Communication interruption is a state in which notification with the scenario execution function is interrupted.

Task statuses include waiting, processing, normal termination, suspension, suspension, abnormal termination, and abnormal termination. Waiting is a state of waiting until a task is assigned to the scenario execution function. During processing, the task is assigned to the scenario execution function and is being executed. "Normal end" is a state in which task execution has ended normally. During suspension is a state in which an instruction to suspend execution of the task has been issued. Suspend is a state in which an instruction to suspend the execution of a task being executed has been made. Abnormal stop is a state in which an error occurred during task execution and the task stopped. Abnormal end is a state in which an error occurred during task execution and the task ended.

FIG. 10 is a diagram showing an example of log data. The log data includes information on time, affiliation, and occurrence event. The affiliation indicates the affiliation of the administrator or the scenario execution function who caused the event or caused the event. Occurrence event indicates an event that has occurred. The occurrence event can include information indicating the location where the event occurred and the location that caused the event, such as the administrator name and the scenario execution function ID.

Next, the operation of the scenario execution system 1 will be explained. First, the information registration unit 231 of the management device 2 registers administrator information and terminal management information in the storage unit 24 . The information registration unit 231 may acquire and set a part of the terminal management information from the scenario execution terminal 4 .

FIG. 11 is a diagram showing sequences of scenario registration processing and schedule registration processing in the scenario execution system 1. FIG. The scenario creation unit 341 of the administrator terminal 3 creates a scenario based on the instructions input by the administrator through the input unit 35 (step S101). When updating a scenario that has already been created, the administrator terminal 3 acquires from the management device 2 the scenario information of the scenario to be updated (parent scenario) or part of the information. The administrator terminal 3 corrects the acquired scenario information or part of the information based on the instructions input by the administrator through the input unit 35 .

After creating the scenario, the scenario registration unit 342 generates scenario information including a scenario file describing the created scenario based on the information input by the administrator through the input unit 35, and uploads it to the management device 2 (step S102). When the scenario is updated, information that has not been changed from the scenario information before updating may be set in the schedule information to be uploaded. Also, the parent scenario ID is set to the scenario ID of the scenario before updating.

If the administrator information specified by the user ID of the administrator received from the administrator terminal 3 is set to allow scenario creation, the scenario management unit 232 of the management device 2 updates the scenario information received from the administrator terminal 3. It is written in the storage unit 24 (step S103). Note that the scenario ID, the user ID indicating the creator, the generation date and time, and the update date and time may be set in the scenario management section 232 without being transmitted from the administrator terminal 3 . Further, the scenario management section 232 may set the storage location of the scenario file in the storage section 24 for the scenario file of the scenario information. Also, if the affiliation set in the scenario information is outside the scope of management based on the affiliation obtained from the administrator information specified by the administrator's user ID, the scenario management unit 232 registers it in the storage unit 24. not performed. Also, the scenario management unit 232 of the management device 2 may divide the scenario information into multiple times and transmit it to the administrator terminal 3 .

The schedule registration unit 343 of the administrator terminal 3 sends a schedule registration request including schedule information describing the timing for executing the scenario registered in the management apparatus 2 according to the instruction input by the administrator through the input unit 35 . (step S104). The scenario ID of the scenario to be executed is set in the execution scenario of the schedule registration request, and information for selecting the scenario execution terminal 4 to execute the scenario is included in the execution terminal.

Note that the administrator terminal 3 may acquire a list of scenario information that matches the search conditions from the management device 2 and set the scenario ID of the scenario information selected from the list as the execution scenario. In this case, the administrator terminal 3 transmits the user ID and search conditions (for example, scenario ID, scenario name, attribute, memo, update date and time, etc.) to the management device 2 . The scenario management unit 232 of the management device 2 identifies the affiliation of the managed object based on the affiliation of the administrator information identified by the user ID, and selects from among the scenario information for which the managed object affiliation is set, Select matching scenario information. The scenario management unit 232 transmits the selected scenario information list to the administrator terminal 3 . The list includes some information extracted from the scenario information, such as scenario IDs, scenario names, attributes, update dates and times. The display control unit 344 of the administrator terminal 3 displays the list on the display unit 36. FIG. The administrator selects the scenario information of the scenario to be executed by the input unit 35 from the displayed list.

The schedule management unit 233 of the management device 2 registers the received schedule information in the storage unit 24 when the administrator information specified by the user ID received from the administrator terminal 3 is set to allow schedule registration (step S105). The schedule ID and the user ID indicating the creator may be set in the schedule management unit 233 without being transmitted from the administrator terminal 3 . If the affiliation set in the schedule information is not subject to management from the affiliation set in the administrator information specified by the administrator's user ID, the schedule management unit 233 registers the schedule information in the storage unit 24. not performed. Also, the schedule management unit 233 of the management device 2 may divide the schedule information into multiple times and transmit it to the administrator terminal 3 .

The schedule management unit 233 may receive an instruction to validate, invalidate, or delete schedule information from the administrator terminal 3 . In this case, a schedule ID specifying schedule information to be validated, invalidated, or deleted is set in the instruction. When the schedule management unit 233 receives a user ID of an administrator whose administrator information indicates that the schedule can be registered and an instruction to activate or deactivate the administrator information, the schedule management unit 233 associates the administrator information with the schedule ID set in the instruction. , the valid or invalid state is written in the storage unit 24 . On the other hand, when the schedule management unit 233 receives a user ID of an administrator whose administrator information indicates that the schedule can be registered and a deletion instruction, the schedule management unit 233 deletes the schedule information of the schedule ID set in the instruction. . Also, the schedule registration request may include an instruction to either validate or invalidate the schedule information. Note that the schedule management unit 233 excludes the affiliation set in the schedule information for which the activation, deactivation, or deletion has been instructed from the affiliation obtained from the administrator information specified by the user ID of the administrator. , the instructed validation, invalidation, or deletion process is not performed.

The administrator terminal 3 obtains a list of schedule information that matches the search conditions from the management device 2, and instructs the schedule ID of the schedule information selected from the list to be validated, invalidated, or deleted. May be set. In this case, the administrator terminal 3 transmits the user ID and search conditions (for example, schedule ID, schedule name, attributes, update date and time, etc.) to the management device 2 . The schedule management unit 233 of the management device 2 identifies the affiliation of the management target based on the affiliation of the administrator information identified by the user ID, and selects the schedule information for which the affiliation of the management target is set according to the search condition. Select matching schedule information. The schedule management unit 233 transmits the selected schedule information and a list of information indicating whether the schedule information is valid or invalid to the administrator terminal 3 . The display control unit 344 of the administrator terminal 3 displays the list on the display unit 36. FIG. The administrator selects the scenario information of the scenario to be executed by the input unit 35 from the displayed list.

FIG. 12 is a diagram showing the sequence of task assignment processing in the scenario execution system 1. As shown in FIG. The notification unit 441 of the scenario execution terminal 4 notifies the management device 2 of the scenario execution function ID of the own terminal and the state of the own terminal (step S201). If the status of the scenario execution function is activation of the scenario execution function, user operation, scenario execution, scenario execution abnormal stop, etc., the notification unit 441 may further notify the task being executed.

The state management unit 234 of the management device 2 generates state management information based on the state notified from the scenario execution terminal 4 that is the source of the state notification (hereinafter referred to as “state notification source terminal”), and stores it in the storage unit 24. Register (step S202). Note that the state management unit 234 generates state management information in which the state is set to communication interruption for scenario execution terminals 4 that do not receive an expected notification or response for a predetermined time or longer, and registers the state management information in the storage unit 24 .

On the other hand, if the number of scenario execution terminals 4 that are currently executing tasks has not reached the number of simultaneous use licenses, or if the client α is not using a floating license, the task management unit 235 sets valid schedule information. Task assignment processing is started at the execution timing specified by the If the task allocation process has started and the task allocation process has not been completed, the task management unit 235 determines whether or not the status notification source terminal is to be assigned a task (step S203). ).

Specifically, first, the task management unit 235 determines whether or not the state of the state notification source terminal is a state in which a task can be assigned, that is, whether or not it is “starting”. When the task management unit 235 determines that the task cannot be assigned, the status notification source terminal is not subject to task assignment.

When the task management unit 235 determines that the state of the state notification source terminal is in a state in which a task can be assigned, the task management unit 235 refers to the terminal management information of the state notification source terminal, and determines the execution terminal of the schedule information and the execution scenario of the schedule information. It is determined whether or not the attribute of the scenario information specified by is satisfied. If the task management unit 235 determines that the condition is satisfied, it determines that the status notification source terminal is to be assigned a task.

When the task management unit 235 determines that the status notification source terminal is to be assigned a task (step S203: YES), the task management unit 235 reads the scenario file, input parameters, output parameters, and timeout from the scenario information specified by the execution scenario of the schedule information. The task management unit 235 sets the read information as a scenario execution instruction, substitutes the input parameter values described in the schedule information for the input parameters, and transmits the result to the status notification source terminal (step S204). When the task assignment to the scenario execution terminal 4 indicated in the execution terminal of the schedule information is completed, the task management section 235 ends the task assignment process.

The scenario execution unit 443 of the scenario execution terminal 4 receives the scenario execution instruction and executes the scenario (step S205). Even after the scenario execution is started, the notification unit 441 periodically notifies the management device 2 of the scenario execution function ID of the own terminal and the state of the own terminal (step S206), and the state management unit 234 of the management device 2 The state management information generated based on the notified state is registered in the storage unit 24 (step S207).

When the scenario execution by the scenario execution unit 443 is completed, the execution result notification unit 444 of the scenario execution terminal 4 sets the execution result in the output parameter and notifies it to the management device 2 (step S208). The execution result receiving unit 236 of the management device 2 receives the execution result and writes it to the storage unit 24 (step S209). The execution result receiving unit 236 reads the execution result from the storage unit 24 and downloads it in response to a request from the administrator terminal 3 .

If the task management unit 235 of the management device 2 determines that the task assignment has not been activated or the status notification source terminal is not the target of task assignment, the scenario assignment determination is terminated.

Next, screens displayed on the administrator terminal 3 by the management device 2 will be described.
FIG. 13 is a diagram showing an example of the new scenario registration screen 81. As shown in FIG. The scenario management unit 232 of the management device 2 generates screen data for the new scenario registration screen 81 and causes the display unit 36 of the administrator terminal 3 to display it. The new scenario registration screen 81 includes a scenario name setting field 811, an affiliation setting field 812, a scenario file file name setting field 813, an input parameter addition button 814, an output parameter addition button 815, a timeout setting field 816, and a memo. It has a setting field 817 , a function tag setting field 818 , a scenario tag setting field 819 , and a new creation button 810 .

A setting field 812 shown in FIG. 8 can set each layer of affiliation represented by three layers. The scenario management unit 232 of the management device 2 displays a list of selectable affiliations according to the affiliation of the administrator of the user ID received from the administrator terminal 3, and sets the selected one in the setting field 812. You may make it When the input parameter addition button 814 is selected, the administrator terminal 3 displays a screen for defining the data format of the input parameter. When the output parameter addition button 815 is selected, the administrator terminal 3 displays a screen for defining the data format of the output parameter. When the new creation button 810 is selected, the scenario registration unit 342 of the administrator terminal 3 uploads the scenario (step S102 in FIG. 11).

FIG. 14 is a diagram showing an example of the scenario update screen 82. As shown in FIG. When updating the scenario information of a scenario that has already been generated, the scenario management unit 232 of the management device 2 updates the scenario update screen 82 using the scenario information of the parent scenario specified by the information received from the administrator terminal 3. Screen data is generated and displayed on the administrator terminal 3. Information set in the scenario information of the parent scenario is displayed by default on the scenario update screen 82, and default values are displayed in the setting fields for updatable information. The scenario update screen 82 includes a scenario name setting field 821, an affiliation setting field 822, a scenario file file name setting field 823, an input parameter setting area 824, an output parameter setting area 825, a timeout setting field 826, and a memo field 826. , a function tag setting field 828, a scenario tag setting field 829, a correction content setting field 830, and an update button 831. After updating the information, when the update button 831 is selected, the scenario registration unit 342 of the administrator terminal 3 uploads the scenario.

FIG. 15 is a diagram showing an example of the scenario history display screen 84. As shown in FIG. The scenario management unit 232 of the management device 2 receives the scenario ID of the scenario information selected from the scenario information list of the search result and the scenario history request from the administrator terminal 3 . The scenario management unit 232 identifies the version of the scenario information of the previous generation whose scenario ID is the parent ID set in the scenario information of the received scenario ID (hereinafter referred to as current scenario information). The scenario management unit 232 similarly repeats the process of specifying the scenario information of the previous version using the parent ID set in the specified scenario information until the scenario information in which the parent ID is not set is obtained. repeat. The scenario management unit 232 identifies scenario information that is one generation newer with the ID of the current scenario information as the parent ID. The scenario management unit 232 repeats the process of identifying a newer version of the scenario information having the ID set in the identified scenario information as the parent ID. The scenario management unit 232 generates a scenario history display screen 84 that lists the current scenario information and some information obtained from the specified scenario information in order of version, and causes the administrator terminal 3 to display the screen.

The scenario history display screen 84 shown in the figure includes a scenario name display area 841 and a scenario information display area 842 . In the scenario information display area 842, information obtained from the specified scenario information is arranged and displayed in version order. In the figure, the date and time of generation, editor, content of correction, and scenario tag are displayed. The editor is obtained from the user name of the administrator information specified by the user ID set as the creator of the scenario information. The current scenario information display area 843 is displayed using a background color indicating that it is the current scenario information. When the scenario management unit 232 receives from the administrator terminal 3 the fact that the selection button has been selected, it causes the administrator terminal 3 to display a scenario information detail screen displaying the details of the scenario information corresponding to the selection button. This scenario information detail screen may have a schedule registration button.

FIG. 16 is a diagram showing an example of the schedule registration screen 85. As shown in FIG. When the administrator terminal 3 selects registered scenario information and requests schedule registration, the schedule management unit 233 of the management device 2 generates screen data for the schedule registration screen 85 using the selected scenario information. , is displayed on the administrator terminal 3. The schedule registration screen 85 includes a schedule name setting field 851, an affiliation setting field 852, a scenario ID display area 853 for selected scenario information, a scenario name display area 854 for selected scenario information, an execution terminal designation button 855, an input It includes a parameter value setting field 856 , an input file specification field 857 , an execution specification button 858 , an operation selection button 859 when an error occurs, and a schedule registration button 850 .

When specifying an execution terminal, an execution terminal specification button 855 is selected to display a screen for inputting the specification of the execution terminal. The input file specification field 857 is a file necessary for scenario execution that is transmitted to the scenario execution terminal 4 when the task management unit 235 of the management device 2 issues a scenario execution instruction. A file can be specified.

The execution designation button 858 is a button for selecting a type such as immediate, date and time designation, daily, weekly, monthly, or end of month. When the date and time designation is selected, a calendar for selecting a date and a setting field for execution time are displayed. If daily is selected, the run time setting fields are displayed, if weekly is selected, the day of the week and run time setting fields are displayed, if monthly is selected, the day and run time setting fields are displayed However, if the end of the month is selected, the number of days before the end of the month and the time setting field are displayed.

After setting the information, when the schedule registration button 850 is selected, the schedule registration unit 343 of the administrator terminal 3 transmits a schedule registration request to the management device 2 (step S104 in FIG. 11).

FIG. 17 is a diagram showing an example of the dashboard screen 86. As shown in FIG. The management information providing unit 238 of the management device 2 receives the management information display request from the display control unit 344 of the administrator terminal 3 . The management information providing unit 238 generates a dashboard screen 86 and displays it on the administrator terminal 3 when the administrator information specified by the user ID received from the administrator terminal 3 is set to permit management information viewing. . The dashboard screen 86 is a screen that displays the status of scenario execution, the number of scenario execution terminals 4 in each status, the number of tasks in each status, statistical information, and the like.

The dashboard screen 86 includes a dashboard icon 861, an abnormal terminal display area 862, an abnormal task display area 863, a display area 864 for the number of scenario execution terminals 4 and the number of tasks, a license information display area 865, and a floating license usage status. display area 866 and a task-in-progress display area 867 .

The dashboard icon 861 is an icon representing normal, warning, or abnormal. The management information providing unit 238 displays an icon indicating normal when there is no scenario execution terminal 4 in the state of communication interruption or scenario execution abnormal stop and no task state abnormally terminated. If there is a scenario execution terminal 4 with communication cutoff, the management information providing unit 238 displays an icon representing a warning, and displays the scenario execution function ID of the scenario execution terminal 4 in the abnormal terminal display area 862 . The management information providing unit 238 displays an icon representing an abnormality when there are one or more scenario execution terminals 4 in the state of communication interruption or abnormal termination of scenario execution, and one or more tasks in the state of abnormal termination. The management information providing unit 238 causes the abnormal terminal display area 862 to display the scenario execution function ID of the scenario execution terminal 4 for which communication is interrupted or the scenario execution is abnormally stopped. Display the scenario name of the task that is set to .

The management information providing unit 238 determines the number of scenario execution terminals 4 to which the scenario execution function ID is assigned (the number of registered terminals), the number of the scenario execution terminals 4 in the active state (the number of active terminals), and the task status. Display area 864 for the number of scenario execution terminals 4 inside (the number of tasks being processed), the number of scenario execution terminals 4 whose task status is waiting (the number of tasks waiting), and the number of tasks that have been executed since startup (total number of tasks). to display.

The management information providing unit 238 causes the license information display area 865 to display various types of license statistical information, such as the number of valid and invalid licenses, in chronological order. The management information providing unit 238 causes the display area 866 to display the usage status of the floating licenses, such as the number of simultaneous usages of the floating licenses. The management information providing unit 238 displays various time-series statistical information regarding tasks, such as the number of tasks in each task state, in the task-in-execution display area 867 .

The management device 2 may provide a RESTful API as an API (Application Program Interface) for cooperating with other system implementation terminals other than the administrator terminal 3 . Terminals with other systems that use RESTful APIs are terminals that implement the functions of other systems that clients arbitrarily decide to use. In the above, the administrator terminal 3 uses the input screen received from the management apparatus 2 to input various information for executing the task, sets the input information to the schedule registration request, and transmits the schedule registration request to the management apparatus 2. is doing. The other-system-implemented terminal generates a schedule registration request using information obtained by executing the functions of the other system it implements, and transmits the generated schedule registration request to the management device 2 using the RESTful API.

For example, the other system-equipped terminal is equipped with a voice recognition system. The voice recognition system accepts an order by the manager's voice, and transmits a schedule registration request to the management device 2 to immediately execute the scenario of ordering work. Alternatively, the other system-equipped terminal is equipped with an email analysis system, and the email analysis system analyzes an email requesting an estimate sent from the administrator, and makes a schedule registration request that causes the management device 2 to execute a scenario for creating an estimate. to send. Further, the other system-equipped terminal may use information obtained by executing the function of the other system that is implemented to transmit a management information display request to the management device 2 using RESTful API. By providing a RESTful API, the management device 2 provides routine management function services such as task execution and monitoring requests using the inputs and functions (applications) of other systems that the client has decided to use. Furthermore, cooperation with other systems and extensibility can be provided.

FIG. 18 is a diagram showing the configuration of the management device 2 using public cloud. The cloud that constitutes the management device 2 is constructed using, for example, web service (AWS) resources provided by Amazon.com. With the configuration shown in the figure, the management device 2 can separate segments for each client and provide security equivalent to that of a virtual private cloud. When receiving an access from the administrator terminal 3 of each client using https, the management device 2 distributes this access to a subnet for each client, and then accesses a container for each client corresponding to the subnet (distribution). equivalent to the function of the section 22). This container (management function container) implementing the processing unit 23 accesses a database (corresponding to the storage unit 24) for each client using RDS (managed relational database service) or the like.

In this way, a server used as the management device 2 is set up in a public cloud service such as AWS, and in the server, the execution environment of the processing unit 23 is isolated for each client by a container. By linking the container with the database of the client, the management device 2 can be implemented by a virtual private cloud for each client.

With the above configuration, the scenario execution system 1 provides the following functions.
(1) File management function: The management device 2 manages files uploaded from the administrator terminal 3 or the scenario execution terminal 4 or downloaded to the administrator terminal 3 or the scenario execution terminal 4 . The management device 2 stores and manages the scenarios and data files to be distributed to the scenario execution terminals 4 and the result files of the execution of tasks by the scenario execution terminals 4 .

(2) Scenario management function: manages scenarios (tasks) to be distributed to the scenario execution terminals 4; Also, set the input/output parameters and timeout time given to the task. For example, an administrator A newly registers a scenario for work A using the administrator terminal 3, and registers it in the management apparatus 2 as version 1 with the date and time of creation added. In addition, the administrator B corrects the scenario of the task B for the second time using the administrator terminal 3 and registers it in the management apparatus 2 . The management device 2 adds the update date and time as version 3 and registers it. Also, if a problem occurs during the execution of the latest version 3 of the scenario of task C corrected by manager C on the scenario execution terminal 4, manager B sends the version 2 schedule information to the management device via the manager terminal 3. Register for 2. As a result, a task of version 2 of the scenario for work C is generated and executed by the scenario execution terminal 4 .

(3) Management execution mode function: By registering in the storage unit 43 of the scenario execution terminal 4 setting information indicating that the execution of scenarios other than the scenario received from the management device 2 is not permitted, the scenario execution terminal 4 can , it is possible to prevent the scenario from being executed except by an instruction from the management device 2 .

(4) Schedule management: The administrator terminal 3 can cause the scenario execution terminal 4 to execute a scenario as a task by registering schedule information in which arbitrary timing is set in the management device 2 . In other words, according to the schedule information received from the administrator terminal 3, the management device 2 allocates a task for causing the scenario execution terminal 4 in the standby state to execute the scenario. It is also possible to set input parameters to be given to the task and task execution triggers. For example, the scenario for task A can be executed at 9:00 every morning, or the scenario for task B can be executed immediately.

(5) Scenario execution function management: manages the state of the scenario execution function of the scenario execution terminal 4, assigns a task to the scenario execution terminal 4 in the standby state, and puts the task on standby if there is no scenario execution terminal 4 in the standby state.

(6) Group control function: The management device 2 can cause a group classified according to the environment (affiliation, function, OS, etc.) of the scenario execution terminal 4 to execute the scenario for each scenario. For example, if the management device 2 uses the mail transmission function for the scenario of task A, the management device 2 can select the scenario execution terminal 4 having the mail transmission function and execute the scenario. Further, when the scenario of task B runs only on a specific OS, the management device 2 can select the scenario execution terminal 4 using that OS and execute the scenario.

(7) Managed object definition machine function: The administrator can define the scope of managed objects. For example, an administrator in charge of the general affairs department can cause the scenario execution terminal 4 of the general affairs department to execute the scenario, but cannot cause the scenario execution terminals 4 of other departments to execute the scenario. Similarly, the manager in charge of the accounting department can cause the scenario execution terminal 4 of the accounting department to execute the scenario, but cannot cause the scenario execution terminals 4 of other departments to execute the scenario. On the other hand, the manager in charge of the information system department can cause all the scenario execution terminals 4 including the general affairs department and the accounting department to execute the scenario. In this way, it is possible for each department to create an independent system for a certain department, and it is also possible to manage a certain department as a whole.

(8) RESTful API cooperation function: The management device 2 provides a RESTful API to cooperate with devices that implement or use functions of other systems. This makes it possible to issue task execution instructions and monitor statuses from other systems.

(9) Dashboard display function: The management device 2 can display the status of the scenario execution terminal 4 and the status of tasks on the administrator terminal 3 .

(10) Event management: manages events such as log-in/logout of administrative users, registration/update of scenarios, registration/update/deletion/validation/invalidation of schedules, task execution triggers and results.

(11) Floating license management: dynamically manages the number of licenses of scenario execution terminals 4 that are used simultaneously.

The functions of the management device 2, the administrator terminal 3, and the scenario execution terminal 4 in the above-described embodiment may be realized by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Furthermore, "computer-readable recording medium" means a medium that dynamically retains a program for a short period of time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system.

According to the embodiment described above, the scenario execution system has an administrator terminal, a scenario execution terminal, and a management device. The administrator terminal includes a scenario registration section and a schedule registration section. The scenario registration unit registers, in the management device, a scenario, which is data indicating a processing procedure, and scenario information indicating the attributes of a scenario execution terminal that executes the scenario. The scenario information may include information specifying other scenario information in which the pre-update scenario is set. The schedule registration unit registers schedule information indicating the execution timing of the scenario in the management device.

The scenario execution terminal includes a notification section, an instruction reception section, a scenario execution section, and an execution result notification section. The notification unit notifies the management device of the state of the own terminal at predetermined time intervals. The instruction receiving unit receives a scenario and a scenario execution instruction from the management device. The scenario execution unit executes the received scenario in response to receiving the scenario execution instruction. The execution result notification unit notifies the management device of the execution result of the scenario by the scenario execution unit. The scenario execution terminal may further include a scenario execution permitting section that controls whether execution of a scenario other than the scenario received from the management device is permitted.

The management device includes a storage section, a scenario management section, a state management section, a task management section, and an execution result reception section. The storage unit stores terminal management information indicating attributes of scenario execution terminals. For example, the attributes include at least one of the organization to which the scenario execution terminal belongs, the function that the scenario execution terminal has, and the execution environment (for example, the size of the display) of the function in the scenario execution terminal. The scenario management unit registers the scenario information and schedule information received from the administrator terminal in the storage unit. The state management unit writes state management information indicating the state notified from the scenario execution terminal into the storage unit. The reported status includes information on the execution status of the scenario. At the execution timing of the scenario indicated by the schedule information, the task management unit can execute the scenario according to the state management information among the scenario execution terminals whose terminal management information includes the attributes set in the scenario information of the scenario. A scenario execution terminal that is shown to be in a state is selected as a task allocation destination, and task allocation is performed by transmitting a scenario and a scenario execution instruction to the selected task allocation destination. The execution result receiving unit receives a scenario execution result from the scenario execution terminal. The management device may further include a statistics calculator that calculates statistics regarding the status of the scenario execution terminal.

The storage unit may further store managed object information indicating the scenario execution terminals to be managed by the administrator. In this case, the scenario information includes administrator information. At the execution timing of the scenario indicated by the schedule information, the task management unit sets the attribute set in the scenario information of the scenario in the terminal management information, and the management target of the administrator indicated by the information included in the scenario information. Among the scenario execution terminals indicated by the management target information, a scenario execution terminal indicated by the state management information that the scenario can be executed is selected as a task assignment destination.

The management device is connected to the administrator terminal and scenario execution terminal of each of a plurality of clients, and executes the processing of the scenario management unit, the state management unit, and the task management unit in a container, which is an execution environment for these processes divided for each client. Execute by Also, the management device has a storage unit for each client. A container has access to storage corresponding to the same client as the container.

Also, the management device may have an application program interface (API) for receiving schedule information from a terminal implementing arbitrary functions instead of the administrator terminal. The terminal generates schedule information using information obtained by executing any installed function, and transmits the generated schedule information to the management device using an API.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

DESCRIPTION OF SYMBOLS 1... Scenario execution system 2... Management apparatus 3... Administrator terminal 4... Scenario execution terminal 7... Network 21... Communication part 22... Distribution part 23... Processing part 24... Storage part 31... Control unit 32 Communication unit 33 Storage unit 34 Processing unit 35 Input unit 36 Display unit 41 Control unit 42 Communication unit 43 Storage unit 44 Processing unit 45 Input unit 46 Display unit 231 Information registration unit 232 Scenario management unit 233 Schedule management unit 234 Status management unit 235 Task management unit 236 Execution result reception unit 237 Log generation unit , 238... Management information providing unit, 239... Storage control unit, 341... Scenario creation unit, 342... Scenario registration unit, 343... Schedule registration unit, 344... Display control unit, 441... Notification unit, 442... Instruction reception unit, 443 Scenario execution unit 444 Execution result notification unit 445 Scenario execution permission unit 446a Function A execution unit 446b Function B execution unit 446c Function C execution unit

Claims (17)

A scenario execution system having an administrator terminal, a scenario execution terminal, and a management device,
The administrator terminal
a scenario registration unit for registering, in the management apparatus, scenario information indicating a scenario, which is data indicating a processing procedure, and attributes of the scenario execution terminal that executes the scenario;
a schedule registration unit that registers schedule information indicating execution timing of the scenario in the management device;
The scenario execution terminal
a notification unit that notifies the management device of the state of the terminal at predetermined time intervals;
an instruction receiving unit that receives the scenario and a scenario execution instruction from the management device;
a scenario execution unit that executes the received scenario in response to receiving the scenario execution instruction;
an execution result notification unit that notifies the management device of the execution result of the scenario by the scenario execution unit;
The management device
a storage unit for storing terminal management information indicating attributes of each of the plurality of scenario execution terminals;
a scenario management unit that registers the scenario information and the schedule information received from the administrator terminal in the storage unit;
a state management unit that writes, in the storage unit, state management information indicating the state notified from each of the plurality of scenario execution terminals;
At the execution timing of the scenario indicated by the schedule information, among the scenario execution terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information, a scenario is executed in the state management information. a task management unit that selects the scenario execution terminal indicated to be in a possible state as a task allocation destination, and performs task allocation for transmitting the scenario and the scenario execution instruction to the selected task allocation destination; ,
an execution result receiving unit that receives the execution result of the scenario from the scenario execution terminal to which the task is assigned ;
The attributes include at least one of an operating system implemented by the scenario execution terminal, an application implemented by the scenario execution terminal, and a screen size of the scenario execution terminal.
Scenario execution system. A scenario execution system having an administrator terminal, a scenario execution terminal, and a management device,
The administrator terminal
a scenario registration unit for registering, in the management apparatus, scenario information indicating a scenario, which is data indicating a processing procedure, and attributes of the scenario execution terminal that executes the scenario;
a schedule registration unit that registers schedule information indicating execution timing of the scenario in the management device;
The scenario execution terminal
a notification unit that notifies the management device of the state of the terminal at predetermined time intervals;
an instruction receiving unit that receives the scenario and a scenario execution instruction from the management device;
a scenario execution unit that executes the received scenario in response to receiving the scenario execution instruction;
an execution result notification unit that notifies the management device of the execution result of the scenario by the scenario execution unit;
The management device
a storage unit for storing terminal management information indicating attributes of each of the plurality of scenario execution terminals , and a number of simultaneous uses, which is the number of the scenario execution terminals that can simultaneously execute tasks ;
a scenario management unit that registers the scenario information and the schedule information received from the administrator terminal in the storage unit;
a state management unit that writes, in the storage unit, state management information indicating the state notified from each of the plurality of scenario execution terminals;
When the number of the scenario execution terminals that are executing tasks obtained based on the state management information does not reach the number of simultaneous uses, the scenario information of the scenario at the execution timing of the scenario indicated by the schedule information. Among the scenario execution terminals for which the set attribute is set in the terminal management information, the scenario execution terminal indicated in the state management information as being capable of executing a scenario is assigned to a task. a task management unit that performs task assignment for transmitting the scenario and the scenario execution instruction to the selected assignment destination of the task;
an execution result receiving unit that receives execution results of the scenario from the scenario execution terminal to which the task is assigned ;
Scenario execution system. The scenario execution terminal further comprises a scenario execution permitting unit that controls whether execution of a scenario other than the scenario received from the management device is permitted.
3. The scenario execution system according to claim 1 or 2 . The management device is connected to the manager terminal and the scenario execution terminal of each of a plurality of clients, and performs the processing of the scenario management section, the state management section, and the task management section in the processing divided for each client. Executed by a container that is an execution environment, and having the storage unit for each client,
the container has access to the storage corresponding to the same client as the container;
The scenario execution system according to any one of claims 1 to 3. The management device has an application program interface for receiving the schedule information from a terminal implementing arbitrary functions instead of the administrator terminal,
The terminal generates the schedule information using information obtained by executing any of the functions, and transmits the generated schedule information to the management device using the application program interface.
The scenario execution system according to any one of claims 1 to 4 . a storage unit for storing terminal management information indicating attributes of each of a plurality of scenario execution terminals;
A scenario, which is data indicating a processing procedure, scenario information indicating attributes of the scenario execution terminal that executes the scenario, and schedule information indicating execution timing of the scenario are received from the administrator terminal and stored in the storage unit. a scenario management section to be registered;
a state management unit that receives notification of a state from each of the plurality of scenario execution terminals at predetermined time intervals and writes state management information indicating the notified state into the storage unit;
At the execution timing of the scenario indicated by the schedule information, among the scenario execution terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information, a scenario is executed in the state management information. a task management unit that selects, as a task allocation destination, the scenario execution terminal indicated to be in a state in which the
an execution result receiving unit that receives an execution result of the scenario from the scenario execution terminal to which the task is assigned ;
with
The attributes include at least one of an operating system implemented by the scenario execution terminal, an application implemented by the scenario execution terminal, and a screen size of the scenario execution terminal.
management device. a storage unit for storing terminal management information indicating the attributes of each of a plurality of scenario execution terminals , and the number of simultaneous uses, which is the number of the scenario execution terminals that can simultaneously execute tasks ;
A scenario, which is data indicating a processing procedure, scenario information indicating attributes of the scenario execution terminal that executes the scenario, and schedule information indicating execution timing of the scenario are received from the administrator terminal and stored in the storage unit. a scenario management section to be registered;
a state management unit that receives notification of a state from each of the plurality of scenario execution terminals at predetermined time intervals and writes state management information indicating the notified state into the storage unit;
When the number of the scenario execution terminals that are executing tasks obtained based on the state management information does not reach the number of simultaneous uses, the scenario information of the scenario at the execution timing of the scenario indicated by the schedule information. Among the scenario execution terminals for which the set attribute is set in the terminal management information, the scenario execution terminal indicated in the state management information as being capable of executing a scenario is assigned to a task. and a task management unit that transmits the scenario and the scenario execution instruction to the selected assignment destination of the task;
an execution result receiving unit that receives an execution result of the scenario from the scenario execution terminal to which the task is assigned ;
A management device comprising The attributes include at least one of an organization to which the scenario execution terminal belongs, a function possessed by the scenario execution terminal, and an execution environment of the function in the scenario execution terminal.
The management device according to claim 6 or 7 . The status notified from the scenario execution terminal to which the task is assigned includes information on the execution status of the scenario.
The management device according to any one of claims 6 to 8 . further comprising a statistics calculation unit that calculates statistics regarding the state of the scenario execution terminal;
The management device according to any one of claims 6 to 9 . The storage unit further stores managed object information indicating the scenario execution terminals to be managed by an administrator,
The scenario information includes administrator information,
The task management unit sets the attribute set in the scenario information of the scenario to the terminal management information and the information included in the scenario information at the execution timing of the scenario indicated by the schedule information. Among the scenario execution terminals indicated by the management target information that are managed by the administrator indicated by the task to select as the assignee of the
The management device according to any one of claims 6 to 10 . The scenario information includes information specifying other scenario information in which the scenario before updating is set,
The management device according to any one of claims 6 to 11 . A scenario execution management method in a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device, comprising:
The administrator terminal
a scenario registration step of registering, in the management device, scenario information indicating a scenario, which is data indicating a processing procedure, and attributes of the scenario execution terminal that executes the scenario;
a schedule registration step of registering schedule information indicating execution timing of the scenario in the management device;
The scenario execution terminal
a notification step of notifying the management device of the state of the own terminal at predetermined time intervals;
an instruction receiving step of receiving the scenario and a scenario execution instruction from the management device;
a scenario execution step of executing the received scenario in response to receiving the scenario execution instruction;
an execution result notification step of notifying the management device of an execution result of the scenario by the scenario execution step;
The management device
a scenario management step of registering the scenario information and the schedule information received from the administrator terminal in a storage unit that stores terminal management information indicating attributes of each of the plurality of scenario execution terminals;
a state management step of writing state management information indicating the state notified from each of the plurality of scenario execution terminals into the storage unit;
At the execution timing of the scenario indicated by the schedule information, among the scenario execution terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information, a scenario is executed in the state management information. a task management step of performing task assignment of selecting the scenario execution terminal indicated to be in a possible state as a task assignment destination, and transmitting the scenario and the scenario execution instruction to the selected task assignment destination; ,
an execution result receiving step of receiving execution results of the scenario from the scenario execution terminal to which the task is assigned ;
has
The attributes include at least one of an operating system implemented by the scenario execution terminal, an application implemented by the scenario execution terminal, and a screen size of the scenario execution terminal.
Scenario execution management method. A scenario execution management method in a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device, comprising:
The administrator terminal
a scenario registration step of registering, in the management device, scenario information indicating a scenario, which is data indicating a processing procedure, and attributes of the scenario execution terminal that executes the scenario;
a schedule registration step of registering schedule information indicating execution timing of the scenario in the management device;
The scenario execution terminal
a notification step of notifying the management device of the state of the own terminal at predetermined time intervals;
an instruction receiving step of receiving the scenario and a scenario execution instruction from the management device;
a scenario execution step of executing the received scenario in response to receiving the scenario execution instruction;
an execution result notification step of notifying the management device of an execution result of the scenario by the scenario execution step;
The management device
terminal management information indicating the attributes of each of the plurality of scenario execution terminals, and the number of simultaneous uses, which is the number of scenario execution terminals that can simultaneously execute tasks, received from the administrator terminal; a scenario management step of registering the scenario information and the schedule information;
a state management step of writing state management information indicating the state notified from each of the plurality of scenario execution terminals into the storage unit;
When the number of the scenario execution terminals that are executing tasks obtained based on the state management information does not reach the number of simultaneous uses, the scenario information of the scenario at the execution timing of the scenario indicated by the schedule information. Among the scenario execution terminals for which the set attribute is set in the terminal management information, the scenario execution terminal indicated in the state management information as being capable of executing a scenario is assigned to a task. a task management step of performing task assignment for transmitting the scenario and the scenario execution instruction to the selected assignment destination of the task;
an execution result receiving step of receiving execution results of the scenario from the scenario execution terminal to which the task is assigned ;
A scenario execution management method comprising: A scenario execution management method in a management device of a scenario execution system having a manager terminal, a scenario execution terminal, and a management device, comprising:
receiving from the administrator terminal a scenario that is data indicating a processing procedure, scenario information indicating attributes of the scenario execution terminal that executes the scenario, and schedule information indicating execution timing of the scenario ; a scenario management step of registering terminal management information indicating attributes of each of the scenario execution terminals in a storage unit;
a state management step of receiving notification of a state from each of the plurality of scenario execution terminals at predetermined time intervals and writing state management information indicating the notified state into the storage unit;
At the execution timing of the scenario indicated by the schedule information, among the scenario execution terminals for which the attribute set in the scenario information of the scenario is set in the terminal management information, a scenario is executed in the state management information. a task management step of selecting, as a task allocation destination, the scenario execution terminal indicated to be in a state capable of executing a task, and transmitting the scenario and a scenario execution instruction to the selected task allocation destination;
an execution result receiving step of receiving execution results of the scenario from the scenario execution terminal to which the task is assigned ;
has
The attributes include at least one of an operating system implemented by the scenario execution terminal, an application implemented by the scenario execution terminal, and a screen size of the scenario execution terminal.
Scenario execution management method. A scenario execution management method in a management device of a scenario execution system having a manager terminal, a scenario execution terminal, and a management device, comprising:
receiving from the administrator terminal a scenario that is data indicating a processing procedure, scenario information indicating attributes of the scenario execution terminal that executes the scenario, and schedule information indicating execution timing of the scenario ; a scenario management step of registering terminal management information indicating the attributes of each of the scenario execution terminals and a number of simultaneous uses, which is the number of scenario execution terminals that can simultaneously execute tasks, in a storage unit;
a state management step of receiving notification of a state from each of the plurality of scenario execution terminals at predetermined time intervals and writing state management information indicating the notified state into the storage unit;
When the number of the scenario execution terminals that are executing tasks obtained based on the state management information does not reach the number of simultaneous uses, the scenario information of the scenario at the execution timing of the scenario indicated by the schedule information. Among the scenario execution terminals for which the set attribute is set in the terminal management information, the scenario execution terminal indicated in the state management information as being capable of executing a scenario is assigned to a task. a task management step of selecting the scenario and sending the scenario execution instruction to the selected assignee of the task;
an execution result receiving step of receiving execution results of the scenario from the scenario execution terminal to which the task is assigned ;
A scenario execution management method comprising: the computer,
A program for functioning as the management apparatus according to any one of claims 6 to 12 .

Images