JP2014115892A - Operation automation support system, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technology for performing list display of components matched with a purpose from a large number of components provided on an RBA tool.SOLUTION: An operation information table which associates and stores component name of an RBA tool and operation information made of a plurality of parameters, and an input of retrieval information which specifies a range of the plurality of parameters are received. The component name and operation information are extracted by retrieving an operation information table with the retrieval information whose input is received. List display information 1030 which is made of the extracted component name and operation information is displayed.

Description

  The present invention relates to an operation automation support system and method, and a program.

  In recent years, it has become possible to automate the operation of the system by means of RBA (Run Book Automation). An RBA tool for automating system operation has a huge number of operation procedure flows and operation operations (hereinafter, components) in order to automate various operations.

  As a background art of this technical field, there is JP 2011-159131 A (Patent Document 1). This gazette states that “a scenario that combines a series of work items based on a work procedure manual and a time associated with the execution of a scenario is combined with information including a computer that performs the work based on the scenario. There is provided means for registering in a system (for example, a server) and performing work related to the time according to, for example, automatic navigation from the system side.

JP 2011-159131 A

  In Patent Document 1, it is possible to improve work quality at the operation site, reduce work man-hours, and the like. However, with the technique described in Patent Document 1, it is not possible to display a list of parts that meet the purpose from among the enormous number of parts that the RBA tool has.

  An object of the present invention is to provide a technique for displaying a list of parts that meet the purpose from among a large number of parts of the RBA tool.

  The above and other objects and novel features of the present invention will be apparent from the description of this specification and the accompanying drawings.

  Of the inventions disclosed in the present application, the outline of typical ones will be briefly described as follows.

  The present invention has an operation information table that stores a part name of an RBA tool and operation information including a plurality of parameters in association with each other. And accepting input of search information that specifies a plurality of the parameter ranges, extracting the part name and the operation information by searching the operation information table with the search information that received the input, the extracted The above-mentioned problem is solved by having a part selection unit that displays a list of part names and the operation information.

  In addition, the present invention is a method using a system for displaying a list of parts that match a purpose from among the enormous number of parts that the RBA tool has, and a method that meets the purpose from the enormous number of parts that the RBA tool has. The present invention can also be applied to a program that causes a computer to function as a system for displaying a list of parts.

  Among the inventions disclosed in the present application, effects obtained by typical ones will be briefly described as follows.

  According to the present invention, it is possible to display a list of parts that meet the purpose from among a huge number of parts that the RBA tool has.

It is a figure which shows the outline | summary of the structural example of the operation automation assistance system in one embodiment of this invention. It is a figure which shows the example of a structure of components in the operation automation assistance system of FIG. FIG. 2 is a diagram illustrating a configuration example of a component information table stored in a component management DB in the operation automation support system of FIG. 1. FIG. 2 is a diagram illustrating a configuration example of an operation information table stored in an operation information DB in the operation automation support system of FIG. 1. FIG. 2 is a diagram illustrating a configuration example of an execution information table stored in an operation information DB in the operation automation support system of FIG. 1. FIG. 3 is a diagram illustrating a configuration example of a template management table stored in a template management DB in the operation automation support system of FIG. 1. FIG. 2 is a diagram illustrating an example of a processing flow of component execution processing in the operation automation support system of FIG. 1. FIG. 2 is a diagram illustrating an example of a processing flow of operation information registration processing in the operation automation support system of FIG. 1. FIG. 2 is a diagram illustrating an example of a processing flow of component search processing in the operation automation support system of FIG. 1. FIG. 2 is a diagram showing an example of a template registration screen in the operation automation support system of FIG. 1. In the operation automation support system of FIG. 1, it is a figure which shows the example of a template selection screen. FIG. 2 is a diagram illustrating an example of a part search screen in the operation automation support system of FIG. 1.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

<System configuration>
FIG. 1 is a diagram showing an outline of a configuration example of an operation automation support system according to an embodiment of the present invention. In FIG. 1, the operation automation support system includes, for example, an RBA tool 101, a component management DB (Database) 102, an operation target device 103, an operation information DB 104, a component creation tool 105, a component selection unit 106, and a template management DB 107.

  The operation automation support system is implemented by predetermined hardware and software. For example, the operation automation support system includes a processor, a memory, and the like, and by executing a program on the memory by the processor, the RBA tool 101, the component management DB 102, the operation target device 103, the operation information DB 104, the component creation tool 105, and the component selection. Unit 106 and template management DB 107 are realized, and the computer functions as an operation automation support system.

  The RBA tool 101 is a tool for executing a component stored in the component management DB 102. When the RBA tool 101 executes the part, the operation procedure defined for the part is executed for the operation target device 103.

  The operation information DB 104 stores an operation information table 400 and an execution information table 500.

  The component creation tool 105 is a tool for the operation component developer to edit the component.

  The component selection unit 106 accepts input of search information for specifying a parameter range from a component search screen 1200 (described later, FIG. 10). Further, the part selection unit 106 extracts the part name and the operation information by searching the operation information table 400 with the search information that has received the input. Then, the part selection unit 106 displays the extracted part name and operation information.

  The template management DB 107 stores search information for searching for parts as a template.

<Detailed configuration>
FIG. 2 is a diagram illustrating a configuration example of components in the operation automation support system of FIG. “XX center-ΔΔ business- □□ operation component” is composed of component A, component B, component C, and component D. The part A is composed of the parts A1, A2, and A3, the part B is composed of the parts B1, B2, and B3, the part C is composed of the parts C1, C2, and C3, and the part D is It consists of a part D1, a part D2, and a part D3.

  FIG. 3 is a diagram showing a configuration example of the component information table 300 stored in the component management DB 102 in the operation automation support system of FIG. The component information table 300 includes data items such as [component ID], [component name], [keyword], and [path]. [Part ID] indicates a symbol for identifying the part. [Part Name] indicates the name of the part. [Keyword] indicates a keyword for specifying the use of the part. [Path] indicates the location of the part.

  FIG. 4 is a diagram showing a configuration example of the operation information table 400 stored in the operation information DB 104 in the operation automation support system of FIG. The operation information table 400 includes [part ID], [part name], [latest execution date], [execution count], [error count], [average execution time], [average recovery time], [average failure interval], etc. Contains data items. [Latest execution date / time] indicates a time when the component corresponding to the component ID is normally terminated as a result of executing the component corresponding to the component ID, and the normal termination time closest to the current time. [Number of executions] indicates the number of times the part corresponding to the part ID is executed. [Number of errors] indicates the number of times of abnormal termination when the component corresponding to the component ID is executed. [Average execution time] indicates an average execution time when the component corresponding to the component ID is normally terminated as a result of executing the component. [Average recovery time] indicates the average time from the time when the part corresponding to the part ID is executed to the time when the part is abnormally terminated until it is executed again. The “average failure interval” indicates an average time from the time when the part corresponding to the part ID is executed to the time when it abnormally ends to the time when it abnormally ends again.

  FIG. 5 is a diagram showing a configuration example of the execution information table 500 stored in the operation information DB 104 in the operation automation support system of FIG. The execution information table 500 includes data items such as [execution ID], [part ID], [part name], [start time], [end time], [execution time], [result], and [parent part ID]. Including. [Execution ID] indicates an ID assigned each time a part is executed. [Start time] indicates the time when the execution of the component corresponding to the component ID is started. [End time] indicates the time when the execution of the component corresponding to the component ID is ended. [Execution time] indicates the time from the start to the end of the execution of the component corresponding to the component ID. [Result] indicates whether the component has been normally terminated or abnormally terminated. [Parent part ID] indicates a part ID including a part corresponding to the part ID.

  FIG. 6 is a diagram showing a configuration example of the template management table 600 stored in the template management DB 107 in the operation automation support system of FIG. The template management table 600 includes [template ID], [template name], [keyword], [creation date / time], [update date / time] and search information ([operation rate lower limit], [operation rate upper limit], [latest execution date / time]. , Execution frequency lower limit, Execution frequency upper limit, Average execution time lower limit, Average execution time upper limit, Average recovery time lower limit, Average recovery time upper limit, Average failure interval lower limit, [Average failure interval upper limit], [Error count lower limit], and [Error count upper limit]) are stored in association with each other.

  [Template ID] indicates a symbol for identifying a template. [Template name] indicates the name of the template. [Creation date] indicates the date and time when the template was created. [Update date and time] indicates the date and time when the created template was subsequently updated. [Occupancy rate lower limit] indicates the lower limit of the operation rate. [Upper limit of operating rate] indicates the upper limit of the operating rate. [Latest execution date and time] indicates the date and time when the search information corresponding to the template was most recently executed. [Lower execution count] indicates the lower limit of the execution count. [Maximum number of executions] indicates the upper limit of the number of executions. [Average execution time lower limit] indicates the lower limit of the average execution time. [Average execution time upper limit] indicates the upper limit of the average execution time. [Lower average recovery time] indicates the lower limit of average recovery time. [Average recovery time upper limit] indicates the upper limit of average recovery time. [Average failure interval lower limit] indicates the lower limit of the average failure interval. [Average failure interval upper limit] indicates the upper limit of the average failure interval. [Lower limit of error count] indicates the lower limit of the error count. [Error count upper limit] indicates the upper limit of error count.

<Example of response screen (1): Template registration screen>
FIG. 10 shows an example of the template registration screen 1000. The template registration screen 1000 includes [template name], [keyword] and search information ([operation rate lower limit], [operation rate upper limit], [latest execution date / time], [execution frequency lower limit], [execution frequency upper limit], [ [Average execution time lower limit], [Average execution time upper limit], [Average recovery time lower limit], [Average recovery time upper limit], [Average failure interval lower limit], [Average failure interval upper limit], [Error count lower limit], [Error count] [Upper limit]) displays a text box to accept input.

  When the operation of the “Register” button 1050 is accepted, the information accepted from the text box is stored in the template management table 600.

  When an operation of the “reference” button 1040 is accepted, a template selection screen 1100 (described later, FIG. 11) is displayed.

<Example of response screen (2): Template selection screen>
FIG. 11 shows an example of the template selection screen 1100. The template selection screen 1100 displays a template list 1060 that displays a list of [template ID], [template name], [creation date / time], and [update date / time] stored in the template management table 600.

  In the template selection screen 1100, selection of one template from the templates displayed in the template list 1060 is accepted.

  When an operation on the “return” button 1080 is accepted, a template registration screen 1000 is displayed.

  Also, when an operation on the “select” button 1070 is accepted, a template registration screen 1000 in which the information of the template accepted for selection is reflected in a text box is displayed.

<Example of response screen (3): Parts search screen>
FIG. 12 shows an example of the component search screen 1200. The parts search screen 1200 displays a list box 1010 that receives a template name selection, a text box 1020 that receives an input of a keyword, and a text box that receives an input of search information. Furthermore, the parts search screen 1200 includes [part ID], [part name], [path], [latest execution date / time], [operation rate], [execution count], [error count], [average execution time], List display information 1030 for displaying a list of information on data items such as [average recovery time] and [average failure interval] is displayed.

<Process (1): Parts search process>
FIG. 9 is a diagram illustrating an example of a processing flow of component search processing in the present system.

  First, in step S <b> 801, the component selection unit 106 determines whether a template name selection has been received from the operator from the list box 1010 displayed on the component search screen 1200. When it is determined that the template name has been selected from the operator from the list box 1010 (S801-Yes), the process proceeds to S802.

  In step S802, the component selection unit 106 searches the template management table 600 using the template name accepted in step S801 as a key, and searches for a [keyword] corresponding to the template name and search information ([operation rate lower limit], [Upper limit of operation rate], [Latest execution date], [Lower execution count], [Upper execution count], [Lower average execution time], [Upper average execution time], [Lower average recovery time], [Upper average recovery time] ], [Average failure interval lower limit], [Average failure interval upper limit], [Error count lower limit], [Error count upper limit]).

  In step S803, the component selection unit 106 reflects the [keyword] acquired in step S802 on the component search screen (described above, FIG. 12), reflects the search information in each parameter, and proceeds to step S805.

  On the other hand, when the component selection unit 106 determines in S801 that the selection of the template name from the list box 1010 is not accepted from the operator (S801-No), the process proceeds to S804.

  In step S804, the component selection unit 106 directly receives input of keywords and search information from the component search screen by an operation of the operator, and the process advances to step S805.

  In step S <b> 805, the component selection unit 106 accepts an operation for the “search” button by an operation of the operator from the component search screen, and the process advances to step S <b> 806.

  Next, in S806, the part selection unit 106 searches the operation information table 400 based on the search information that has received the input, thereby operating information ([part ID], [latest execution date], [number of executions]). , [Error count], [Average execution time], [Average recovery time], [Average failure interval]) and [Part name] corresponding to the operation information.

  In step S807, the component selection unit 106 searches the component information table 300 using the [component name] and [keyword] acquired in step S806 as keys to correspond to [component name] and [keyword] [ Get [path].

  Next, in S808, the component selection unit 106 calculates [operation rate] for each [component name] based on the operation information acquired in S806. [Occupancy rate] is calculated by dividing [Average failure interval] by a value obtained by adding [Average recovery time] and [Average failure interval].

  Next, in S809, the parts selection unit 106 merges the [part name] and the operation information acquired in S806, the [path] acquired in S807, and the [operation rate] calculated in S808. Generate merge information.

  In step S <b> 810, the component selection unit 106 generates list display information 1030 by sorting the merged information so that [part name] having a higher operation rate is displayed at the top of the list.

  Finally, in S811, the component selection unit 106 displays the list display information 1030 generated in S810 and ends the process.

<Process (2): Component execution process>
FIG. 7 is a diagram illustrating an example of a processing flow of component execution processing in the present system.

  First, in S701, the RBA tool 101 automatically searches the component information table 300 stored in the component management DB 102 using the self component name registered in the scheduler as a key, thereby automatically [path] corresponding to the component name. Acquire and go to S703. Alternatively, by receiving an input of a component name from the operator to the component creation tool 105 in S702, the component information table 300 stored in the component management DB 102 is searched using the input component name as a key, so that the component name is obtained. The corresponding [path] is acquired, and the process proceeds to S703.

  In step S <b> 703, the RBA tool 101 acquires a part stored in the [path] acquired in step S <b> 701 or S <b> 702. The RBA tool 101 operates the operation target device 103 by executing a flow and an operation operation defined in the acquired component.

  In step S <b> 704, the RBA tool 101 performs operation information registration processing (described later in FIG. 8), and ends the component execution processing.

<Process (3): Operation information registration process>
FIG. 8 is a diagram showing an example of a processing flow of operation information registration processing in this system.

  First, in S712, the RBA tool 101 determines whether or not the operation executed in S703 by the flow or operation operation has been normally completed. When the RBA tool 101 determines that the operation is normally completed (S712-Yes), the process proceeds to S713.

  Next, in S713, the RBA tool 101 stores [execution ID], [part ID], [start time], [end time] in the execution information table 500 based on [part name] and the execution content of S703. Execution information including data items such as [execution time], [result], and [parent component ID] is stored.

  Next, in S714, the RBA tool 101 operates the operation information ([Part ID], [Latest execution date / time], [Execution count], [Error count] in the operation information table 400 corresponding to [Part name] executed in S703. ], [Average execution time], [Average recovery time], [Average failure interval]) are updated based on the execution contents of S703, and the process is terminated.

  On the other hand, when the RBA tool 101 determines that the operation is not normally completed in S712 (S712-No), the process proceeds to S715.

  Next, in S715, the RBA tool 101 stores [execution ID], [part ID], [start time], [end time] based on [part name] in the execution information table 500 and the execution content of S703. Execution information including data items such as [execution time], [result], and [parent component ID] is stored.

  Next, in S716, the RBA tool 101 updates [Execution count] and [Error count] in the operation information table 400 corresponding to the part name executed in S703.

  Next, in S717, the part creation tool 105 accepts correction of an abnormal part of the part from the operator.

  Next, in S718, the operation target device 103 is operated by executing a flow and an operation operation defined in the corrected part corrected in S717.

  Next, in S719, the RBA tool 101 determines whether or not the operation by the flow or operation operation executed in S718 has ended normally. When the RBA tool 101 determines that the operation is normally completed (S719-Yes), the process proceeds to S720. On the other hand, when the RBA tool 101 determines that the operation is not normally completed in S719 (S719-No), the process proceeds to S715.

  Next, in S720, the RBA tool 101 stores [execution ID], [part ID], [start time], [end time] in the execution information table 500 based on [part name] and the execution content of S718. Execution information including data items such as [execution time], [result], and [parent component ID] is stored.

  Next, in S721, the RBA tool 101 updates the operation information in the operation information table 400 corresponding to [part name] executed in S718 based on the execution contents of S718, and ends the processing (S722).

  Here, in the operation automation support method and program of the present invention, S714 corresponds to a storage step, S801 and S804 correspond to a search information input reception step, S806 corresponds to a search step, and S811 corresponds to a list display step. To do.

<Effects of the present embodiment>
According to the operation automation support system in the present embodiment described above, the extracted part name and operation information are retrieved by searching the operation information table 400 using the search information that has received the input, and extracting the part name and operation information. Can be displayed in a list.

  In addition, it has a parts information table 300 that stores a keyword for specifying the use of a part and a part name in association with each other. By searching the part information table 300 using a keyword, a part name corresponding to the keyword can be extracted. It becomes like this.

  In addition, by calculating the operation rate based on the average recovery time and average failure interval included in the operation information, and sorting in the order of the calculated operation rate, it is possible to display a higher-level list of parts with higher operation rates and operation information. become.

  As mentioned above, although the invention made | formed by this invention was concretely demonstrated based on embodiment, this invention is not limited to the said embodiment, It can change variously in the range which does not deviate from the summary. Needless to say.

  The present invention has an excellent effect of being able to display a list of parts that meet a purpose from among a huge number of parts that the RBA tool 101 has, and can also be applied to an operation automation support system, method, and program.

101 RBA tool 102 Parts management DB
103 Operation target device 104 Operation information DB
105 Part creation tool 106 Part selection unit 107 Template management DB
300 parts information table 400 operation information table 500 execution information table 600 template management table 1000 template registration screen 1010 list box 1020 text box 1030 list display information 1040 “reference” button 1050 “registration” button 1060 template list 1070 “select” button 1080 “ Back button 1100 Template selection screen 1200 Parts search screen

Claims (5)

An operation information table for storing RBA tool component names and operation information including a plurality of parameters in association with each other;
Accepting input of search information specifying a plurality of parameter ranges, extracting the part name and the operation information by searching the operation information table with the search information that has received the input, and extracting the part name And a parts selection unit for displaying a list of the operation information. In the operation automation support system according to claim 1,
The operation automation support system further includes a component information table for storing the component name and a keyword for specifying the use of the component in association with each other,
The part selection unit accepts input of the keyword, extracts the part name corresponding to the keyword that has received the input from the part information table, and searches the operation information table with the extracted part name. The operation information is extracted, and the part name extracted from the part information table and the operation information extracted from the operation information table are displayed in a list. In the operation automation support system according to claim 1 or 2,
The component selection unit calculates an operation rate based on an average recovery time and an average failure interval included in the operation information acquired from the operation information table, and sorts the operation information and the operation in the order of the calculated operation rate. An operation automation support system that displays a list of the component names corresponding to information. A storage step of storing RBA tool component names and operation information including a plurality of parameters in association with each other by the RBA tool;
A search information input receiving step for receiving input of search information for specifying a plurality of ranges of the parameters from the part search screen;
A search step of extracting the part name and the operation information by searching the information stored in the storage step with the search information received in the search information input reception step by a component selection unit;
An operation automation support method, comprising: a list display step of displaying a list of the component name and the operation information extracted in the search step by the component selection unit. A program for causing a computer to function as an operation automation support system,
A storage step of storing RBA tool component names and operation information including a plurality of parameters in association with each other by the RBA tool;
A search information input receiving step for receiving input of search information for specifying a plurality of ranges of the parameters from the part search screen;
A search step of extracting the part name and the operation information by searching the information stored in the storage step with the search information received in the search information input reception step by a component selection unit;
A program for causing the computer to execute a list display step of displaying a list of the component name and the operation information extracted in the search step by the component selection unit.

Images