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

Abstract

To manage the execution of a scenario in an information processing device.SOLUTION: A management device 2 receives scenario information indicating a scenario and an attribute of a scenario execution terminal 4 which executes the scenario and schedule information indicating an execution timing of the scenario from a manager terminal 3, and registers them in a storage unit. The scenario execution terminal 4 notifies the management device 2 of a state of an own device with every predetermined time. The management device 2 selects the scenario execution terminal 4 in a state where the execution of the scenario is possible among scenario execution terminals 4 having attributes set in the scenario information of the scenario in the execution timing of the scenario indicated by the schedule information as an allocation destination of a task, and transmits the scenario and a scenario execution instruction to the selected allocation destination of the task. The scenario execution terminal 4 executes the received scenario, and notifies the management device 2 of an execution result.SELECTED DRAWING: Figure 1

Description

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 manually performed using an information processing device such as a PC (personal computer). For example, a scenario describing a work procedure is created (for example, refer to Patent Document 1), and the PC executes the scenario to reproduce the work manually performed (for example, refer to Patent Document 2). The RPA can reduce time cost, human cost, and work mistakes.

Japanese Patent No. 5026451 Japanese Patent No. 4883638

There has been a demand for a company or an organization to manage the execution of a scenario, such as an execution time of the scenario or an information processing device for executing the scenario, in order to improve the work efficiency 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 the execution of a scenario 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 apparatus, wherein the administrator terminal is a scenario that is data indicating a processing procedure, and the scenario that executes the scenario. The scenario execution terminal includes a scenario registration unit that registers scenario information indicating the attribute of the execution terminal in the management device, and a schedule registration unit that registers schedule information indicating the execution timing of the scenario in the management device. A notification unit that notifies the management device of the state of its own terminal at predetermined time intervals, an instruction reception unit that receives the scenario and the scenario execution instruction from the management device, and the reception unit that receives the scenario execution instruction. The management device includes a scenario execution unit that executes a scenario, and an execution result notification unit that notifies the management device of the execution result of the scenario by the scenario execution unit, and the management device includes terminal management information indicating attributes of the scenario execution terminal. A storage unit that stores the scenario information, a scenario management unit that registers 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, Of the status management unit that writes in the storage unit and the scenario execution terminal in 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 Selecting the scenario execution terminal whose status management information indicates that the scenario can be executed as a task allocation destination, and transmitting the scenario and the scenario execution instruction to the selected task allocation destination The scenario execution system includes a task management unit that performs task allocation, and an execution result reception unit that receives an 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 permission unit that controls whether or not to permit execution of a scenario other than the scenario received from the management device. Prepare

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

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 that implements an arbitrary function, instead of the administrator terminal. Then, the terminal generates the schedule information by using the information obtained by executing the arbitrary function, and transmits the generated schedule information to the management device by using the application program interface.

One aspect of the present invention is scenario information indicating a storage unit that stores terminal management information indicating an attribute of a scenario execution terminal, a scenario that is data indicating a processing procedure, and an attribute of the scenario execution terminal that executes the scenario. , And a scenario management unit that receives schedule information indicating the execution timing of the scenario from the administrator terminal and registers the schedule information in the storage unit, and a status notification from the scenario execution terminal at predetermined time intervals, and the notified At a state management unit that writes state management information indicating a state to 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. Of the scenario execution terminals, the scenario execution terminal whose status management information indicates that the scenario can be executed is selected as a task assignment destination, and the scenario is assigned to the selected task assignment destination. And a task execution unit that sends a scenario execution instruction, and an execution result receiving unit that receives an execution result of the scenario from the scenario execution terminal.

One aspect of the present invention is the management device described above, wherein the attribute is either an organization to which the scenario execution terminal belongs, a function of the scenario execution terminal, or an execution environment of the function in the scenario execution terminal. Including at least

One mode of the present invention is the above-mentioned management device, wherein the status notified from the scenario execution terminal to which the task is assigned includes information on the execution status of the scenario.

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

One aspect of the present invention is the management device described above, wherein the storage unit further stores management target information indicating the scenario execution terminal managed by the manager, and the scenario information stores information about the manager. The task management unit includes, in 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 is included in the scenario information. Among the scenario execution terminals indicated by the management target information as being managed by the administrator indicated by the information, the scenario execution terminal indicated by the state management information as being in a state in which a scenario can be executed. Is selected as the task assignee.

One aspect of the present invention is the above-described management device, wherein the scenario information includes information that identifies 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 apparatus, wherein the administrator terminal is data indicating a processing procedure, and the scenario Scenario registration step of registering scenario information indicating the attribute of the scenario execution terminal that executes the scenario in the management apparatus, schedule registration step of registering schedule information indicating execution timing of the scenario in the management apparatus, and scenario execution A terminal, a notification step of notifying the management device of the state of its own terminal every predetermined time, an instruction reception step of receiving the scenario and a scenario execution instruction from the management device, in response to the reception of the scenario execution instruction, A scenario execution step of executing the received scenario, an execution result notification step of notifying the management device of the execution result of the scenario by the scenario execution step, and the management device indicating the attribute 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 state management information indicating the state notified from the scenario execution terminal in the storage unit. At the state management step of writing and at the execution timing of the scenario indicated by the schedule information, the state among the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information Task assignment that selects the scenario execution terminal whose management information indicates that a scenario can be executed as a task assignment destination, and sends the scenario and the scenario execution instruction to the selected task assignment destination And a execution result receiving step of receiving an execution result of the scenario from the scenario execution terminal.

One aspect of the present invention is a scenario execution management method in the management device of a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device, wherein the scenario is data indicating a processing procedure, and the scenario is executed. A storage unit that receives scenario information indicating an attribute of the scenario execution terminal and schedule information indicating an execution timing of the scenario from the administrator terminal, and stores terminal management information indicating an attribute of the scenario execution terminal. A scenario management step of registering in the storage unit, a status management step of receiving a status notification from the scenario execution terminal at predetermined time intervals, and writing status management information indicating the notified status to the storage unit; At the execution timing of a scenario, a scenario is executable in the status management information among the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information. That the scenario execution terminal is indicated as a task allocation destination, and a task management step of transmitting the scenario and a scenario execution instruction to the selected task allocation destination; and a scenario execution result from the scenario execution terminal And an execution result receiving step of receiving the execution result.

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

According to the present invention, it becomes possible to manage the execution of a scenario in an information processing device.

It is a block diagram of the scenario execution system by one Embodiment of this invention. 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 embodiment. It is a functional block diagram which shows the structure of the scenario execution terminal by the same embodiment. It is a figure which shows the example of the administrator information by the embodiment. It is a figure which shows the example of the terminal management information by the embodiment. It is a figure which shows the example of the scenario information by the embodiment. It is a figure which shows the example of the schedule information by the embodiment. It is a figure which shows the example of the state management information by the embodiment. It is a figure which shows the example of log data by the same embodiment. It is a figure which shows the sequence of the scenario registration process and schedule registration process in the scenario execution system by the same embodiment. It is a figure which shows the sequence of the task allocation process in the scenario execution system by the same embodiment. It is a figure which shows the example of the scenario new registration screen by the embodiment. It is a figure which shows the example of the scenario update screen by the embodiment. It is a figure which shows the example of the scenario history display screen by the same embodiment. It is a figure which shows the example of the schedule registration screen by the 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 an embodiment of the present invention. The 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 of the client α and the scenario execution terminal 4 via a network 7 such as the Internet. The management device 2 further manages each client (not shown) via the network 7, 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 person terminal 3 and the scenario execution terminal 4. For the sake of simplicity, the function and operation of the scenario execution system 1 will be described below by taking one client α as an example. The operations and functions of the scenario execution system 1 are the same for 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 the scenario execution terminal 4 are, for example, PCs. One 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 the RPA (Robotic Process Automation) scenario generated and instructed to be executed by the administrator terminal 3. The scenario execution terminals 4 can be divided into groups according to the organization of the client α. In the figure, Group A is the Human Resources 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 and execute scenarios.

FIG. 2 is a functional block diagram showing the configuration of the management device 2. The management device 2 is realized by, for example, one or more information processing devices (for example, computer servers) on the cloud. When the management device 2 is implemented by using a plurality of information processing devices that are communicatively connected via the network 7, the functional units included in the management device 2 are distributed and implemented in the plurality of information processing devices. May be done. Which information processing apparatus is used to implement each functional unit of the management apparatus 2 may be arbitrary. Also, the same functional unit may be realized by a plurality of information processing devices.

The management device 2 includes a communication unit 21, a distribution unit 22, a processing unit 23, and a storage unit 24. The communication unit 21 transmits/receives data to/from the administrator terminal 3 and the scenario execution terminal 4 via the network 7. The distribution unit 22 distributes the access from the administrator terminal 3 and the scenario execution terminal 4 to the processing unit 23 of the container according to the client. The processing unit 23 is mounted in a different container for each client. The storage unit 24 is implemented by using a different storage area for each client or in a different database device 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 of each administrator, authority, and information of the scenario execution terminal 4 to be managed. The identification information of the administrator may be, for example, an ID given to the administrator or the address of the administrator terminal 3. The authority indicates the management function that the 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 administrator of the group A (human resources department) targets the scenario execution terminal 4 of the group A (human resources department), and the administrator of the group D (information system department) manages the groups A, B, C (human resources department). , Accounting department, general affairs department), the scenario execution terminals 4 of all groups are managed. The management target may be indicated by the identification information, the attribute, the group, etc. of the scenario execution terminal 4. Note that one administrator may belong to multiple groups.

The terminal management information includes identification information of the scenario execution terminal 4, license expiration date, address, and attribute information. The identification information of the scenario execution terminal 4 is an ID issued 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 allows the scenario execution terminal 4 to use the scenario execution function. The attribute indicates a group (organization) to which the scenario executing terminal 4 belongs, a function of the scenario executing terminal 4, an application version for executing the function, an execution environment of the function in the scenario executing terminal 4, and the like. Note that one scenario execution terminal 4 may belong to two or more organizations. The function of the scenario execution terminal 4 can be indicated by, for example, the OS (Operation System) name or the name and type of the application installed in the scenario execution terminal 4. Version information may be added to the OS name and the application name.

The scenario information includes the identification information of the scenario information, the name of the scenario, the file in which the scenario is described, the update information, the attribute of the scenario execution terminal 4 that executes the scenario, and the identification information of the administrator who created the scenario. The 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 that identifies other scenario information in which the scenario before update is set. Further, the scenario information includes the data format of the input parameter when the scenario is executed and the data format of the output parameter when the scenario is completed.

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

The state management information indicates the state of the scenario execution terminal 4 at each time. The log data indicates the event that occurred in the administrator terminal 3 and the scenario execution terminal 4 and the date and time when the event occurred. Events include administrator login/logout, scenario information registration/update, schedule information registration/update/deletion, enable/disable, task execution triggers and execution results. 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. The floating license is a service in which executing scenarios simultaneously among the scenario execution terminals 4 to which the license is assigned determines the upper limit of the number of terminals.

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 status management unit 234 receives a status notification from the scenario execution terminal 4 at predetermined time intervals, generates status management information indicating the notified status, and writes the status management information in the storage unit 24.

The task management unit 235, at the execution timing of the scenario indicated by the schedule information, the status management information among the scenario execution terminals 4 set in the terminal management information as the execution terminal set in the scenario information of the scenario. The scenario execution terminal 4 which indicates that the scenario can be executed is selected as the task allocation destination. The task management unit 235 transmits the file in which the scenario is described 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 an event in the administrator terminal 3 and the scenario execution terminal 4, generates log data of the detected event, and registers it in the storage unit 24. The management information providing unit 238 is an example of a statistical calculation unit that calculates statistics related to the status of the scenario execution terminal 4 and the task status. The management information providing unit 238 transmits screen data indicating the calculation result of the statistics to the administrator terminal 3 and displays it. 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. The administrator terminal 3 includes a control unit 31, a communication unit 32, a storage unit 33, a processing unit 34, an input unit 35, and a display unit 36. The control unit 31 includes a CPU and various memories, and controls each unit. The communication unit 32 transmits/receives data to/from the management device 2 via the network 7. The storage unit 33 stores various types of 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 receives the administrator's input from the input unit 35 and creates a scenario. The scenario registration unit 342 receives the administrator's input from the input unit 35 and transmits the scenario information in which the created scenario file is set to the management device 2. The schedule registration unit 343 receives the input from the administrator through 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 by using an existing input device such as a keyboard, pointing device (mouse, tablet, etc.), button, touch panel and the like. The input unit 35 is operated by the user when the user's instruction is input 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, and an organic EL (Electro Luminescence) display.

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

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

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

The notification unit 441 notifies the management device 2 of the state of the own terminal at predetermined time intervals of several tens of seconds to several minutes, such as a 30-second cycle. The instruction receiving unit 442 receives a scenario and a scenario execution instruction from the management device 2. The scenario execution unit 443 executes the scenario in response to the reception of the 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 to permit execution of a scenario other than the scenario received from the management device 2 based on the setting information stored in the storage unit 43.

The function X execution unit 446 executes the application of the function X. The function X is a function that can be used for executing a scenario, and can be an arbitrary function implemented in a PC, such as email transmission/reception, spreadsheet, document editing, postcard creation, graphic drawing, or web browser. In the figure, a function X execution unit 446 (X=A, B, C) that executes each application of functions A, B, and C is referred to as a function A execution unit 446a, a function B execution unit 446b, and a function C execution unit 446c. It has been described.

The input unit 45 is configured by using an existing input device such as a keyboard, a pointing device, a touch panel. The input unit 45 is operated by the user when the user's instruction is input to the scenario execution terminal 4. The display unit 46 is an image display device such as a CRT display, a liquid crystal display, an 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 information on user ID, user name, affiliation and authority. The user ID is identification information that identifies the administrator. The user name is the name of the administrator. Affiliation indicates the organization to which the administrator belongs. The organization may have a hierarchical structure. Further, one administrator may belong to two or more organizations. The affiliation is used as management target information indicating the scenario execution terminal 4 managed by the administrator. That is, it indicates which belonging of the scenario execution terminal 4 can be managed depending on the belonging of the administrator. The authority indicates, for example, whether scenario registration, schedule registration, or viewing of status display is permitted.

FIG. 6 is a diagram showing an example of the 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 given to the scenario execution function for each scenario execution terminal 4. The license expiration date indicates the expiration date of the license of the application software that causes the scenario execution terminal 4 to realize 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 attribute indicates the 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. The screen size is the size of the display (display unit 46) included in the scenario execution terminal 4. The affiliation indicates the organization to which the scenario execution terminal 4 belongs. The function tag indicates the function of the scenario execution terminal 4. For the function, the name, type, version, etc. of an application (for example, accounting software, mail transmission/reception software, etc.) installed in the scenario execution terminal 4 can be used.

FIG. 7 is a diagram showing an example of scenario information. The 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, generation date and time, and update date and time. .. The scenario ID is information that uniquely identifies the scenario. The creator indicates the administrator who created the scenario information, and for example, the user ID is used. The parent scenario ID indicates the scenario ID of the original scenario when the scenario is created by updating the already generated scenario. The scenario name indicates the name of the scenario.

The scenario file indicates a file in which a scenario is described or a storage location of the file in the storage unit 24. The input parameter defines the data format of the parameter input when the scenario is executed. The output parameter defines the data format of the parameter for which the scenario execution result is set. The timeout indicates the time to wait before determining that the scenario execution is an error when the scenario execution is stopped midway. The attribute indicates the attribute of the scenario execution terminal 4 that is the execution target of the scenario. The attribute is indicated by the OS name, screen size, affiliation, function tag and the like. The memo is a description about the scenario. The scenario tag is a tag given to a scenario. The correction content indicates the content changed from the parent scenario. The creation date and time indicates the creation date and time 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 a schedule ID, creator, schedule name, affiliation, execution scenario, execution terminal, input parameter value, execution timing, and operation information when an abnormality occurs. The schedule ID is information that uniquely identifies the schedule information. The creator indicates the administrator who created the scenario information, and for example, the user ID is used. The affiliation indicates the affiliation of the schedule information, and the scenario execution terminals 4 belonging to the same affiliation can execute the scenario. The execution scenario is the scenario ID of the execution target scenario.

The execution terminal indicates the scenario execution terminal 4 (hereinafter, also referred to as “execution target terminal”) for executing the scenario and the number of execution terminals. The maximum number of licenses that can be used is the number of licenses that can be used simultaneously. When the execution target terminal is selected based on the attribute set in the scenario information, the execution terminal does not have to be set. When the execution target terminal is selected by a predetermined condition in addition to the attribute set in the scenario information, the condition is set in the execution terminal. For the execution terminal, the attribute (affiliation or function tag) of the scenario execution terminal 4, the scenario execution function ID, the PC name, the state, etc. can be used. When the attributes, states, etc. are set without specifying a specific scenario execution terminal 4 such as the scenario execution function ID and the PC name in the execution terminals, the scenario execution terminals 4 of the number of executions among the scenario execution terminals 4 satisfying the attributes are set. To run the scenario.

The input parameter value indicates the value of the parameter input to the scenario execution terminal 4 when the scenario is executed. The execution timing indicates the timing to execute the scenario. The execution timing is indicated by immediate, predetermined date and time, daily and time, predetermined day and time of each month, predetermined day and time of every week, end of month or a predetermined day before and after the end of the month. The operation when an abnormality occurs indicates the operation performed when the scenario execution terminal 4 has an abnormality during the execution of the scenario.

FIG. 9 is a diagram showing an example of the state management information. The status management information includes information on the scenario execution function ID, time, scenario execution function status, and task status. The scenario execution function state indicates the state of the scenario execution function specified by the scenario execution function ID. The status includes stoppage, restarting, starting up, license expiration, starting up, user operation, scenario execution, scenario execution abnormal stop, preparation for next scenario execution, communication interruption, and the like. During the stop, the scenario execution function is instructed to stop, or the scenario execution function is stopped. During the restart, the scenario execution function is instructed to restart. During startup, the scenario execution function is being started. License revocation is a state in which the license for the scenario execution function has revoked. During the start-up, the scenario execution function has started normally and is waiting for the execution of the scenario. During the user operation, the scenario execution function is performing a scenario recording operation, and the next scenario cannot be executed until this state changes. During scenario execution, the scenario specified by the scenario execution function is being executed. During the scenario execution abnormal stop, the scenario execution function is in a stopped state due to some problem while the scenario instructed is being executed. During preparation for execution of the next scenario, the scenario execution function is in a state of deleting and rewriting data so that the next scenario can be executed. Communication interruption is a state in which the notification to the scenario execution function is interrupted.

Task states include waiting, processing, normal termination, suspended, suspended, abnormally stopped, and abnormally terminated. The waiting state is a state of waiting until a task is assigned to the scenario execution function. During processing, the scenario execution function is assigned to a task and is being executed. Normal termination is a state in which task execution has terminated normally. During the suspension, the suspension of the task execution is instructed. The suspended state is a suspended state in which the suspension of the execution of the task being executed is instructed. Abnormal stop is a state in which an abnormality has occurred during the execution of a task and the task has stopped. Abnormal termination is a state in which an abnormality has occurred during the execution of a task and the task has ended.

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

Next, the operation of the scenario execution system 1 will be described. 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 a part of the terminal management information from the scenario execution terminal 4 and set it.

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

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

The scenario management unit 232 of the management device 2 sets the scenario information received from the administrator terminal 3 to the scenario information received from the administrator terminal 3 when the scenario information is set in the administrator information specified by the user ID of the administrator. The data is written in the storage unit 24 (step S103). The scenario ID, the user ID indicating the creator, the generation date and the update date and time may be set in the scenario management unit 232 without being transmitted from the administrator terminal 3. The scenario management unit 232 may set the storage location of the scenario file in the storage unit 24 in the scenario file of the scenario information. If the affiliation set in the scenario information is outside the management target of the affiliation obtained from the administrator information specified by the administrator user ID, the scenario management unit 232 registers it in the storage unit 24. Does not. Further, the scenario management unit 232 of the management device 2 may transmit the scenario information to the administrator terminal 3 in multiple times.

The schedule registration unit 343 of the administrator terminal 3 issues a schedule registration request including schedule information in which timing for causing the management apparatus 2 to execute the registered scenario 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 the execution terminal includes information for selecting the scenario execution terminal 4 that executes the scenario.

The administrator terminal 3 may acquire a scenario information list that matches the search condition 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 the search condition (for example, scenario ID, scenario name, attribute, memo, update date and time) to the management device 2. The scenario management unit 232 of the management device 2 identifies the affiliation of the management target based on the affiliation of the administrator information specified by the user ID, and selects the scenario information in which the affiliation of the management target is set as the search condition. Select the matching scenario information. The scenario management unit 232 sends the list of the selected scenario information to the administrator terminal 3. The list includes some information extracted from the scenario information, such as the scenario ID, the scenario name, the attribute, and the update date and time. The display control unit 344 of the administrator terminal 3 displays the list on the display unit 36. The administrator selects scenario information of a 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 schedule information can be registered in the administrator information specified by the user ID received from the administrator terminal 3 (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 managed by the affiliation set in the administrator information specified by the administrator user ID, the schedule management unit 233 registers it in the storage unit 24. Does not. Further, the schedule management unit 233 of the management device 2 may transmit the schedule information to the administrator terminal 3 in a plurality of times.

The schedule management unit 233 may receive an instruction to validate, invalidate, or delete the schedule information from the administrator terminal 3. In this case, the instruction is set with a schedule ID that identifies schedule information to be validated, invalidated, or deleted. When the schedule management unit 233 receives a user ID of an administrator whose schedule information is set to be able to be registered in the administrator information and an instruction to enable or disable it, the schedule management unit 233 associates it with the schedule ID set to the instruction. , Valid or invalid state is written in the storage unit 24. On the other hand, when the schedule management unit 233 receives the user ID of the administrator whose schedule registration is permitted in the administrator information and the deletion instruction, the schedule management unit 233 deletes the schedule information of the schedule ID set in the instruction. .. Further, the schedule registration request may include an instruction to enable or disable the schedule information. Note that the schedule management unit 233 excludes the affiliation set in the schedule information instructed to be enabled, disabled, or deleted from the affiliation obtained from the administrator information specified by the administrator user ID. If it is, the instructed activation, deactivation, or deletion processing is not performed.

The administrator terminal 3 acquires a schedule information list that matches the search condition from the management device 2, and designates the schedule ID of the schedule information selected from the list as a target for activation, deactivation, or deletion. You may set it. In this case, the administrator terminal 3 transmits the user ID and the search condition (for example, schedule ID, schedule name, attribute, update date and time) to the management device 2. The schedule management unit 233 of the management device 2 specifies the affiliation of the management target based on the affiliation of the administrator information specified by the user ID, and selects the affiliation of the management target as the search condition from the schedule information in which the affiliation of the management target is set. Select the 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. The administrator selects scenario information of a scenario to be executed by the input unit 35 from the displayed list.

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

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

On the other hand, the task management unit 235 sets valid schedule information when the number of scenario execution terminals 4 currently executing the task has not reached the number of concurrent licenses or the client α does not use the floating license. The task allocation process is started at a certain execution timing. When the task management unit 235 has started the task allocation process and has not completed the task allocation process, the task management unit 235 determines whether the status notification source terminal is to be the task allocation target (step S203). ).

Specifically, the task management unit 235 first determines whether or not the status of the status notification source terminal is a task assignable status, that is, “starting”. When the task management unit 235 determines that the task cannot be assigned, the state notification source terminal determines that the task notification source terminal is not a task assignment target.

When the task management unit 235 determines that the state of the status notification source terminal is the state in which the task can be assigned, the task management unit 235 refers to the terminal management information of the status notification source terminal to execute the schedule information execution terminal and the schedule information execution scenario. It is determined whether the attribute of the scenario information specified by is satisfied. The task management unit 235 determines that the status notification source terminal is a task allocation target when it determines that the conditions are satisfied, and determines that the status notification source terminal is not a task allocation target when it determines that the terminals are not satisfied.

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

The scenario execution unit 443 of the scenario execution terminal 4 receives the scenario execution instruction and executes the scenario (step S205). 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 even after the scenario execution is started (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 the management device 2 (step S208). The execution result receiving unit 236 of the management device 2 receives the execution result and writes it in 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 allocation has not been started or the status notification source terminal is not the task allocation target, the scenario allocation determination ends.

Next, the screen displayed by the management device 2 on the administrator terminal 3 will be described.
FIG. 13 is a diagram showing an example of the scenario new registration screen 81. The scenario management unit 232 of the management device 2 generates screen data of the scenario new registration screen 81 and displays it on the display unit 36 of the administrator terminal 3. The scenario new 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 field. A setting field 817, a function tag setting field 818, a scenario tag setting field 819, and a new creation button 810 are provided.

The setting field 812 shown in the figure is capable of setting each hierarchical level represented by three hierarchical levels. The scenario management unit 232 of the management device 2 displays a list of affiliations that can be selected according to the affiliation of the administrator of the user ID received from the administrator terminal 3 and sets the one selected in the setting field 812. You may do so. When the input parameter addition button 814 is selected, a screen for defining the data format of the input parameter is displayed on the administrator terminal 3. When the output parameter addition button 815 is selected, a screen for defining the data format of the output parameter is displayed on the administrator terminal 3. 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. When updating the scenario information of the already generated scenario, the scenario management unit 232 of the management device 2 uses the scenario information of the parent scenario specified by the information received from the administrator terminal 3 to display the scenario update screen 82. The screen data is generated and displayed on the administrator terminal 3. On the scenario update screen 82, the information set in the scenario information of the parent scenario is displayed by default, and for the updatable information, the default value is displayed in the setting field. 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. Setting field 827, function tag setting field 828, scenario tag setting field 829, correction content setting field 830, and update button 831. When the update button 831 is selected after updating the information, 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. The scenario management unit 232 of the management device 2 receives the scenario ID and the scenario history request of the scenario information selected from the scenario information list of the search result from the administrator terminal 3. The scenario management unit 232 identifies the scenario information of the version before the one having the parent ID set in the scenario information of the received scenario ID (hereinafter referred to as current scenario information) as the scenario ID. Similarly, the scenario management unit 232 uses the parent ID set in the identified scenario information to perform the process of identifying the scenario information of the previous version until the scenario information in which the parent ID is not set is obtained. repeat. The scenario management unit 232 identifies the first generation new scenario information whose parent ID is the ID of the current scenario information. The scenario management unit 232 repeats the process of specifying the newer version of the scenario information having the ID set in the specified scenario information as the parent ID. The scenario management unit 232 generates a scenario history display screen 84 that displays a partial list of information obtained from the identified scenario information in order of version, centered on the current scenario information, and displays the scenario history display screen 84 on the administrator terminal 3.

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 identified scenario information is displayed in order of version. In the figure, the date and time of generation, the editor, the correction content, and the 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. In addition, the display area 843 of the current scenario information 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 that the selection button has been selected, the scenario management unit 232 causes the administrator terminal 3 to display a scenario information detail screen that displays 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. When the administrator terminal 3 selects the registered scenario information and requests the schedule registration, the schedule management unit 233 of the management device 2 uses the selected scenario information to generate the screen data of the schedule registration screen 85. , 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 of the selected scenario information, a scenario name display area 854 of the selected scenario information, an execution terminal designation button 855, and an input. A parameter value setting field 856, an input file designation field 857, an execution designation button 858, an operation selection button 859 when an abnormality occurs, and a schedule registration button 850 are included.

When the execution terminal is designated, the execution terminal designation button 855 is selected, and a screen for inputting the designation of the execution terminal is displayed. The input file specification field 857 is a file required for scenario execution that is transmitted to the scenario execution terminal 4 when the task management unit 235 of the management apparatus 2 gives a scenario execution instruction, and is uploaded to the management apparatus 2 by the administrator terminal 3. You can specify a file.

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 an execution time setting field are displayed. If daily is selected, the run time setting fields are displayed, if weekly is selected, the day and run time setting fields are displayed, and if monthly is selected, the day and run time setting fields are displayed. However, when the end of the month is selected, a setting field for the number of days before the end of the month and the time is displayed.

When the schedule registration button 850 is selected after setting the information, 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. 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 the dashboard screen 86 and displays it on the administrator terminal 3 when the management information viewable is set in the administrator information specified by the user ID received from the administrator terminal 3. .. The dashboard screen 86 is a screen for displaying 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 tasks, a license information display area 865, and a floating license usage status. Display area 866 and a task being executed display area 867.

The dashboard icon 861 is an icon indicating normal, warning, or abnormal. The management information providing unit 238 displays an icon indicating normality when there is no scenario execution terminal 4 in a state where communication is interrupted or scenario execution is abnormally stopped, and when there is no task state that is abnormally terminated. The management information providing unit 238 displays an icon representing a warning when the scenario execution terminal 4 of communication interruption is present, and displays the scenario execution function ID of the scenario execution terminal 4 in the abnormality occurrence terminal display area 862. The management information providing unit 238 displays an icon indicating an abnormality when there is one or more task states in abnormal termination and the scenario execution terminal 4 in the state of communication interruption or scenario execution abnormal stop. The management information providing unit 238 causes the abnormality occurrence terminal display area 862 to display the scenario execution function ID of the scenario execution terminal 4 that is in the state of communication interruption or scenario execution abnormality stop, and causes the abnormality occurrence task display area 863 to end abnormally. Display the scenario name of the task that is set to.

The management information providing unit 238 processes the number of scenario execution terminals 4 (the number of registered terminals) to which the scenario execution function ID is assigned, the number of scenario execution terminals 4 in the activated state (the number of activated terminals), and the task state. Display area 864 showing the number of scenario executing terminals 4 in progress (the number of tasks being processed), the number of scenario executing terminals 4 in a task state of waiting (the number of waiting tasks), and the number of tasks completed from startup (total number of tasks) To display.

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

The management device 2 may provide a RESTful API as an API (Application Program Interface) for cooperating with other system-implemented terminals other than the administrator terminal 3. The other system implementation terminal that uses the RESTful API is a terminal that implements the function of the other system that the client arbitrarily decides to use. In the above description, the administrator terminal 3 uses the input screen received from the management device 2 to input various information for executing the task, sets the input information in the schedule registration request, and transmits it to the management device 2. doing. The other system mounting terminal generates a schedule registration request using the information obtained by executing the function of the mounted other system, and transmits the generated schedule registration request to the management device 2 using the RESTful API.

For example, the other system implementation terminal has a voice recognition system implemented, the voice recognition system accepts an order by the voice of the administrator, and transmits to the management device 2 a schedule registration request for immediately executing the scenario of the ordering business. Alternatively, the other system implementation terminal has an email analysis system implemented, and the email analysis system analyzes the email of the request for quotation sent from the administrator and requests the management apparatus 2 to execute a scenario for creating a quotation. To send. Further, the other system mounting terminal may transmit a management information display request to the management device 2 by using the RESTful API by using the information obtained by executing the function of the mounted other system. By providing the RESTful API, the management device 2 provides a standard management function service such as a task execution request and a monitoring request using the input and function (application) of another system that the client has decided to use. Moreover, it is possible to provide cooperation and expandability with other systems.

FIG. 18 is a diagram showing the configuration of the management device 2 using the public cloud. The cloud configuring the management device 2 is constructed using, for example, the resources of the web service (AWS) provided by Amazon.com. With the configuration shown in the figure, the management device 2 can provide the security equivalent to that of the virtual private cloud by separating the segment for each client. When the management device 2 receives an access from the administrator terminal 3 of each client by using https, it allocates this access to the subnet for each client, and then accesses the container for each client corresponding to the subnet (the allocation). Equivalent to the function of the minute part 22). This container (management function container) that implements 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 that server, the execution environment of the processing unit 23 is isolated for each client by a container. Then, by associating the container with the database of the client, the management device 2 can be implemented in 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 scenarios and data files to be distributed to the scenario execution terminal 4, and result files obtained by executing the tasks by the scenario execution terminal 4.

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

(3) Management execution mode function: The scenario execution terminal 4 is registered in the storage unit 43 of the scenario execution terminal 4 by registering the setting information that prohibits execution of scenarios other than the scenario received from the management apparatus 2 from being registered. 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. That is, the management device 2 allocates a task that causes the scenario execution terminal 4 in the standby state to execute a scenario according to the schedule information received from the administrator terminal 3. It is also possible to set the input parameters given to the task and the trigger for executing the task. For example, the scenario of business A can be executed every morning at 9:00, and the scenario of business B can be executed immediately.

(5) Scenario execution function management: The state of the scenario execution function of the scenario execution terminal 4 is managed, the task is assigned to the scenario execution terminal 4 in the standby state, and the task is put on standby if there is no scenario execution terminal 4 in the standby state.

(6) Group control function: The management device 2 can execute a scenario for each scenario in groups classified by the environment (affiliation, function, OS, etc.) of the scenario execution terminal 4. For example, when the email transmission function is used for the scenario of the job A, the management device 2 can select the scenario execution terminal 4 having the email transmission function and execute the scenario. Moreover, when the scenario of the job B operates only on a specific OS, the management device 2 can select the scenario execution terminal 4 using that OS and execute the scenario.

(7) Management target definition device function: The range of the management target can be defined by the administrator. For example, the administrator in charge of the general affairs department can execute the scenario on the scenario execution terminal 4 of the general affairs department, but cannot execute the scenario on the scenario execution terminals 4 of other departments. Similarly, the manager in charge of the accounting department can cause the scenario executing terminal 4 of the accounting department to execute the scenario, but cannot cause the scenario executing 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 the whole for a certain department.

(8) RESTful API cooperation function: The management device 2 provides a RESTful API for cooperation with a device that implements or uses the function of another system. This enables the task execution instruction and status monitoring 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 login/logout of administrative users, scenario registration/update, schedule registration/update/deletion/validation/invalidation, task execution triggers and results.

(11) Floating license management: Dynamically manage the number of licenses of the 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, the 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 by a computer system and executed. The “computer system” mentioned here includes an OS and hardware such as peripheral devices. The "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, the "computer-readable recording medium" means to hold a program dynamically for a short time like a communication line when transmitting the program through a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory inside a computer system that serves as a server or a client in that case may hold a program for a certain period of time. Further, the program may be for realizing a part of the above-described functions, and may be a program for realizing the above-mentioned functions 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 unit and a schedule registration unit. The scenario registration unit registers scenario information, which is data indicating a processing procedure, and scenario information indicating an attribute of a scenario execution terminal that executes the scenario, in the management device. The scenario information may include information that identifies other scenario information in which the scenario before update 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 unit, an instruction reception unit, a scenario execution unit, and an execution result notification unit. The notification unit notifies the management device of the state of its 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 the reception of the scenario execution instruction. The execution result notifying unit notifies the management device of the scenario execution result by the scenario executing unit. The scenario execution terminal may further include a scenario execution permission unit that controls whether to permit execution of a scenario other than the scenario received from the management device.

The management device includes a storage unit, a scenario management unit, a state management unit, a task management unit, and an execution result reception unit. The storage unit stores terminal management information indicating attributes of the scenario execution terminal. For example, the attribute includes at least one of the organization to which the scenario execution terminal belongs, the function of the scenario execution terminal, 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 the state management information indicating the state notified from the scenario execution terminal in the storage unit. The notified 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 in the status management information among the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information. A scenario execution terminal, which is shown to be in this state, is selected as a task allocation destination, and a task and a scenario execution instruction are transmitted 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 statistic calculation unit that calculates statistics related to the state of the scenario execution terminal.

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

The management device is connected to the administrator terminal and the scenario execution terminal of each of a plurality of clients, and the processing of the scenario management unit, the state management unit, and the task management unit is a container that is an execution environment of these processes divided for each client. Run by. Further, the management device has a storage unit for each client. The container can access the storage unit corresponding to the same client as the container.

Further, the management device may have an application program interface (API) for receiving schedule information from a terminal that implements an arbitrary function, instead of the administrator terminal. The terminal generates schedule information using the information obtained by executing an arbitrary function that is implemented, and transmits the generated schedule information to the management device using the API.

Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and includes a design and the like within a range not departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1... Scenario execution system, 2... Management device, 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 receiving unit, 237... Log generation unit , 238... Management information providing section, 239... Storage control section, 341... Scenario creation section, 342... Scenario registration section, 343... Schedule registration section, 344... Display control section, 441... Notification section, 442... Instruction receiving section, 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 (13)

A scenario execution system having an administrator terminal, a scenario execution terminal, and a management device,
The administrator terminal is
A scenario registration unit that registers scenario information, which is data indicating a processing procedure, and scenario information indicating attributes of the scenario execution terminal that executes the scenario, in the management device.
A schedule registration unit that registers schedule information indicating execution timing of the scenario in the management device,
The scenario execution terminal is
A notification unit that notifies the management device of the state of its own terminal every predetermined time,
An instruction receiving unit that receives the scenario and the 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 notifying unit for notifying the management device of the execution result of the scenario by the scenario executing unit,
The management device is
A storage unit that stores terminal management information indicating attributes of the scenario execution terminal;
A scenario management unit that registers the scenario information and the schedule information received from the administrator terminal in the storage unit;
A status management unit that writes status management information indicating the status notified from the scenario execution terminal to the storage unit;
At the execution timing of the scenario indicated by the schedule information, of the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information, the scenario is executed in the state management information. A task management unit that selects the scenario execution terminal that is shown to be in a possible state as a task allocation destination, and performs task allocation that transmits the scenario and the scenario execution instruction to the selected task allocation destination. ,
An execution result receiving unit that receives an execution result of the scenario from the scenario execution terminal,
Scenario execution system. The scenario execution terminal further includes a scenario execution permission unit that controls whether or not to permit execution of a scenario other than the scenario received from the management device,
The scenario execution system according to claim 1. The management device is connected to the administrator terminal and the scenario execution terminal of each of a plurality of clients, and performs the processing of the scenario management unit, the status management unit, and the task management unit for each of the clients. It is executed by a container which is an execution environment, and has the storage unit for each client,
The container can access the storage unit corresponding to the same client as the container.
The scenario execution system according to claim 1 or 2. The management device has an application program interface for receiving the schedule information from a terminal that implements an arbitrary function, 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 3. A storage unit that stores terminal management information indicating attributes of the scenario execution terminal,
A scenario which is data indicating a processing procedure, scenario information indicating an attribute of the scenario execution terminal that executes the scenario, and schedule information indicating an execution timing of the scenario are received from the administrator terminal and stored in the storage unit. The scenario management section to register,
A status management unit that receives a status notification from the scenario execution terminal at predetermined time intervals and writes status management information indicating the notified status to the storage unit,
At the execution timing of the scenario indicated by the schedule information, of the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information, the scenario is executed in the state management information. A task management unit that selects the scenario execution terminal indicated as being in a possible state as a task allocation destination, and transmits 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,
A management device including. The attribute includes at least one of an organization to which the scenario execution terminal belongs, a function of the scenario execution terminal, and an execution environment of the function in the scenario execution terminal.
The management device according to claim 5. The state notified from the scenario execution terminal to which the task is assigned includes information on the execution state of the scenario,
The management device according to claim 5 or 6. Further comprising a statistic calculation unit that calculates statistics regarding the state of the scenario execution terminal,
The management device according to any one of claims 5 to 7. The storage unit further stores management target information indicating the scenario execution terminal managed by the administrator,
The scenario information includes information about an administrator,
The task management unit, 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 the information included in the scenario information. Of the scenario execution terminals indicated by the management target information as being managed by the administrator, the status execution information indicates that the scenario execution terminal indicates that the scenario can be executed. Selected as the assignee of
The management device according to any one of claims 5 to 8. The scenario information includes information specifying other scenario information in which the scenario before update is set,
The management device according to any one of claims 5 to 9. A scenario execution management method in a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device,
The administrator terminal is
A scenario registration step of registering scenario information, which is data indicating a processing procedure, and scenario information indicating an attribute of the scenario execution terminal that executes the scenario in the management device;
A schedule registration step of registering schedule information indicating execution timing of the scenario in the management device;
The scenario execution terminal is
A notification step of notifying the management device of the state of its own terminal every predetermined time,
An instruction receiving step of receiving the scenario and the 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 notifying step of notifying the management device of the execution result of the scenario by the scenario executing step,
The management device is
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 the scenario execution terminal,
A status management step of writing status management information indicating the status notified from the scenario execution terminal to the storage unit,
At the execution timing of the scenario indicated by the schedule information, of the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information, the scenario is executed in the state management information. A task management step of selecting the scenario execution terminal indicated as being in a possible state as a task allocation destination, and performing task allocation for transmitting the scenario and the scenario execution instruction to the selected task allocation destination. ,
An execution result receiving step of receiving an execution result of the scenario from the scenario execution terminal,
A method for managing scenario execution having: A scenario execution management method in the management device of a scenario execution system having an administrator terminal, a scenario execution terminal, and a management device,
The scenario, which is the data indicating the processing procedure, the scenario information indicating the attribute of the scenario executing terminal that executes the scenario, and the schedule information indicating the execution timing of the scenario are received from the administrator terminal, and the scenario is received. A scenario management step of registering in a storage unit that stores terminal management information indicating attributes of execution terminals;
A status management step of receiving a status notification from the scenario execution terminal at predetermined time intervals and writing status management information indicating the notified status to the storage unit,
At the execution timing of the scenario indicated by the schedule information, of the scenario execution terminals in which the attribute set in the scenario information of the scenario is set in the terminal management information, the scenario is executed in the state management information. A task management step of selecting the scenario execution terminal indicated as being in a possible state as a task allocation destination, and transmitting the scenario and the scenario execution instruction to the selected task allocation destination.
An execution result receiving step of receiving an execution result of the scenario from the scenario execution terminal,
A method for managing scenario execution having: Computer,
A program for causing the management apparatus according to any one of claims 5 to 10 to function.

Images