JP5974875B2 - Related estimation program, related estimation device, and related estimation method - Google Patents

Description

  The present invention relates to a relation estimation program, a relation estimation apparatus, and a relation estimation method for estimating a relation between elements constituting an IT (Information Technology) system.

  One of the operational tasks in the IT system is a change release task. The change release work is a work to make a partial change of the operating system. Examples of the change release work include a work for changing a device or an application by recovering from a failure or adding a function.

  In change release work, the work procedure differs depending on the device and application to be released. Therefore, it is necessary to determine the devices and applications to be stopped / started and the stop / start order for each release target.

  Conventionally, review of work procedures in change release work has been done manually. The devices / applications to be stopped / started and their stop / start order are manually created and checked in consideration of the system connection and dependency.

  A technique is known that searches for a connection in the system schema between two input elements and acquires a dependency relationship between the configurations of the network system. The system schema is an information model that describes system components and the relationships between the system components.

Japanese Patent No. 4175280

  As described above, when a work procedure is manually created, there is a problem that it takes time to create the procedure. In addition, there is a problem that mistakes are likely to occur in manual work confirmation. Because of these problems, it is desired that work procedures are automatically generated by a computer.

  The devices / applications to be stopped / started and their stopping / starting order are determined by the connection relationship, dependency relationship, etc. in the work target system. Therefore, when the work procedure is automatically generated by the computer, the system configuration information of the work target system is required. The system configuration information includes information on each element that constitutes a system such as a device or an application, and information related to each element such as a connection relationship and a dependency relationship. In the automatic generation of the work procedure, the work procedure is generated from the system configuration information of the work target system.

  When automatic generation of work procedures is applied to a newly developed system, system configuration information having information necessary for automatic generation of work procedures may be created at the time of new development of the system.

  When automatic generation of work procedures is introduced into an existing system that is already in operation, information on each element that makes up the system can be easily obtained from a design document or CMDB (Configuration Management Database). . However, it is difficult to obtain the related information between each element because the information is not clearly described in the document or the information is distributed in a plurality of documents and setting files. In order to introduce automatic generation of work procedures into an existing system that is already in operation, it is necessary to acquire relevant information between each element in the work target system.

  In one aspect, an object of the present invention is to provide a technique for estimating a relationship between components in an IT system.

  In one aspect, the disclosed program causes a computer to function as follows. That is, the program is configured from hardware or software elements by obtaining a first work procedure indicating the order of operations performed on a work target system in a computer on which the program is installed and executed. A second work procedure having the same purpose as the first work procedure is automatically generated from information indicating the relation between elements in the work target system in accordance with information in which the correspondence between the elements in the system and the work procedure is defined. In the work target system, a work procedure that is a difference between the first work procedure and the second work procedure is extracted, and a work procedure that becomes a difference is generated using the information that defines the correspondence. Causes the process to identify the relationship between elements to be executed.

  In one aspect, it is possible to estimate the relationship between components in the IT system.

It is a figure explaining the example of the IT system of the object which produces | generates a work procedure. It is a figure which shows the example of the operation procedure production | generation rule used when producing | generating a work procedure automatically with a computer. It is a figure explaining the example of the automatic production | generation of a work procedure. It is a figure which shows the example of the work procedure produced | generated automatically. It is a procedure production | generation process flowchart by this Embodiment. It is a figure which shows the structural example of the related estimation apparatus by this Embodiment. It is a figure which shows the hardware structural example of the computer which implement | achieves the related estimation apparatus by this Embodiment. It is a figure which shows the structural example (1) of the work target system by a present Example. It is a figure which shows the example (1) of the existing procedure manual by a present Example. It is a figure which shows the example of the work content management table by a present Example. It is a figure which shows the example (1) of the existing procedure data by a present Example. It is a figure which shows the example (1) of the automatic production | generation procedure data by a present Example. It is a figure which shows the example (1) which represented the flow of the existing procedure and automatic generation procedure by a present Example with a graph. It is a figure which shows the example of the intermediate data for difference extraction by a present Example. It is a figure which shows the example (1) of a result table by a present Example. It is a figure which shows the example (1) of the work procedure used as the difference by a present Example. It is a figure which shows the example (2) of a result table by a present Example. It is a figure which shows the example (3) of a result table by a present Example. It is a figure which shows the structural example (2) of the work target system by a present Example. It is a figure which shows the example (2) of the existing procedure manual by a present Example. It is a figure which shows the example (2) of the existing procedure data by a present Example. It is a figure which shows the example (2) of the automatic generation procedure data by a present Example. It is a figure which shows the example (2) which represented the flow of the existing procedure and automatic generation procedure by a present Example with a graph. It is a figure which shows the example (2) of the work procedure used as the difference by a present Example. It is a figure which shows the example (4) of a result table by a present Example. It is a figure which shows the structural example (3) of the work target system by a present Example. It is a related estimation process flowchart by the related estimation apparatus of this Embodiment. It is a related specific process flowchart by the specific part of this Embodiment. It is a result determination process flowchart by the update part of this Embodiment. It is a figure which shows the structural example of the related estimation apparatus by this Embodiment. It is a figure which shows the example of a definition which has the hierarchical structure regarding the content of the work | work operated in an example of the production | generation process of a work procedure. It is a figure which shows the example of the element information in an example of the production | generation process of a work procedure. It is a figure which shows the example of the relevant information in an example of the production | generation process of a work procedure. It is a figure which shows the example of the work expansion | deployment rule in an example of the production | generation process of a work procedure. It is a figure which shows the example of the procedure expansion rule in an example of the production | generation process of a work procedure. It is a figure which shows the example of the procedure rewriting rule in an example of the production | generation process of a work procedure. It is a figure for demonstrating "LayerUp" of a procedure rewriting rule. It is a figure which shows the example of a structure of the work target system in the specific example of the production | generation process of a work procedure, and the example of information. It is a figure which shows the example (1) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (2) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (3) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (4) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (5) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (6) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example (7) of the tree structure produced | generated during a production | generation process. It is a figure which shows the example of the work procedure produced | generated in one specific example of the production | generation process of a work procedure. It is a figure which shows the example of the process flow in one specific example of the production | generation process of a work procedure.

  Hereinafter, the present embodiment will be described with reference to the drawings.

  First, an example of a proposed technique will be described as a technique for automatically generating a work procedure in an operation work such as a change release work for an IT system by a computer. The work procedure indicates the order of operations performed on the work target system in order to realize the intended work content. The work contents indicate the contents of work to be performed, such as “stop AP server”, “start WEB server”, and the like.

  FIG. 1 is a diagram for explaining an example of an IT system that generates a work procedure.

  The work target system shown in FIG. 1A shows an example of an IT system that is a target for generating a work procedure. The work target system is composed of hardware elements such as servers and software elements such as applications. In the work target system shown in FIG. 1A, squares represent hardware elements, and rounded squares represent software elements. Hereinafter, the IT system is also simply referred to as a system.

  In the work target system shown in FIG. 1A, “WEB Server” and “AP Server” are servers. As shown in FIG. 1A, “WEB Server” and “AP Server” are connected to each other. “WEB Server” is connected to the external “Internet”.

  In the work target system shown in FIG. 1A, “AplA”, “AplB”, and “AplC” are applications. As shown in FIG. 1A, “AplA” and “AplC” operate on “WEB Server”. “AplB” is running on “AP Server”. In FIG. 1A, bold arrows indicate data access relationships between applications. In the work target system shown in FIG. 1A, there is data access from “AplC” to “AplA” and data access from “AplA” to “AplB”.

  FIGS. 1B and 1C show an example of system configuration information of the work target system shown in FIG. The system configuration information includes information on each element constituting the system and information indicating a relationship between each element. The element information 120 shown in FIG. 1B shows an example of information on each element constituting the system in the system configuration information. The related information 121 shown in FIG. 1C shows an example of information indicating the relation between each element.

  Element information 120 shown in FIG. 1B has element, type, name, and notation information. The element indicates whether the element of the corresponding record is a hardware element or a software element. The type is information for classifying the type of element, such as a server, a load balancer (LB), and an application. The name indicates the name given to the element of the corresponding record. The notation indicates the notation on the data of the element of the corresponding record. In the data of the present embodiment, each element constituting the system is expressed in a markup format using tags. In the element information 120 shown in FIG. 1B, <Server> </> tags represent server elements, and <Application> </> tags represent application elements.

  The related information 121 shown in FIG. 1C has type, related source, and related destination information. The type is information that classifies the type of association between elements. Relation source and relation destination indicate related elements. In the related information 121 shown in FIG. 1C, for example, when the type of the relation is “data access”, the relation source indicates an application that performs data access, and the relation destination receives data access from the relation source application. Indicates an application. Further, for example, when the relation type is “server / application relation”, it indicates that the relation destination application operates on the relation source server. Further, for example, when the relation type is “server relation”, the connection relation between the relation source server and the relation destination server is indicated.

  FIG. 2 is a diagram illustrating an example of operation procedure generation rules used when a work procedure is automatically generated by a computer.

  When the work procedure is automatically generated by the computer, a rule for deriving the work procedure from the system configuration information of the work target system is necessary. The operation procedure generation rule 150 shown in FIG. 2 shows an example of rule information in which the association between elements in the system and the correspondence between work procedures are defined.

  The operation procedure generation rule 150 shown in FIG. 2 has a rule ID, work contents, related information between elements, and information on operations to be performed. The rule ID is identification information that identifies a defined rule. In the operation procedure generation rule 150 shown in FIG. 2, one record indicates one rule, and a rule ID is assigned to each record.

  The work content is information indicating the content of the target work such as “stop AP server”, “start WEB server”, for example, in the rule of the corresponding record. The work contents further have information on work objects and work items. The work target indicates an element that is a target of the work to be performed. The work item indicates work to be performed such as “start”, “stop”, and the like.

  The relationship information between elements is information indicating a condition regarding the relationship between elements in the rule of the corresponding record. The related information between elements further includes type and related information. The type is information for classifying the type of association between elements, similar to the type in the related information 121 shown in FIG. Association indicates the relationship between elements. In the operation procedure generation rule 150 shown in FIG. 2, for example, the relation “<Application> Aplα → Apl β </>” in the rule ID “R1” is the origin of the application “Apl α”, and the application “Apl β” is It shows that it is related.

  The operation to be performed is information indicating the order in which the element to be operated is operated in the rule of the corresponding record. The operation to be performed has further information before and after. The information before and after indicates that the work for the element indicated earlier is performed and then the work for the element indicated later is performed.

For example, in the operation procedure generation rule 150 shown in FIG.
・ When the work content is “Stop” of “Apl β”
・ If there is data access from “Apl α” to “Apl β”,
・ It is defined that “Apl β” is stopped after “Apl α” is stopped.

For example, in the operation procedure generation rule 150 shown in FIG.
・ When the work content is “Stop” of “Serverα”,
・ If “Aplβ” is running on “Serverα”,
・ It is defined that “Serverα” is stopped after “Apl β” is stopped.

Also, for example, in the operation procedure generation rule 150 shown in FIG.
・ If the work content is “Stop” of “Aplβ” on “Serverα”,
・ If there is a server load balancing service from “LB” to “Serverα”,
It is defined that the server load distribution service to “Apl β” running on “Server α” is blocked and then “Apl β” is stopped.

  Note that <LB> </> tags represent elements of the load balancer. The <SLBService> </> tag represents a server load balancing service, and </> <SLBService> Aplβ <Server> Server α </> </> represents “Apl β” running on “Server α”. Represents the server load balancing service. <Application> Apl β <Server> Server α </> </> represents “Apl β” operating on “Server α”.

  FIG. 3 is a diagram illustrating an example of automatic generation of work procedures.

  Here, the automatic generation tool operating on the computer uses the operation procedure generation rule 150 shown in FIG. 2 to perform an operation for stopping the application “AplB” in the work target system shown in FIG. An example of automatically generating a procedure will be described. The procedure generation data 140 shown in FIG. 3 is work data used for automatic generation of work procedures. In the procedure generation data 140, the check flag is a flag indicating whether the work of the corresponding record has been processed or not processed. “1” indicates that processing has been completed, and “0” indicates that processing has not been performed.

  As shown in FIG. 3 (A), in the procedure generation data 140, as the intended work content, the application “AplB” is recorded as the work target, and “stop” is recorded as the work item. The check flag is “0” indicating unprocessed.

  Since the check flag of the record of the work target “AplB” is “0”, the automatic generation tool performs processing for the work target “AplB”. From the related information 121 shown in FIG. 1C, the data access relationship from the related source application “AplA” to the related destination application “AplB” is obtained. The obtained relation matches the pattern of the relation information between elements in the rule with the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. From the operation to be performed on the rule with the rule ID “R1”, it is understood that the application “AplA” needs to be “stopped” before the “stop” of the application “AplB”.

  As shown in FIG. 3B, a record in which the work object “AplA” and the work item “stop” are recorded is added to the procedure generation data 140. The check flag of this record is “0” indicating unprocessed. Note that the check flag of the record of the work target “AplB” that has been processed is updated to “1” indicating that the processing has been completed.

  Since the check flag of the record of the work target “AplA” is “0”, the automatic generation tool performs processing for the work target “AplA”. From the related information 121 shown in FIG. 1C, the data access relationship from the related source application “AplC” to the related destination application “AplA” is obtained. The obtained relation matches the pattern of the relation information between elements in the rule with the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. It can be seen from the operation to be performed on the rule with the rule ID “R1” that the application “AplC” needs to be “stopped” before the “stop” of the application “AplA”.

  As shown in FIG. 3C, a record in which the work target “AplC” and the work item “stop” are recorded is added to the procedure generation data 140. The check flag of this record is “0” indicating unprocessed. Note that the check flag of the record of the work target “AplA” that has been processed is updated to “1” indicating that the processing has been completed.

  Since the check flag of the record of the work target “AplC” is “0”, the automatic generation tool performs processing for the work target “AplC”. However, none of the relations including the work target “AplC” obtained from the relation information 121 shown in FIG. 1C matches the rule of the operation procedure generation rule 150 shown in FIG. As shown in FIG. 3D, in the procedure generation data 140, the check flag of the record of the work target “AplC” is updated to “1” indicating that the processing has been completed. The records of the procedure generation data 140 shown in FIG. 3D arranged in order from the bottom form a series of work procedures when performing the work of stopping the application “AplB”.

  FIG. 4 is a diagram illustrating an example of an automatically generated work procedure.

FIG. 4A shows an example in which a flow of a series of automatically generated work procedures obtained from the final result of the procedure generation data 140 shown in FIG. 3D is represented by a graph using nodes and arcs. Show. Nodes represent work on elements, and arcs represent the order in which work is done. As shown in FIG. 4 (A), the work procedure when working for the purpose of stopping “AplB” in the work target system shown in FIG.
“AplC” stops → “AplA” stops → “AplB” stops.

  FIG. 4B shows an example of a procedure manual describing a series of automatically generated work procedures obtained from the final result of the procedure generation data 140 shown in FIG. The automatic generation tool generates a procedure manual shown in FIG. 4B from the final result of the procedure generation data 140 shown in FIG. 3D, for example. The automatic generation tool stores the generated procedure manual 141 as, for example, a document file. The user can view the automatically generated procedure manual 141 displayed on a display device such as a display or printed out on paper.

  FIG. 5 is a flowchart of the procedure generation process according to this embodiment.

  The automatic generation tool acquires the work content indicating the target work (step S100). The automatic generation tool records the acquired work content in the first record of the procedure generation data 140 (step S101). At this time, the check flag is set to “0”.

  The automatic generation tool acquires the work target of the record whose check flag is “0” in the procedure generation data 140 (step S102). The automatic generation tool determines whether the related data including the acquired work target is in the related information 121 in the system configuration information of the work target system (step 103).

  If there is related data including the acquired work target (YES in step S103), the automatic generation tool determines whether the operation procedure generation rule 150 includes a rule corresponding to the related data including the acquired work target. (Step S104).

  If there is a rule corresponding to the related data including the acquired work target (YES in step S104), the automatic generation tool records a record whose work target is the element to be operated first in the operation to be performed by the corresponding rule. It adds to the procedure production | generation data 140 (step S105). At this time, the check flag of the added record is set to “0”. If there is no related data including the acquired work target (NO in step S103), or if there is no rule corresponding to the related data including the acquired work target (NO in step S104), the automatic generation tool The record is not added to the procedure generation data 140.

  The automatic generation tool updates the check flag of the corresponding work target record in the procedure generation data 140 to “1” (step S106). The automatic generation tool determines whether or not the procedure generation data 140 includes a record with a check flag “0” (step S107). If there is a record whose check flag is “0” (YES in step S107), the automatic generation tool returns to the process in step S102 and proceeds to the next work target process. If there is no record whose check flag is “0” (NO in step S107), the automatic generation tool ends the process. The final procedure generation data 140 becomes work procedure data for executing the intended work.

  As described so far, the information indicating the relation between the elements constituting the work target system using the operation procedure generation rule 150 that defines the correspondence between the relation between the elements constituting the system and the work procedure between the elements. Therefore, it is possible to automatically generate a work procedure for a target work with a computer.

  In the case of an existing system that is already in operation, information on each element constituting the work target system can be easily obtained from, for example, a CMDB or a system design document. However, it is difficult to obtain information indicating the relationship between each element because there is no document in which the information is clearly described or information is distributed among a plurality of documents and setting files.

  In particular, applications are updated more frequently due to changes in specifications than devices such as servers, and the association between elements is rarely managed as in devices. Therefore, even if system configuration information about the work target system is collected, the system configuration information lacks related information such as dependency relationships between applications, data flow relationships between applications, and data access relationships between applications. More cases. The dependency relationship between applications indicates a relationship in which a certain application operates according to the operation of another application. The data flow relationship between applications indicates a relationship in which data of a certain application becomes an input of another application. The data access relationship between applications indicates a relationship in which a certain application accesses data of another operating application.

  In view of such a situation, hereinafter, a technique for estimating a relationship between elements constituting a work target system using a computer will be described mainly using an example of estimating a relationship between applications.

  FIG. 6 is a diagram illustrating a configuration example of the relation estimation apparatus according to the present embodiment.

  The relationship estimation apparatus 10 shown in FIG. 6 estimates the relationship between elements constituting the work target system. The related estimation device 10 includes a configuration information acquisition unit 11, a configuration information storage unit 12, a procedure acquisition unit 13, a procedure generation unit 14, a rule storage unit 15, a difference extraction unit 16, a specification unit 17, an update unit 18, and an output unit 19. Prepare.

  The configuration information acquisition unit 11 acquires system configuration information of the work target system. In the example illustrated in FIG. 5, the configuration information acquisition unit 11 acquires system configuration information from the CMDB 20. The configuration information acquisition unit 11 stores the acquired system configuration information in the configuration information storage unit 12.

  The configuration information storage unit 12 is a storage unit that stores system configuration information about the work target system. The system configuration information stored in the configuration information storage unit 12 includes, for example, element information 120 as shown in FIG. 1B and related information 121 as shown in FIG.

  The CMDB 20 is a database that integrates and manages information on elements constituting the system. Here, it is assumed that the system configuration information acquired from the CMDB 20 lacks some information regarding the related information 121, that is, information indicating the relationship between elements constituting the work target system. The system configuration information at the stage acquired by the configuration information acquisition unit 11 from the CMDB 20 is not sufficient system configuration information for automatic generation of a work procedure for the work target system. Note that the configuration information acquisition unit 11 may acquire system configuration information from other than the CMDB 20, such as a design document file of the work target system.

  The procedure acquisition unit 13 acquires a first work procedure. In the present embodiment, the first work procedure is, for example, a work procedure created by a person in consideration of the configuration of the work target system with respect to the intended work content. In the example of the present embodiment, the procedure acquisition unit 13 acquires from the procedure information storage unit 30 a file of a document that has been manually created in the past and has a work procedure with a track record of operation, and describes it in the document. It is assumed that the first work procedure is acquired by automatically extracting the performed work procedure.

  Note that the first work procedure is not necessarily a work procedure created in the past. For example, the design method of the first work procedure can be arbitrarily designed, such as obtaining the work procedure input by the user on the spot while considering the configuration of the work target system.

  The procedure generation unit 14 determines the first from the information indicating the relationship between the elements in the work target system according to the information in which the correspondence between the elements in the system composed of hardware or software elements and the correspondence between the work procedures is defined. The second work procedure having the same purpose as the work procedure is automatically generated.

  In the example of the present embodiment, the procedure generation unit 14 is a means realized by the above-described automatic generation tool. In addition, information in which a correspondence between elements and a work procedure in a system composed of hardware or software elements is defined is an operation procedure generation rule 150 as shown in FIG. The rule storage unit 15 is a storage unit that stores the operation procedure generation rule 150. The information indicating the relationship between elements in the work target system is related information 121 included in the system configuration information of the work target system as shown in FIG. That is, the procedure generation unit 14 automatically generates a second work procedure from the related information 121 included in the system configuration information of the work target system in accordance with the operation procedure generation rule 150 stored in the rule storage unit 15.

  The difference extraction unit 16 extracts a work procedure that is a difference between the first work procedure acquired by the procedure acquisition unit 13 and the second work procedure generated by the procedure generation unit 14.

  The specifying unit 17 uses the operation procedure generation rule 150 used when the procedure generation unit 14 automatically generates the second work procedure to generate a work procedure that becomes a difference extracted by the difference extraction unit 16. Identify relationships between elements in the target system. As described above, in the automatic generation of the work procedure, the operation procedure between the elements is derived from the relationship between the elements using the operation procedure generation rule 150. On the other hand, the specifying unit 17 uses the operation procedure generation rule 150 in the reverse direction to the case of automatic generation of the work procedure, and derives the relationship between the elements from the work procedure between the elements.

  The update unit 18 updates information indicating the relationship between elements in the work target system based on the result of specifying the relationship between elements by the specifying unit 17. For example, when the difference work procedure is a work procedure included in the first work procedure, the update unit 18 stores the association between the elements specified from the difference work procedure in the configuration information storage unit 12. Added to the related information 121 in the system configuration information.

  The output unit 19 outputs the system configuration information to which information indicating the relationship between the estimated elements stored in the configuration information storage unit 12 is added.

  In the initial system configuration information acquired from the CMDB 20 and stored in the configuration information storage unit 12, some information indicating the relationship between elements is missing. In this state, when a difference between the first work procedure and the second work procedure is taken, the work procedure that is the difference obtained is included in the first work procedure and is not in the second work procedure. It becomes a procedure. At this time, assuming that the first work procedure is an accurate work procedure, the relationship between the elements specified from the work procedure as a difference exists in the work target system, and the system configuration of the configuration information storage unit 12 In information, it is the relationship between elements that lack information. As described above, by using the operation procedure generation rule 150, the system configuration information includes the relationship between the elements in which the work procedure that is the difference between the first work procedure and the second work procedure occurs. Although there is no record, it is possible to estimate the relationship between elements that exist in the actual work system.

  Further, by adding the relationship between the identified elements to the information indicating the relationship between the elements in the system configuration information stored in the configuration information storage unit 12, more accurate system configuration information can be easily obtained. . Although depending on the scale of the work target system, it is difficult to estimate all the relationships between the elements that are insufficient in the system configuration information in one relevance estimation process for the work of one target work content. More accurate system configuration information can be obtained by repeatedly performing the related estimation processing for a plurality of tasks having different target work contents. This makes it easy to automatically generate work procedures in an existing system that is already in operation.

  Up to this point, the principle is that the first work procedure is an accurate work procedure. However, work procedures created manually may include redundant or ambiguous procedures, even if there are no shortages or errors. Even if a redundant work procedure is included in a work procedure that has been used in the past, there is a case where the redundant work procedure is executed as it is because there is no problem if the work procedure has no shortage or error. In addition, even if there is an ambiguous description or redundant description in the document of the work procedure, there is a case where the work without the ambiguity or redundancy is performed by the implicit understanding among the users who perform the work.

  When the relationship between the elements according to the present embodiment is estimated using the first work procedure acquired in such a situation, the relationship between the elements that do not actually exist in the work target system is determined. There is a possibility of adding to the information. In order to solve such a problem, in the present embodiment, it is determined that redundant estimation is added from a redundant work procedure in the process of repeatedly performing the related estimation process for a plurality of works having different target work contents. Delete the relationship between elements from the system configuration information.

  The updating unit 18 determines the relationship between the elements specified by the specifying unit 17 depending on whether the work procedure that becomes the difference is a work procedure included in the first work procedure or the second work procedure. Determine whether to add to or delete from system configuration information.

  For example, if the difference work procedure is a work procedure included in the first work procedure, the relationship between the elements identified from the difference work procedure is the relationship between the elements existing in the work target system. The system configuration information in the configuration information storage unit 12 may be missing. At this time, the update unit 18 adds the association between the elements specified from the difference work procedure to the system configuration information stored in the configuration information storage unit 12.

  Further, for example, when the difference work procedure is a work procedure included in the second work procedure, the relationship between the elements specified from the difference work procedure is recorded in the system configuration information of the configuration information storage unit 12. There is a possibility that there is an association between elements that do not exist in the actual work target system. At this time, if the work target element causing the difference work procedure is an element to be worked on first in the difference work procedure, the update unit 18 specifies the difference work procedure. The relationship between the elements to be processed is deleted from the system configuration information stored in the configuration information storage unit 12.

  In this case, the work target element that causes the difference work procedure is the work target in the second work procedure, and is not the work target in the first work procedure. Assuming that the first work procedure is the correct work procedure, the first work procedure must always include work on the elements that are required in the course of performing the work on the target element. It is. At this time, if there is a work procedure in which the element that is not included in the first work procedure is the work target to be performed first in the second work procedure, the relationship between the elements from which the work procedure has occurred Is a relationship between elements that do not exist in the actual work target system.

  Thereby, it is possible to appropriately delete the relationship between the erroneous elements added to the system configuration information of the work target system by the redundant first work procedure.

  FIG. 7 is a diagram illustrating a hardware configuration example of a computer that realizes the relation estimation device according to the present embodiment.

  A computer 1 that implements the relationship estimation device 10 of the present embodiment shown in FIG. 6 includes, for example, a CPU (Central Processing Unit) 2, a memory 3 as a main memory 3, a storage device 4, a communication device 5, a medium reading / writing A device 6, an input device 7, an output device 8 and the like are provided. The storage device 4 is an external storage device such as an HDD (Hard Disk Drive) or an auxiliary storage device. The medium reading / writing device 6 is, for example, a CD-R (Compact Disc Recordable) drive or a DVD-R (Digital Versatile Disc Recordable) drive. The input device 7 is, for example, a keyboard / mouse. The output device 8 is a display device such as a display, for example.

  The relationship estimation device 10 and each function unit included in the relationship estimation device 10 illustrated in FIG. 6 can be realized by hardware such as the CPU 2 and the memory 3 included in the computer 1 and a software program. A program that can be executed by the computer 1 is stored in the storage device 4, read into the memory 3 at the time of execution, and executed by the CPU 2.

  The computer 1 can also read a program directly from a portable recording medium and execute processing according to the program. The computer 1 can also sequentially execute processing according to the received program every time the program is transferred from the server computer. Further, this program can be recorded on a recording medium readable by the computer 1.

  Hereinafter, the estimation of the relationship between the elements constituting the work target system according to the present embodiment will be described using a more specific example.

  The configuration information acquisition unit 11 acquires system configuration information of the work target system from the CMDB 20. The acquired system configuration information is stored in the configuration information storage unit 12.

  FIG. 8 is a diagram illustrating a configuration example (1) of the work target system according to the present embodiment.

  The configuration example of the work target system illustrated in FIG. 8 illustrates the configuration of the work target system based on the system configuration information acquired by the configuration information acquisition unit 11. In the configuration example of the work target system shown in FIG. 8, only the relationship between elements that are recorded in the system configuration information is described, and between elements that are present in the actual work target system but are not recorded in the system configuration information. The relationship is not described.

  As shown in FIG. 8, the work target system of the present embodiment includes servers “WEB Server”, “AP Server 1”, “AP Server 2”, and a load balancer “LB” as hardware elements. In addition, the work target system of this embodiment includes applications “AplX”, “AplY”, and “AplZ” as software elements.

  In the work target system shown in FIG. 8, arrows indicate the relationship between hardware elements. As shown in FIG. 8, in the work target system, a request issued from “WEB Server” is load-balanced between “AP Server1” and “AP Server2” by “LB” server load balancing service. There is a relationship. In the target system, the applications “AplY” and “AplZ” run on the server “WEB Server”, and the application “AplX” runs on the servers “AP Server1” and “AP Server2”. There is a connection. Such association between the elements constituting the work target system is recorded in the system configuration information of the work target system stored in the configuration information storage unit 12.

  In the configuration example of the work target system shown in FIG. 8, the relationship between application elements is not described. That is, the system configuration information of the work target system shown in FIG. 8 stored in the configuration information storage unit 12 lacks the recording of information about the relationship between application elements. Below, the example which estimates the relationship between the elements of the application which are missing with system configuration information with the relationship estimation apparatus 10 by this Embodiment is demonstrated.

  A plurality of document files stored in the procedure information storage unit 30 describe work procedures having different operation contents and having operational results in the past. In the following, a document that has been created manually in the past and that has a work procedure with a track record of operation is referred to as an existing procedure manual. Assume that the relationship estimation apparatus 10 reads out existing procedure manual files one by one in the specified order, and performs a relationship estimation process between elements according to the present embodiment.

  FIG. 9 is a diagram illustrating an example (1) of the existing procedure manual according to the present embodiment.

  In the related estimation device 10, the procedure acquisition unit 13 first reads out the file of the existing procedure manual 130 a shown in FIG. 9 from the procedure information storage unit 30. The procedure acquisition unit 13 assigns a procedure manual ID “001” to the acquired existing manual 130a. The procedure manual ID is identification information for uniquely identifying an existing procedure manual. In this embodiment, since the relationship estimation process between elements is performed for each existing procedure manual, a procedure manual ID is issued for each existing procedure manual to manage the relationship estimation process between elements.

  In the existing procedure manual 130a shown in FIG. 9, the target work content is described in the header portion. Further, in the existing procedure manual 130a shown in FIG. 9, the work procedure is described in a form in which the number indicating the order and the work to be performed in the order are listed.

  The procedure acquisition unit 13 acquires the target work content and the work procedure from the existing procedure manual 130a. In this embodiment, the procedure acquisition unit 13 analyzes the text of the existing procedure manual and extracts the target work content and work procedure. In the text analysis of the existing procedure manual, a well-known text processing technique shall be used. For example, the procedure acquisition unit 13 can acquire a work target “XX” and a work item “XX” from a text “XX is XX” by a well-known syntax analysis technique. it can.

In existing procedure manuals, for example, work items with the same content may be expressed in various words. For example, even with the same meaning of “stop”, there are various expressions such as “shutdown”, “stop”, and “stop”. The procedure acquisition unit 13 is, for example,
“Shutdown” → “Stop”
“Stop” → “Stop”
“Stop” → “Stop”
“Launch” → “Start”
“Boot” → “Start”
...
In this way, using the dictionary in which the correspondence of word notation is recorded, the notation of work items with the same content is unified.

  First, the procedure acquisition unit 13 acquires the work target and the work item in the target work content from the header portion of the existing procedure manual 130a. Here, the work target “AP Server 1” and the work item “stop” are acquired from the existing procedure manual 130a as target work contents. The procedure acquisition unit 13 records the acquired target work content in the work content management table.

  FIG. 10 is a diagram illustrating an example of a work content management table according to the present embodiment.

  The work content management table 131 shown in FIG. 10 is an example of information for managing target work content. In the work content management table 131 shown in FIG. 10, the target work content acquired from the existing procedure manual 130a is recorded.

  The work content management table 131 shown in FIG. 10 has information of procedure manual ID, work target, and work item. The procedure manual ID indicates the procedure manual ID assigned to the existing procedure manual. The work target indicates the work target of the target work content acquired from the existing procedure manual. The work item indicates the work item of the target work content acquired from the existing procedure manual.

  Next, the procedure acquisition unit 13 acquires a work procedure from the existing procedure manual 130a. For example, the syntax analysis is performed on the description of the work procedure in the order of the numbers shown in the existing procedure manual 130a, and the work procedure is extracted from the existing procedure manual 130a. The work procedure acquired here is the first work procedure. In the present embodiment, the first work procedure is a work procedure that is created manually in consideration of the relationship between elements and has a past operation record. Hereinafter, the first work procedure in the present embodiment is referred to as an existing procedure.

  FIG. 11 is a diagram illustrating an example (1) of the existing procedure data according to the present embodiment.

  The existing procedure data 132a illustrated in FIG. 11 is an example of data in which an existing procedure acquired from the existing procedure document 130a having the procedure document ID “001” illustrated in FIG. 9 is recorded. The existing procedure data 132a has information on operation order, work target, and work item. The operation order indicates the order in which the work indicated by the record is performed. The work target indicates the work target of the work indicated by the record. The work item indicates the work item of the work indicated by the record.

  The procedure generation unit 14 acquires the work content intended by the existing procedure manual 130a to be processed. Here, the procedure generation unit 14 obtains the target work content of the procedure manual ID “001” from the work content management table 131 shown in FIG.

  The procedure generation unit 14 performs work of the desired work content from the system configuration information of the work target system shown in FIG. 8 stored in the configuration information storage unit 12 according to the operation procedure generation rule 150 stored in the rule storage unit 15. Generate a work procedure to do The rule storage unit 15 stores, for example, an operation procedure generation rule 150 shown in FIG. The procedure generation unit 14 automatically generates a work procedure according to the procedure generation process flow described with reference to FIGS. The work procedure generated here is the second work procedure. Hereinafter, the second work procedure in the present embodiment is referred to as an automatic generation procedure.

  FIG. 12 is a diagram illustrating an example (1) of the automatic generation procedure data according to the present embodiment.

  The automatic generation procedure data 142a illustrated in FIG. 12 is an example of data in which an automatic generation procedure generated from the system configuration information of the work target system illustrated in FIG. 8 is recorded. The target work content of the automatic generation procedure of the automatic generation procedure data 142a shown in FIG. 12 is the target work content of the existing procedure manual 130a having the procedure manual ID “001” shown in FIG. The automatic generation procedure data 142a has information on operation order, work target, and work item. The operation order indicates the order in which the work indicated by the record is performed. The work target indicates the work target of the work indicated by the record. The work item indicates the work item of the work indicated by the record.

  The existing procedure of the existing procedure data 132a shown in FIG. 11 and the automatic generation procedure of the automatic generation procedure data 142a shown in FIG. The difference extraction unit 16 extracts a work procedure that becomes a difference between these work procedures.

  FIG. 13 is a diagram illustrating an example (1) in which the flow of the existing procedure and the automatic generation procedure according to the present embodiment is represented by a graph.

  FIG. 13A is a graph showing the flow of the existing procedure. FIG. 13B is a graph showing the flow of the automatic generation procedure. In the graph shown in FIG. 13, a node represents a work in each operation order of the existing procedure data 132a or the automatically generated procedure data 142a. An arc represents the order in which operations are performed among the operations in each operation sequence. The arc is drawn from the node of the work whose operation order is earlier to the node whose operation order is later.

  In the node, the descriptions “APS1” and “APS2” represent “AP Server1” and “AP Server2”, respectively. “APS1 (LB service)” and “APS2 (LB service)” represent server load distribution services by “LB” for “AP Server1” and “AP Server2”, respectively. “AplX (APS1)” and “AplX (APS2)” represent “AplX” on “AP Server1” and “AplX” on “AP Server2”, respectively.

  In the existing procedure manual, there is a case where the work target in the work procedure is vaguely described. For example, in the existing procedure manual 130a shown in FIG. And 3. In the work procedure shown in, the work target is described as “AplX” on “AP Server”. In this description, it is not clear whether the work target is "AplX" on "AP Server1", "AplX" on "AP Server2", or both.

  Therefore, the difference extraction unit 16 refers to the system configuration information stored in the configuration information storage unit 12, expands all the operations that can be a work target, and creates a difference between the existing procedure and the automatic generation procedure. Extract the procedure. For example, as shown in the graph of FIG. 13A, the operation of the operation sequence “3” in the existing procedure data 132a shown in FIG. 11 is the blocking of the server load balancing service for “AplX” on “AP Server1”. It can be divided into server load balancing service blockage for “AplX” on “AP Server2”. Further, as shown in the graph of FIG. 13A, the operation of the operation sequence “4” in the existing procedure data 132a shown in FIG. 11 is performed by stopping “AplX” on “AP Server1” and “AP Server2”. It is divided into “AplX” stop.

In addition, the work procedure derived from the relationship between elements is not necessarily a work procedure in which the operation order is continuous. For example, when there is a data access relationship of “Apl α” → “Apl β”, “Apl γ” → “Apl β”, the work procedure for stopping “Apl β” is as follows:
Stopping “Apl α” → Stopping “Apl γ” → Stopping “Apl β”. In this case, the stop of “Apl α” and the stop of “Apl β” are not work procedures in which the operation sequence is continuous, but there is an inter-element relationship between “Apl α” and “Apl β”.

  Therefore, the difference extraction unit 16 extracts all work combinations whose operation order is from first to later as a target for extracting a work procedure that becomes a difference between the existing procedure and the automatic generation procedure. For example, as shown in the graph of FIG. 13B, the work procedure from the work of the operation order “1” to the work of the operation order “3” in the automatic generation procedure data 142a shown in FIG. To be extracted.

  In consideration of such a situation, the difference extraction unit 16 performs the operation order from first to last for each of the existing procedure and the automatic generation procedure when extracting the difference of the work procedure between the existing procedure and the automatic generation procedure. Extract all work procedures that combine work.

  FIG. 14 is a diagram illustrating an example of difference extraction intermediate data according to the present embodiment.

  FIG. 14A shows the difference extraction intermediate data 160 that is generated from the existing procedure data 132a shown in FIG. An example is shown. Each record of the differential extraction intermediate data 160 shown in FIG. 14A is a work procedure record indicated by each arc in the graph of the existing procedure shown in FIG. In the difference extraction intermediate data 160, the work target at the start point indicates the work target of the node that is the start point of the arc, and the work target at the end point indicates the work target of the node that is the end point of the arc.

  FIG. 14B shows a difference extraction intermediate in which all the work procedures that are generated from the automatic generation procedure data 142a shown in FIG. An example of data 161 is shown. Each record of the differential extraction intermediate data 161 shown in FIG. 14B is a record of the work procedure indicated by each arc in the graph of the automatic generation procedure shown in FIG. 13B. In the difference extraction intermediate data 161, the work target at the start point indicates the work target of the node that is the start point of the arc, and the work target at the end point indicates the work target of the node that is the end point of the arc.

  The difference extraction unit 16 obtains a difference between the difference extraction intermediate data 160 of the existing procedure shown in FIG. 14A and the difference extraction intermediate data 161 of the automatic generation procedure shown in FIG. 14B. , Extract the work procedure that is the difference between the existing procedure and the automatic generation procedure.

  In the graph of the existing procedure shown in FIG. 13A, the arc of the thick arrow indicates a work procedure that is a difference from the automatic generation procedure shown in FIG. In the graph of the existing procedure shown in FIG. 13A, the node of the thick line frame indicates the work target that causes the work procedure that becomes the difference indicated by the arc of the thick line arrow. That is, due to the existence of a work target that is a difference between the existing procedure and the automatic generation procedure, a work procedure that is a difference between the existing procedure and the automatic generation procedure occurs.

  The difference extraction unit 16 outputs information on the work procedure as all the extracted differences to the result table. At this time, the difference extraction unit 16 also records information on whether the work procedure to be a difference is a work procedure included in an existing procedure or an automatic generation procedure in the result table. In addition, information on a work target that causes a work procedure that is a difference is also recorded in the result table.

  FIG. 15 is a diagram illustrating an example (1) of the result table according to the present embodiment.

  The result table 162a shown in FIG. 15 shows an example of data for recording information such as extraction results of work procedures that are differences. In the result table 162a shown in FIG. 15, information on the work procedure that is a difference between the existing procedure and the automatic generation procedure in a series of processes for the existing procedure document 130a with the procedure document ID “001” is recorded.

  The result table 162a illustrated in FIG. 15 includes appearance procedure, difference work object, start work object, end work object, estimated related information, and determination result information. The appearance procedure indicates whether the work procedure that is the difference between the corresponding records is included in the existing procedure or the automatic generation procedure. The differential work target indicates a work target that causes a work procedure that is a difference between the corresponding records. The work target of the start point indicates the work target of the work to be performed first in the work procedure that is the difference between the corresponding records. The work target at the end point indicates the work target of the work to be performed later in the work procedure that is the difference between the corresponding records. The estimated related information and the determination result will be described later.

  The specifying unit 17 uses the operation procedure generation rule 150 stored in the rule storage unit 15 to determine, for each work procedure that becomes a difference extracted by the difference extraction unit 16, between the elements that cause the work procedure that becomes the difference. Identify the association.

  For example, it is assumed that the operation procedure generation rule 150 illustrated in FIG. 2 is stored in the rule storage unit 15. For each record in the result table 162a, the specifying unit 17 extracts a rule for deriving a work procedure that is a difference indicated by the corresponding record from the operation procedure generation rule 150 illustrated in FIG.

  The rule for deriving a work procedure that is a difference is a rule in which the relationship between the work target of the start point and the work target of the end point in the work procedure that becomes the difference matches the relationship between the destination of the operation to be performed and the post-operation. The specifying unit 17 extracts, from the operation procedure generation rule 150, a rule having a relationship between the destination of the operation to be performed and the destination that matches the relationship between the start work target and the end work target in the difference work procedure. . The specifying unit 17 acquires related information between elements from the extracted rules. The specifying unit 17 specifies the relationship between the elements indicated in the acquired relationship information between the elements as the relationship between the elements that causes the work procedure to be a difference.

  FIG. 16 is a diagram illustrating an example (1) of a work procedure that is a difference according to the present embodiment.

  FIG. 16 shows a graph of a work procedure that becomes all the extracted differences in a series of processes for the existing procedure manual 130a with the procedure manual ID “001”.

  In the work procedure that is the difference shown in FIG. 16A, the relationship between the work point at the start point and the work target at the end point is the operation to be performed in the rule of the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between before and after. The identifying unit 17 determines from the application “AplY” to the application “AplZ” that the relation between the elements causing the work procedure that is the difference shown in FIG. 16A from the relation information between the elements in the rule with the rule ID “R1”. Identify data access to.

  In the work procedure with each difference shown in FIG. 16B, the relationship between the work object at the start point and the work object at the end point should be the work in the rule of rule ID “R1” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between the destination and after the operation. The specifying unit 17 determines that the relationship between the elements that cause the work procedure as each difference shown in FIG. 16B is changed from the application “AplY” to the application “AplX” from the related information between the elements in the rule with the rule ID “R1”. ”To specify data access.

  In the work procedure with each difference shown in FIG. 16C, the relationship between the work object at the start point and the work object at the end point should be the work in the rule of the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between the destination and after the operation. The specifying unit 17 determines that the relationship between the elements that cause the work procedure as each difference shown in FIG. 16C is changed from the application “AplZ” to the application “AplX” from the related information between the elements in the rule with the rule ID “R1”. ”To specify data access.

  In the work procedure that is the difference shown in FIG. 16D, the relationship between the work target of the start point and the work target of the end point is the operation to be performed in the rule of the rule ID “R3” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between before and after. The specifying unit 17 determines that the relationship between the elements causing the work procedure that is the difference shown in FIG. 16D is related from the load balancer “LB” to the server “AP” from the relationship information between the elements in the rule with the rule ID “R3”. Specify load distribution to Server2 ”.

  Regarding the work procedure that is the difference shown in FIG. 16E, the relationship between the work destination to be worked and the work work corresponding to the relation between the work object at the start point and the work object at the end point is the operation shown in FIG. It is assumed that the procedure generation rule 150 does not exist. Regarding the work procedure that becomes each difference shown in FIG. 16 (E), the rule for directly deriving the work procedure does not exist in the operation procedure generation rule 150 shown in FIG. It is determined that the relationship between the elements cannot be obtained from the work procedure as each difference.

  The specifying unit 17 outputs the relationship between the specified elements to the result table 162a for the work procedure that is the difference in which the relationship between the elements is specified.

  FIG. 17 is a diagram illustrating an example (2) of the result table according to the present embodiment.

  A result table 162a illustrated in FIG. 17 illustrates an example in which the estimated related information data is added to the result table 162a illustrated in FIG. In the result table 162a, the estimated relation information records the relation between the elements specified by using the operation procedure generation rule 150 in the work procedure that is the difference between the records. In the result table 162a shown in FIG. 17, the record of the work procedure that is the difference for which the association between the elements cannot be obtained is deleted.

  The update unit 18 determines whether the work procedure that is the original difference from which the relation between the elements is obtained is the work procedure included in the existing procedure or the automatic generation procedure. The update of the system configuration information stored in the configuration information storage unit 12 is determined. When the work procedure that is the original difference from which the relationship between the elements is obtained is a work procedure included in the existing procedure, the update unit 18 stores information indicating the relationship between the elements in the configuration information storage unit 12 at that time. It is determined to be added to the configured system configuration information. The case where the work procedure that is the original difference from which the relationship between the elements is obtained is a work procedure included in the automatic generation procedure will be described later.

  FIG. 18 is a diagram illustrating an example (3) of the result table according to the present embodiment.

  A result table 162a illustrated in FIG. 18 illustrates an example in which a determination result of system configuration information update is further added to the result table 162a illustrated in FIG. In the result table 162a, the determination result is recorded as the determination result regarding the update of the system configuration information using the relationship between the elements specified from the work procedure which is the difference between the records. In the result table 162a shown in FIG. 18, since all appearance procedures are existing procedures, all determination results are added.

  The update unit 18 updates the system configuration information stored in the configuration information storage unit 12 based on the determination result of the system configuration information update.

  In the result table 162a shown in FIG. 18, the determination results for all records are “added”. The update unit 18 stores the system configuration information of the work target system illustrated in FIG. 8 stored in the configuration information storage unit 12 in the configuration information storage unit 12, with the relationship between the elements indicated in the related information estimated in each record of the result table 162 a illustrated in FIG. 18. Add to Note that the load distribution from the load balancer “LB” to the server “AP Server2” is not particularly updated because the information related to the load is included in the initial system related information as shown in FIG. Absent.

  FIG. 19 is a diagram illustrating a configuration example (2) of the work target system according to the present embodiment.

  In the configuration example of the work target system shown in FIG. 19, the relationship between the elements obtained by a series of processes for the existing procedure manual 130a with the procedure manual ID “001” is added to the system configuration information of the work target system shown in FIG. The configuration of the work target system based on the configured system configuration information is shown. In the configuration example of the work target system illustrated in FIG. 19, a thick line arrow indicates a relationship between added elements.

  In a state where the system configuration information of the work target system shown in FIG. 19 is stored in the configuration information storage unit 12, the relationship estimation apparatus 10 proceeds to processing for the next existing procedure manual.

  FIG. 20 is a diagram illustrating an example (2) of the existing procedure manual according to the present embodiment.

  The procedure acquisition unit 13 reads the file of the existing procedure manual 130b shown in FIG. 20 from the procedure information storage unit 30. The procedure acquisition unit 13 assigns a procedure manual ID “002” to the acquired existing manual 130b.

  The procedure acquisition unit 13 acquires the work target and the work item in the target work content from the header portion of the existing procedure manual 130b. Here, the work target “AP Server” and the work item “stop” are acquired from the existing procedure manual 130b as target work contents. The procedure acquisition unit 13 records the acquired target work content in the work content management table 131. The procedure acquisition unit 13 acquires an existing procedure from the existing procedure manual 130b.

  FIG. 21 is a diagram illustrating an example (2) of the existing procedure data according to the present embodiment.

  The existing procedure data 132b illustrated in FIG. 21 is an example of data in which an existing procedure acquired from the existing procedure document 130b having the procedure document ID “002” illustrated in FIG. 20 is recorded.

  The procedure generation unit 14 acquires the work content intended by the existing procedure manual 130 b with the procedure manual ID “002” from the work content management table 131. The procedure generation unit 14 performs work of the intended work content from the system configuration information of the work target system shown in FIG. 19 stored in the configuration information storage unit 12 according to the operation procedure generation rule 150 stored in the rule storage unit 15. Generate a work procedure to do

  FIG. 22 is a diagram illustrating an example (2) of the automatic generation procedure data according to the present embodiment.

  The automatic generation procedure data 142b illustrated in FIG. 22 is an example of data in which an automatic generation procedure generated from the system configuration information of the work target system illustrated in FIG. 19 is recorded. The target work content of the automatic generation procedure of the automatic generation procedure data 142b shown in FIG. 22 is the target work content of the existing procedure manual 130b having the procedure manual ID “002” shown in FIG.

  The existing procedure of the existing procedure data 132b shown in FIG. 21 and the automatic generation procedure of the automatic generation procedure data 142b shown in FIG. The difference extraction unit 16 extracts a work procedure that becomes a difference between these work procedures.

  FIG. 23 is a diagram illustrating an example (2) in which the flow of the existing procedure and the automatic generation procedure according to the present embodiment is represented by a graph.

  FIG. 23A is a graph showing the flow of the existing procedure of the existing procedure data 132b shown in FIG. FIG. 23B is a graph showing the flow of the automatic generation procedure of the automatic generation procedure data 142b shown in FIG. In the graph of the automatic generation procedure shown in FIG. 23 (B), the arc of the thick dotted arrow indicates the work procedure that becomes a difference from the existing procedure shown in FIG. 23 (A). In the graph of the automatic generation procedure shown in FIG. 23B, the node of the thick dotted line frame indicates the work target that causes the work procedure to be the difference indicated by the arc of the thick dotted line arrow.

  The difference extraction unit 16 outputs information on the work procedure as all the extracted differences to the result table. At this time, the difference extraction unit 16 also records information on whether the work procedure to be a difference is a work procedure included in an existing procedure or an automatic generation procedure in the result table. In addition, information on a work target that causes a work procedure that is a difference is also recorded in the result table.

  The specifying unit 17 uses the operation procedure generation rule 150 stored in the rule storage unit 15 to determine, for each work procedure that becomes a difference extracted by the difference extraction unit 16, between the elements that cause the work procedure that becomes the difference. Identify the association.

  FIG. 24 is a diagram illustrating an example (2) of a work procedure that is a difference according to the present embodiment.

  FIG. 24 shows a graph of a work procedure that becomes all the extracted differences in a series of processes for the existing procedure manual 130b with the procedure manual ID “002”.

  In the work procedure that is the difference shown in FIG. 24A, the relationship between the work task at the start point and the work target at the end point is the operation to be performed in the rule with the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between before and after. The specifying unit 17 determines from the application “AplY” to the application “AplZ” that the relationship between the elements causing the work procedure that is the difference shown in FIG. Identify data access to.

  In the work procedure with each difference shown in FIG. 24B, the relationship between the work point of the start point and the work point of the end point should be the work in the rule of the rule ID “R1” of the operation procedure generation rule 150 shown in FIG. Corresponds to the relationship between the destination and after the operation. The specifying unit 17 determines that the relationship between the elements that cause the work procedure as each difference shown in FIG. 24B is changed from the application “AplZ” to the application “AplX” from the related information between the elements in the rule with the rule ID “R1”. ”To specify data access.

  With respect to the work procedures that are the differences shown in FIG. 24C, the relationship between the work destination to be worked and the work work corresponding to the relation between the work object at the start point and the work object at the end point is the operation shown in FIG. It is assumed that the procedure generation rule 150 does not exist. With respect to the work procedure that becomes each difference shown in FIG. 24C, since the operation procedure generation rule 150 shown in FIG. 2 does not have a rule for directly deriving the work procedure, the specifying unit 17 shows the work procedure shown in FIG. It is determined that the relationship between the elements cannot be obtained from the work procedure as each difference.

  The specifying unit 17 outputs the relationship between the specified elements to the result table for the work procedure that is the difference in which the relationship between the elements is specified.

  The update unit 18 determines whether to update the system configuration information stored in the configuration information storage unit 12 for the association between the identified elements. When the work procedure that is the original difference from which the relationship between the elements is obtained is a work procedure included in the automatic generation procedure, the update unit 18 determines that the work target that caused the work procedure that becomes the difference is It is confirmed whether it is a target to work first in the work procedure as the difference. If the work target that caused the work procedure that is the difference is the target to be worked on first in the work procedure that is the difference, the update unit 18 displays information indicating the relationship between the corresponding elements. At this time, it is determined to be deleted from the system configuration information stored in the configuration information storage unit 12. If the work target that causes the work procedure that becomes the difference is not the target to be worked on first in the work procedure that becomes the difference, the update unit 18 sets the configuration information storage unit for the relationship between the corresponding elements. 12 determines that no processing is to be performed on the system configuration information stored in 12.

  FIG. 25 is a diagram illustrating an example (4) of the result table according to the present embodiment.

  The result table 162b shown in FIG. 25 is a result table in which information on a work procedure that is a difference between the existing procedure and the automatic generation procedure is recorded in a series of processes for the existing procedure document 130b with the procedure document ID “002”. An example is shown. In the result table 162b illustrated in FIG. 25, the difference work target is a work target that causes the work procedure to be the difference indicated in the corresponding record. Note that the work procedure that is the difference indicated by each record in the result table 162b shown in FIG. 25 is a work procedure included in the automatic generation procedure.

  In the result table 162b shown in FIG. 25, the second and third records are records corresponding to work procedures that are two differences shown in the graph of FIG. From the work procedure as a difference indicated by these records, the relation of data access from the application “AplZ” to the application “AplX” is specified. If the relationship between such elements exists in the actual work target system, the application “AplZ” is set as the start work target in the process of executing the work of the target work content in the existing procedure manual 130b shown in FIG. Work procedure is required.

  However, in the existing procedure manual 130b shown in FIG. 20 that has been used in the past, there is no description of work for the application “AplZ”. If it is necessary to execute the work for the application “AplZ” in the process of executing the work of the target work content, the work for the application “AplZ” is added to the existing procedure manual 130b shown in FIG. Should be listed. The fact that there is no description of the work for the application “AplZ” in the existing procedure manual 130b shown in FIG. 20b means that it is not necessary to perform the work for the application “AplZ” in the process of executing the work of the intended work content. It is.

  From this, the relationship between the elements identified from the work procedure of the difference starting from the application “AplZ” shown in the second and third records of the result table 162b shown in FIG. 25 is the actual work. Presumed not to exist in the target system. In the result table 162b of FIG. 25, the update unit 18 uses the system configuration of the configuration information storage unit 12 to indicate the relationship between the elements in the second and third records that have the application “AplZ” as the differential work target. It is determined to be deleted from the information. In the second and third records in the result table 162b shown in FIG. 25, the determination result is “deleted”.

  In the result table 162b shown in FIG. 25, the first record is a record corresponding to the work procedure that is the difference shown in the graph of FIG. From the work procedure that is the difference indicated by this record, the relation of data access from the application “AplY” to the application “AplZ” is specified.

  As described above, it is not necessary to execute the work for the application “AplZ” that is the target of the differential work in the process of executing the work of the work content intended by the existing procedure manual 130b shown in FIG. When the work for the application “AplZ” is not performed, the work procedure shown in FIG. 24A in which the application “AplZ” that is the differential work target is the work work at the end point does not occur. Therefore, even if the data access relation from the application “AplY” to the application “AplZ” exists in the actual work target system, the work procedure shown in FIG. 24A is not reflected in the existing procedure. No problem.

  In the result table 162b of FIG. 25, the update unit 18 relates to the system configuration information in the configuration information storage unit 12 regarding the relationship between elements in the first record having the application “AplZ” as the end work as the end work. It is determined that no processing is performed. In the first record in the result table 162b shown in FIG. 25, the determination result is “no processing”.

  The update unit 18 updates the system configuration information stored in the configuration information storage unit 12 based on the determination result of the system configuration information update.

  In the result table 162b shown in FIG. 25, the determination results of the second and third records are “deleted”. The update unit 18 stores the relationship between the elements indicated in the related information estimated in the second and third records in the result table 162b shown in FIG. 25 and stored in the configuration information storage unit 12 as shown in FIG. Delete from the system configuration information of the system. For the relationship between elements indicated in the related information estimated in the first record in the result table 162b shown in FIG. 25, the process of updating the system configuration information is not performed.

  Note that, for example, the relationship between elements deleted from the system configuration information stored in the configuration information storage unit 12 is recorded from the work procedure included in the existing procedure. However, a mechanism not added to the system configuration information may be provided.

  FIG. 26 is a diagram illustrating a configuration example (3) of the work target system according to the present embodiment.

  In the configuration example of the work target system shown in FIG. 26, the relationship between the elements obtained by the series of processes for the existing procedure manual 130b with the procedure manual ID “002” is deleted from the system configuration information of the work target system shown in FIG. The configuration of the work target system based on the configured system configuration information is shown. In the configuration example of the work target system shown in FIG. 26, the thick line arrow indicating the access from the application “AplZ” to the application “AplX” that is in the configuration example of the work target system shown in FIG.

  The output unit 19 stores system configuration information including information indicating the relationship between the estimated elements stored in the configuration information storage unit 12 after the processing for all the specified existing procedure manuals is completed. Is output as a result of processing by the related estimation device 10.

  Hereinafter, the flow of processing by the relation estimation apparatus according to the present embodiment will be described using the flowcharts shown in FIGS.

  FIG. 27 is a flowchart of a relationship estimation process performed by the relationship estimation apparatus according to the present embodiment.

  In the related estimation device 10, the configuration information acquisition unit 11 acquires system configuration information of the work target system from the CMDB 20 (step S10). The acquired system configuration information is stored in the configuration information storage unit 12.

  The procedure acquisition unit 13 selects one existing procedure manual with a past operation record for the work target system (step S11). Here, the procedure acquisition unit 13 reads the selected procedure manual file from the procedure information storage unit 30.

  The procedure acquisition unit 13 extracts the work contents intended by the existing procedure manual from the existing procedure manual (step S12). In addition, the procedure acquisition unit 13 acquires an existing procedure from the existing procedure manual (step S13). Here, the procedure acquisition unit 13 automatically extracts information by text analysis on the existing procedure manual.

  The procedure generation unit 14 executes procedure generation processing (step S14). In the procedure generation process, a work procedure for a target work content extracted from the existing procedure manual is extracted from the system configuration information stored in the configuration information storage unit 12 according to the operation procedure generation rule stored in the rule storage unit 15. Automatically generated. The work procedure generated by the procedure generation process is an automatic generation procedure. The procedure generation process is, for example, the process shown in the flowchart of FIG.

  The difference extraction unit 16 extracts a work procedure that becomes a difference between the existing procedure and the automatic generation procedure (step S15). For example, the extracted work procedure is recorded in a result table as shown in FIG. The identification unit 17 executes a relation identification process (step S16). The association specifying process is a process of specifying an association between elements that causes a work procedure that becomes a difference extracted by the difference extraction unit 16. Details of the association specifying process will be described later.

  The update unit 18 executes a result determination process (step S17). The result determination process is a process for determining the update of the system configuration information stored in the configuration information storage unit 12 for the association between the elements specified by the specifying unit 17. Details of the result determination process will be described later. The update unit 18 updates the system configuration information stored in the configuration information storage unit 12 according to the determination result obtained by the result determination process (step S18).

  The output unit 19 determines whether the processing has been completed for all specified existing procedure manuals (step S19). If the processing has not been completed for all existing procedure manuals (NO in step S19), the relationship estimation apparatus 10 returns to the process in step S11 and proceeds to the processing of the next existing procedure manual. If the processing has been completed for all existing procedure manuals (YES in step S19), the output unit 19 outputs the system configuration information (step S20) and ends the processing.

  FIG. 28 is a flowchart of related identification processing by the identification unit of the present embodiment.

  For example, the specifying unit 17 selects one record in the result table as shown in FIG. 15 (step S110). The specifying unit 17 acquires the work target at the start point and the work target at the end point from the selected record (step S111). The specifying unit 17 refers to the operation procedure generation rule 150 in the rule storage unit 15 and determines the relationship between the destination and the destination of the operation to be performed, which matches the acquired relationship between the start point work target and the end point work target. The rule possessed is extracted (step S112). The specifying unit 17 determines whether or not the operation procedure generation rule 150 has a rule in which the relationship between the acquired start point work target and the end point work target matches the relationship between the operation destination and the operation to be performed. (Step S113).

  If there is no matching rule (NO in step S113), the specifying unit 17 deletes the selected record (step S114).

  If there is a matching rule (YES in step S113), the specifying unit 17 acquires, from the operation procedure generation rule 150, related information between elements in the extracted rule (step S115). The specifying unit 17 records information indicating the relationship between the elements obtained by assigning the work target of the start point and the work target of the end point to the work target of the related information between the acquired elements in the related information estimated in the result table. (Step S116).

  The identifying unit 17 determines whether the processing has been completed for all the records in the result table (step S117). If the processing has not been completed for all the records (NO in step S117), the specifying unit 17 returns to the processing in step S110 and proceeds to the processing for the next record. If the processing has been completed for all the records (YES in step S117), the specifying unit 17 ends the processing.

  FIG. 29 is a flowchart of a result determination process performed by the update unit according to this embodiment.

  For example, the update unit 18 selects one record in the result table as shown in FIG. 17 (step S120). The update unit 18 determines whether the appearance procedure of the selected record is an existing procedure (step S121). If the appearance procedure is an existing procedure (YES in step S121), the updating unit 18 records “addition” in the determination result of the selected record (step S122). The update unit 18 determines whether the processing has been completed for all the records in the result table (step S123). If the processing has not been completed for all the records (NO in step S123), the update unit 18 returns to the processing in step S120 and proceeds to the processing for the next record.

  If the processing has been completed for all the records (YES in step S123), the updating unit 18 selects one record that does not yet have a determination result in the result table (step S124). The update unit 18 determines whether the difference work target of the selected record matches the work target of the starting point (step S125). If the difference work target and the start work object match (YES in step S125), the update unit 18 records “delete” in the determination result of the selected record (step S126). The update unit 18 determines whether the processing has been completed for all the records in the result table (step S127). If the processing has not been completed for all the records (NO in step S127), the updating unit 18 returns to the processing in step S124 and proceeds to processing for the next record.

  If the processing has been completed for all the records (YES in step S127), the updating unit 18 selects one record that does not yet have a determination result in the result table (step S128). The update unit 18 records “no processing” in the determination result of the selected record (step S129). The update unit 18 determines whether the processing has been completed for all the records in the result table (step S130). If the processing has not been completed for all the records (NO in step S130), the updating unit 18 returns to the processing in step S128 and proceeds to the processing for the next record. If the processing has been completed for all the records (YES in step S130), the updating unit 18 ends the processing.

  Next, the work procedure automatic generation process will be described in more detail.

  FIG. 30 is a diagram illustrating a configuration example of the relationship estimation device 10 according to the present embodiment.

  The relation estimation apparatus 10 shown in FIG. 30 includes a work input unit 40, and the rule storage unit 15 stores a work procedure rule 210 and a procedure rewrite rule 220. The configuration example of the relationship estimation device 10 shown in FIG. 30 shows the configuration example shown in FIG. 6 in more detail, and the same processing units are given the same numbers.

  The work input unit 40 inputs a work to be operated in a work target system that generates a work procedure. The input work is indicated by a set of (work element, work target).

  The work procedure rule 210 is a rule that expands a parent element (higher element) to a child element (lower element) between hierarchized elements constituting a work, and the work element input by the work input unit 40 , A rule that expands to “operation” as the lowest element.

  The procedure rewrite rule 220 is a rule that rewrites a given work based on the work elements and work target attributes defined in the work procedure rule 210.

  The procedure generation unit 14 and the work input unit 40 correspond to the automatic generation rule already described, and the work procedure rule and the procedure rewrite rule 220 correspond to the operation procedure generation rule 150, respectively.

  The work procedure generated by the procedure generator 14 is a sequence of a plurality of operations (Instructions) indicating work procedures operated in the work target system, as shown in the procedure manual of FIG. 4B. The contents of work to be operated can be defined using hierarchical classification (class).

  FIG. 31 is a diagram illustrating a definition example having a hierarchical structure regarding the contents of work to be operated.

  The work to be operated can be defined, for example, in a hierarchical class of tasks, tasks, procedures, and operations from the upper level.

  A task (Task) is a class according to business classification. One task has a classification called one or a plurality of works. A work is a class that is a basic unit. One work has a classification called one or a plurality of procedures. A procedure is a work step that realizes a workpiece. A procedure has one or more instruction classifications. An entire work defined by each hierarchical classification of task, work, procedure, and operation is called an action. In the following description, components such as applications and devices constituting the work target system may be referred to as work targets or targets.

  Based on the action shown in FIG. 31, the procedure generation unit 14 rewrites the work level set (work element, target) input by the work input unit 40 to generate the operation level set (operation, target). You can say that.

  FIG. 32 is a diagram illustrating an example of the element information 120 in the system configuration information of the work target system in an example of work procedure generation processing.

  32 is information obtained by adding an attribute to the element information 120 shown in FIG. The attribute defines a more detailed type for each type of component. For example, “Redundancy-Active” “StandBy” or the like. “Redundancy-Active” indicates that the component is in operation of the redundant system, and “StandBy” indicates that the component is on standby.

  FIG. 33 is a diagram illustrating an example of the related information 121.

  The related information 121 in FIG. 33 is information showing the definition of the related information 121 shown in FIG. 1C in more detail. It shows that the operation “Upgrade (LayerUp)” at the time of rewriting corresponds to the type “Server / application related”, and the operation “Depend” at the time of rewriting corresponds to “Server related”.

  The work procedure rule 210 has a work development rule 211 for expanding a work into a procedure in the hierarchy shown in FIG. 30, and a procedure expansion rule 212 for expanding a procedure into an operation.

  FIG. 34 is a diagram illustrating an example of the work development rule 211.

The work expansion rule 211 is indicated by a description that, as described below, a work that is an upper element is represented on the left side, a procedure that is a lower element is represented on the right side, and the left side is expanded on the right side.
(WorkName, WorkAttribute, TargetClass, Condition) → (ProcedureName) column In FIG. 34, the work expansion rule 211 is represented in a data table format.

  RuleID is a rule identification number. WorkName is the name of the work, and “Start”, “Stop”, “Patch Application”, etc. are defined. WorkAttribute is a work attribute, and “stop”, “start”, “normal”, and the like are defined. “Stop” indicates that the work belongs to the stop work, “start” belongs to the start work, and “normal” belongs to the normal work.

  TargetClass is a classification (class) of work objects, and classifications such as “server” and “application” are defined. Condition is a condition for applying a rule, and a server type, an OS type, and the like are set.

  ProcedureName is a procedure to be expanded, and it is possible to set a sequence of procedures, work, etc. in addition to a single procedure. For example, in the rule with the rule identification number RuleID “W7”, the work “patch application” is “stop” for the work class (represented as <work>), “patch application” for the procedure class, and “start” for the work class. It means that it will be expanded.

  FIG. 35 is a diagram showing an example of the procedure development rule 212.

  Similarly to the work expansion rule 211, the procedure expansion rule 212 is also indicated by a description that a procedure that is a higher element is represented on the left side and an operation that is a lower element is represented on the right side, and the left side is expanded on the right side. It is an example which represents the rule 212 in a data table format.

  ProcedureName is the name of the procedure, and “server stop / start”, “job net stop / start”, “daemon stop / start”, “patch application”, etc. are defined. ProcedureAttribute is an attribute of a procedure, and “stop”, “start”, “normal”, and the like are defined in the same manner as the work.

  InstructionName is an operation to be expanded, and one or more operations are set. The operations are "server node stop / start", "server node stop / start check", "job net stop / start", "job net stop / start check", "daemon stop / start", "daemon stop / start check" "Patch module preparation", "Patch application", "Patch application confirmation", etc.

  FIG. 36 is a diagram illustrating an example of the procedure rewrite rule 220.

  The procedure rewriting rule 220 is a rule for rewriting a given work to a new work element or work procedure based on the work element or work target attribute when the work is developed. The procedure rewriting rule 220 shown in FIG. 36 represents the rule of rewriting from the left side (procedure X) to the right side (procedures Y1, Y2,...) In XML format description.

  <Rule> is rule identification information, and <Node> is an element to be rewritten. <Left> represents information on the left side, and <Right> represents information on the right side.

  <actionClass> indicates the class in the action of the element to be rewritten, and is set to work, procedure, or operation. <actionAttribute> is an attribute of the element to be rewritten.

  <objectFunction> represents the setting of a work element to be rewritten (operation at the time of development), and for example, “LayerUp”, “Depend”, and the like are set. “LayerUp” is an operation for upgrading the component to be rewritten to the component one layer above. “Depend” is an operation for specifying the relation source based on the relation of the target component.

  FIG. 37 is a diagram for explaining “LayerUp”. When the configuration of the work target system shown in FIG. 32 has the hierarchical structure shown in FIG. 37, “LayerUp” means that the component of the hierarchy immediately above the target component is specified. For example, when the work target is “OS”, “middleware” in the immediately higher hierarchy is the target, and when the work target is “application”, the “SLB service” in the immediately higher hierarchy is the target.

  <actionFunction> represents the operation when rewriting. For example, “Expand” is set. “Expand” is an operation of expanding a work to be rewritten (work element, work target) into a lower work hierarchy.

  FIG. 36A shows an example of a rewrite rule when RuleID is “R8”, <actionAttribute> is stop, and <actionClass> is Work, and targets all the dependency sources of the rewrite target. And <actionFuntion> is a rule that rewrites the work element as the result of the rewrite operation of Expand. FIG. 36B shows a rewrite rule when RuleID is “R5”, <actionAttribute> is “stop”, and <actionClass> is “Procedure”. And <actionFunction> is a rule that rewrites the work element that is the rewrite operation result of Expand.

  Next, the automatic generation of work procedures will be described more specifically.

  FIG. 38 is a diagram illustrating a configuration example of the work target system and an example of information in a specific example of processing. 38A is an image diagram of the assumed configuration of the work target system, FIG. 38B is a diagram showing the configuration information 120 of the work target system, and FIG. 38C is a diagram showing the related information 121. .

  Assumed work systems are "Web Server (Web Server)" which is a logical server connected to the Internet, and "Apl1 Server (Apl1 Server)" which is a logical server that acquires data from "Web Server". Are linked. The application daemon “apache” is executed on “Web Server”, and the application job net “jobnet” is executed on “Apl1 Server”.

  The procedure generation unit 14 performs the following processing. 39 to 45 are diagrams illustrating examples of tree structures generated during processing.

  (1) It is assumed that the work input unit 40 is a set of (stop, Apl1 Server) that is one of work-level works (work elements, work targets) constituting a task.

  As shown in FIG. 39, the procedure generation unit 14 prepares a tree structure, and adds the input (stop, Apl1 Server) set as a child node of the root (Root) to the tree structure. A set which is each processing target in the tree structure is called a node.

  (2) The procedure generation unit 14 refers to the element information 120 and the related information 121, identifies <actionClass> and <actionAttribute> of the input work element, and checks whether there is a corresponding procedure rewrite rule 220. Since the <actionClass> of “stop” is Work and <actionAttribute> is “stop” from the work expansion rule 211, the rule of “R8” is matched with the condition of <Left> of the rule “R8” of the procedure rewrite rule 220 Apply.

  The procedure generation unit 14 specifies the component “Web Server” of the relation source of the target “Apl1 Server” from <objectFuntion> Depend that is the condition of the first node of <Right> of the rewrite rule “R8” ( Stop, Web Server) pair is generated. Then, as shown in FIG. 40, the set generated in the tree structure is added as an elder brother node so that the relationship between the nodes in the same hierarchy (work level) and the node is “association source” → “association destination”.

  (3) Furthermore, by <actionFunction> Expand which is the node condition next to <Right> of “R8”, the procedure generation unit 14 “stops the work from the work expansion rule 211 for the (stop, Apl1 Server) pair. The rule “W1” is applied and rewritten to a lower-level procedure level (server stop, Apl1 Server) group, and as shown in FIG. 41, the tree structure is rewritten (stop, Apl1 Server). Add as a child node of.

    (4) The procedure generation unit 14 checks whether there is a procedure rewrite rule 220 corresponding to a procedure level (physical server stop, Apl1 Server) group. Since <actionClass> of “Server stop” is Procedure and <actionAttribute> is “stop” from the work deployment rule 212, the rule “R5” is set to match the <Left> condition of the rule “R5” of the procedure rewrite rule 220. Apply.

  From the <objectFuntion> LayerUp that is the condition of the first node of <Right> of the rewrite rule “R5”, the procedure generation unit 14 obtains the component “jobnet” in the layer immediately above the target “Apl1 Server” from the element information 120. Identify and generate (Jobnet stop, jobnet). Then, as shown in FIG. 42, the set generated in the tree structure is added as an elder node so that the previous hierarchy of nodes in the same hierarchy (work level) is “higher component” → “lower component”. To do.

  (5) Furthermore, the procedure generation unit 14 applies the rule “P1” in which the server is “stopped” from the procedure expansion rule 212 according to <actionFunction> Expand which is the node condition next to <Right> of “R5”. Then, the procedure level (server stop, Apl1 Server) is rewritten to a set of lower level operation level (server node stop, Apl1 Server), (server node stop confirmation, Apl1 Server). Add as a child node to the structure.

  Note that the work (job net stop, jobnet) is similarly rewritten to a set of (job net stop, jobnet) and (job net stop confirmation, jobnet), and as shown in FIG. 44, as a child node in the tree structure to add.

  (6) The rewriting process shown in the above (2) to (5) is executed until all the sets are expanded to (operation, target). For the work (stop, Web server) generated in (2) above, the processes (3) to (5) are performed in the same manner as the original work.

  (7) As shown in FIG. 45, when all the pairs are expanded into operation level pairs (operations and targets), the operation level pairs are taken out in order from the first node based on the posterior relationship of the nodes. A set of (operation, target) is used as a work procedure.

  FIG. 46 is a diagram illustrating an example of a work procedure based on a column of operation level sets (operations and targets) taken out.

  FIG. 47 is a diagram illustrating an example of a processing flow of work procedure generation processing.

  The procedure generation unit 14 sets a target (work level work element, target) set input by the work input unit 40 as a child node of the root of the tree structure (step S150).

  The procedure generation unit 14 determines whether there is a node other than the operation level (step S151), and if there is a node other than the operation level (Y in step S151), sets the node other than the operation level as a processing target (step S151). S152).

  The procedure generation unit 14 selects the work procedure rule 210 or the procedure rewrite rule 220 (rule in which the condition on the left side of the rule matches the work element) that matches the processing target node (step S153), and the right side of the selected rule. A rewritten node is generated (step S154).

  The procedure generator 14 determines whether the hierarchy (see FIG. 31) in the action of the newly generated node is the same as the node to be processed (step S155), and if the hierarchy is the same (Y in step S155). The newly generated node is added to the tree structure as a preceding node (brother node) at the same level as the processing target node (step S156). If the hierarchies are not the same (N in Step S155), the procedure generation unit 14 adds the newly generated node to the tree structure as a node (child node) one level below the processing target node (Step S157). .

  If there is no node other than the operation level in the process of step S151 (N of step S151), the procedure generation unit 14 sequentially outputs the end node (operation level node) of the generated tree structure (step S158).

  With the relation estimation device 10 according to the present embodiment described above, it is possible to estimate relation information between elements constituting the work target system, which is insufficient in the system configuration information of the work target system. This makes it easy to introduce technology that automatically generates work procedures for systems that are already in operation. Actually, it takes many days to manually extract and acquire related information from a plurality of documents and setting information. However, if the related estimation device 10 according to the present embodiment is used, it is mechanically used. Since it can be processed, related information can be acquired in a short time.

  Note that the technique for estimating the relation between elements constituting the system by the relation estimation apparatus 10 of the present embodiment can be used for purposes other than the automatic generation of work procedures. For example, since the relationship between the applications can be estimated by the relationship estimation apparatus 10 according to the present embodiment, the operation state of the application in the system can be understood by analyzing the result. Based on such information, the application can be modified so that a simpler system can be operated.

  Further, the relation estimation device 10 expands the work from the work contents indicated by the superordinate concept to the system structural elements set as work targets and the structurally related elements, and changes the work contents to the operation level. It is possible to automatically generate an operation level work procedure by expanding to the above work. As a result, the workload for creating the work procedure itself can be reduced.

  Although the present embodiment has been described above, the present invention can naturally be modified in various ways within the scope of the gist thereof.

DESCRIPTION OF SYMBOLS 10 Relational estimation apparatus 11 Configuration information acquisition part 12 Configuration information storage part 13 Procedure acquisition part 14 Procedure generation part 15 Rule storage part 16 Difference extraction part 17 Identification part 18 Update part 19 Output part 20 CMDB
30 Procedure information storage unit

Claims (6)

Computer
Obtain a first work procedure that indicates the order of operations to be performed on the work target system,
In accordance with information in which a correspondence between elements in a system composed of hardware or software elements and a correspondence between the work procedures is defined, information indicating a relation between elements in the work target system is used to determine the first work procedure and Automatically generate a second procedure for the same purpose,
Extracting a work procedure which is a difference between the first work procedure and the second work procedure;
A relation estimation program for executing a process of identifying a relation between elements in the work target system, which causes the work procedure to be the difference using the information in which the correspondence is defined. In addition to the computer,
When the work procedure to be the difference is a work procedure included in the first work procedure, the relationship between the identified elements is added to the information indicating the relationship between the elements,
When the difference work procedure is a work procedure included in the second work procedure, the work target element that caused the difference work procedure is the first difference in the difference work procedure. The relation estimation program according to claim 1, for executing a process of deleting the relation between the identified elements from the information indicating the relation between the elements if the element is a target to be worked on. 2. The process of acquiring the first work procedure includes acquiring the first work procedure by automatically extracting the work procedure from a document file in which the work procedure is described. Or the related estimation program of Claim 2. A procedure acquisition unit for acquiring a first work procedure indicating an order of operations to be performed on the work target system;
In accordance with information in which a correspondence between elements in a system composed of hardware or software elements and a correspondence between the work procedures is defined, information indicating a relation between elements in the work target system is used to determine the first work procedure and A procedure generator for automatically generating a second work procedure of the same purpose;
A difference extraction unit that extracts a work procedure that is a difference between the first work procedure and the second work procedure;
An association estimation apparatus comprising: a specifying unit that identifies an association between elements in the work target system that generates the work procedure as the difference using the information in which the correspondence is defined. Computer
Obtain a first work procedure that indicates the order of operations to be performed on the work target system,
In accordance with information in which a correspondence between elements in a system composed of hardware or software elements and a correspondence between the work procedures is defined, information indicating a relation between elements in the work target system is used to determine the first work procedure and Automatically generate a second procedure for the same purpose,
Extracting a work procedure which is a difference between the first work procedure and the second work procedure;
A relation estimation method characterized by executing a process of identifying a relation between elements in the work target system, which generates the work procedure as the difference, using the information in which the correspondence is defined. In the computer,
When automatically generating the second work procedure,
As a work to be performed on the work target system, information indicating a work set including a work element and a work target is acquired,
Based on the information indicating the relationship between the elements in the system, a set of tasks is generated from the acquired set of tasks and the other elements related to the target of the set are set as work targets, and the work elements are classified hierarchically. Based on the information including the classification indicating the operation in the lower hierarchy and the acquired work set and the generated work set are expanded to the work element of the classification indicating the operation, and the classification of the classification indicating the expanded operation The relation estimation program according to claim 1, for causing the processing to generate the second work procedure from a set of work elements and work targets.

Images