JP6655497B2 - Operation management device, operation management method, and operation management system - Google Patents

Description

  The present invention relates to an operation management apparatus, an operation management method, and an operation management system, and more particularly, to centrally manage information from a control facility and information from a computer facility associated therewith, and flexibly control information including an operation policy. The present invention is suitably applied to an operation management apparatus, an operation management method, and an operation management system including a combination, an operation management responsibility range, and the like.

  2. Description of the Related Art In recent years, technical development for the purpose of increasing the reliability of system operation has been performed. In the conventional system operation management system, information is managed using a relational database (hereinafter abbreviated as “database”) regarding a control facility and a service management platform (hereinafter, “control facility” is exemplified) on the site side ( Patent Document 1, Non-Patent Document 1). In other words, in the conventional system operation management system, the system structure and the rules for operation that are assumed in advance according to the site side are embodied as a data structure type, and operation management is performed according to a fixed operation policy for the data type. Is going.

Japanese Patent No. 4300149

"Development of Real-Time SGL Purification Unit for Manufacturing Equipment" Transactions of Information Processing Society of Japan Database Vol. 2 No. 2 p. p. 137-146 (June 2009)

  In conventional system operation, information required for management of control equipment on the site side is managed by a database, but the above-mentioned system operation management system program often involves database design, and the database Developed in close association. For this reason, similar increase in the number of managed objects can be handled, but system specifications cannot be easily changed in response to changes in on-site control equipment, etc., and flexible management of on-site control equipment etc. Was difficult. Further, when utilizing a relational database, the operation policy depends on the data type and is associated with each other, so that the operation policy for a range including a plurality of data structures cannot be set.

  The present invention has been made in view of the above points, and provides an operation management apparatus, an operation management method, and an operation management system that can flexibly manage the on-site control equipment and accompanying computer equipment in consideration of the scope of operation management responsibility. It is something to propose.

  In order to solve such a problem, an operation management apparatus according to the present invention provides a physical and logical inclusion relationship of each component including a control facility and an associated computer facility constituting a system, and a configuration information indicating each of the components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing each of the structured identification information represented by a tree structure including each of the logical inclusion identification information associated with the configuration, A combination management unit that manages a combination of each configuration control policy program corresponding to an element and each logical inclusion identification information corresponding to each configuration information indicating each configuration element; When recognizing one logical inclusion identification information, target range information indicating a range of a processing target, execution authority range information indicating a range of execution authority of each of the configuration control policy programs, and A necessary configuration control policy program among the respective configuration control policy programs, based on the influence range information indicating an influence range when each of the configuration control policy programs is executed, and And a program execution unit for executing the program.

  Also, the operation management method according to the present invention is an operation management method in an operation management device including an identification information management unit, a combination management unit, and a program execution unit, wherein the identification information management unit includes Each structured identification that represents the physical and logical inclusion relationship of each component including the accompanying computer equipment in a tree structure, including each logical inclusion identification information associated with each configuration information indicating each component. While managing as information, the identification information management step of specifying the management target by the information of the identification information management unit that manages the uniqueness of each of the structured identification information, and the combination management unit corresponds to each of the constituent elements. A combination management program that manages a combination of each configuration control policy program and each logical inclusion identification information corresponding to each configuration information indicating each configuration element. Step, when the program execution unit recognizes one of the logical inclusion identification information pieces of the logical inclusion identification information, target range information indicating a range of a processing target, and the program of the operation management device described above. Based on execution authority range information indicating a range of execution authority of the control policy program and influence range information indicating an influence range when each of the configuration control policy programs is executed, from among the respective configuration control policy programs, A program execution step of specifying a necessary configuration control policy program and executing the specified configuration control policy program.

  Further, the operation management system according to the present invention is a system in which the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system are associated with the respective configuration information indicating the respective components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing each of the structured identification information expressed in a tree structure including the logical inclusion identification information, A combination management unit that manages a combination of a configuration control policy program and each of the logical inclusion identification information corresponding to each of the configuration information indicating each of the configuration elements; and a logical inclusion of one of the logical inclusion identification information When the identification information is recognized, target range information indicating a range of a processing target, execution authority range information indicating a range of execution authority of each of the configuration control policy programs, and each of the configuration controls A required configuration control policy program is specified from the respective configuration control policy programs based on the influence range information indicating an influence range when the policy program is executed, and the specified configuration control policy program is executed. And an operation management device including a program execution unit, and a user device that uses the control equipment and the associated computer equipment.

  According to the present invention, it is possible to flexibly manage on-site control equipment and accompanying computer equipment in consideration of the scope of operation management responsibility.

FIG. 1 is a block diagram illustrating a schematic configuration example of an operation management system according to a first embodiment. FIG. 2 is a conceptual diagram illustrating a system configuration and an example of a structured ID defined so as to manage the consistency of the entire range of the system configuration. FIG. 2 is a block diagram illustrating a physical configuration example of a redundant system as an example to which the first embodiment is applied; It is a conceptual diagram which shows an example of the structured ID which redefined the system configuration of the redundant system as a data structure and defined it. FIG. 9 is a screen diagram showing an example of editing a structured ID representing the configuration of a redundant system. FIG. 11 is a table configuration diagram showing an example of a table set by selecting an identifier representing a redundant physical machine and registering the actual state of a program. FIG. 13 is a screen diagram showing an example of a manner in which a redundant system policy program is set in a structured ID representing the configuration of a redundant system in a retrofit manner. FIG. 11 is a diagram illustrating an example of a management table for managing accumulated data of target range information of a redundant policy program after a redundant policy program is set in a structured ID representing a configuration of a redundant system after the redundant policy program. FIG. 9 is a diagram illustrating an example of correspondence between a failure handling policy program for an individual mounting failure and a failure (target range information) exceeding its operational management responsibility range. 9 is a flowchart illustrating an example of a configuration control process from failure detection to configuration control. It is an example of the notification message in the HMI in which the feature of the configuration control is reflected. It is a figure which shows an example of the state information extension management table, and an example of the technique which extended the state information by the wrapper ID. FIG. 3 is a diagram illustrating an example of a design mode of a structured ID including definitions of a physical machine and a virtual machine. FIG. 3 is a diagram illustrating an example of a branch-like structured ID that defines a relationship between a physical machine and a virtual machine, and an example of a relationship link definition table. 19 is a flowchart illustrating an example of a relocation management process for relocating a virtual machine between physical machines.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
(1) Background of One Embodiment of the Present Invention In one embodiment of the present invention (hereinafter, referred to as “the present embodiment”), first, as a premise, control which is to be managed by a control facility operation management device is assumed. An identifier is assigned to a facility (also referred to as a "field device") or a computer facility, and a failure notification unit (corresponding to a failure notification and configuration control execution unit 113, 213, 313 in FIG. 1 described later) in the control facility or the computer facility. ), The control equipment and the computer equipment are managed by associating the information obtained in the above with the assigned identifier.

  In most cases, information required for management of such control equipment is generally stored and managed in a database by designing a database. In this case, it is implicitly assumed that one component provider (component vendor) designs the entire control system including the control device and the like because of the necessity of designing the database.

  In such a case, the SCADA or the business application that manages the control equipment employs a method of uniquely specifying the target information by using the location information of the database or a query. It is likely that the operation management device and the database need to be provided integrally by a single component provider, which may make it difficult to easily change the system configuration and to gradually expand software from hardware. is there.

  Hereinafter, in the present embodiment, the fact that a close relationship is formed between the control facility operation management device and the database in this manner is also referred to as “tight coupling”. On the other hand, SQL (Structured Query Language) used in a database has a high degree of freedom in expression, and it is possible to uniquely identify information to be managed by performing necessary parsing, while identifying uniqueness by simple character string comparison. Therefore, it is difficult to utilize the SQL itself as identification information of each control facility.

  Therefore, in the present embodiment, although details will be described later, control equipment having different design timing or architecture (also referred to as “field equipment”) and information acquired by the failure notification unit of the equipment and the equipment structure are uniquely identified. Encoding is performed using possible identifiers, and the plurality of identifiers are connected to each other to ensure the uniqueness of the plurality of identifiers. This manages arbitrary information and system structures from hardware, software, and abstract concepts to implementation-dependent identification and fault identifiers.

  Further, in the present embodiment, in order to establish a parent-child relationship between identifiers, and to identify a plurality of control facilities and associated computer facilities from each other using a tree structure representing such parent-child relationships, identifiers having a parent-child relationship are used. To join. At the time of such coupling, in the present embodiment, a control equipment operation management device (corresponding to a control equipment operation management device 700 in FIG. 1 described later) and computer equipment associated therewith are modeled between the identifiers. Logical inclusion identification information (corresponding to a wrapper ID described later).

  Further, a redundant system abstract concept identifier (corresponding to the redundant system abstract concept identifiers 800a and 800b in FIGS. 4A and 4B to be described later) for identifying the redundant system configuration is used as the upper identifier of the logical inclusion identification information. By newly defining, the redundant system can be controlled.

  As will be described in detail later, the control equipment operation management apparatus uses a combination of a structured ID structured by combining identifiers and logical inclusion identification information, and information on control equipment to be managed and associated computer equipment. Managing.

  In the present embodiment, when processing is performed in response to a request for utilizing such a management target, when a certain identifier is specified, the management target is determined based on the logical inclusion identification information combined with this identifier. The physical location of the information about the management target is specified, and as a result, the information about the management target is provided.

  On the other hand, in the present embodiment, when a control command is issued to the control equipment or the associated computer equipment as such a management target, the structured ID representing the management target is received from the user as an opportunity. By transmitting a control command to a control facility to be subjected to the structured ID or a computer facility associated with the structured ID, or by writing the control command to a control interface (hereinafter abbreviated as “control IF”), Via the control IF, control equipment to be managed and computer equipment associated therewith are controlled. Hereinafter, the concept of the present invention will be described more specifically.

  Further, for an issue including a plurality of operation management responsibilities described later, a wrapper ID is set at a decomposition point of operation management authority (corresponding to each of the attachment / detachment points P, P0 to P4 described later in the structured ID), Implement configuration control based on the equipment structure, fault range, and operation management responsibility

(2) First Embodiment (2-1) Overall Configuration of Operation Management System FIG. 1 shows a schematic configuration example of an operation management system 1000 according to the first embodiment. Since the control equipment is often configured as hardware, in the present embodiment, a redundantly configured system is exemplified as complicated computer equipment such as hardware, prerequisite middleware, and applications. In the following embodiments, components having the same reference numerals are basically the same components and perform the same operations in principle, and therefore, the description of the components having the same reference numerals will be omitted in principle.

  The operation management system 1000 calculates, for example, information acquired by a failure notification unit in a computer facility (corresponding to a computer facility associated with a control facility configuring the system) as a target component in the present embodiment. It is managed in association with the identifier assigned to the equipment.

  The computer equipment here is roughly divided into three types of systems: a system to be controlled as a source of information, a management device for the information, and a system to a user of the information. The control target side system of the information source, the information management device, and the user side system of the information are connected to each other via the network 400, and are configured to be able to exchange information with each other. I have.

  The system to be controlled as a source of the information described above is, for example, the redundant physical machine 100 (hereinafter also referred to as “redundant physical machine A”) and the redundant physical machine 200 (hereinafter “redundant physical machine B”) in FIG. ) And the redundant physical machine 300 (hereinafter also referred to as “redundant physical machine C”).

  The information management device described above corresponds to, for example, the control facility operation management device 700 and the recording medium 771 in FIG. The above-described information user system corresponds to, for example, an HMI (Human Machine Interface) 500 in FIG.

(2-2) System to be Controlled as Information Source The operation management system 1000 includes, as described above, the redundant physical machine 100, the redundant physical machine 200, and the redundant physical A machine 300 is provided, and a redundant system abstract concept identifier 800 is configured as a component that logically represents a redundant system. Since the redundant physical machine 200 and the redundant physical machine 300 have almost the same configuration as the redundant physical machine 100, in the following description, the redundant physical machine 100 will mainly be described for the internal configuration.

  This redundant system has, as an example, a dual Duplex system and a dual Dual system as described later. Therefore, in the present embodiment, redundant system abstract concept identifiers 800a and 800b are used as components that logically represent the duplex system Duplex and the duplex system Dual (for example, FIGS. 3, 4 to 9). And FIG. 13).

  The redundant physical machine 100 is a type of computer like the control facility operation management device 700, and mainly includes a memory 110 and a communication interface 120. The memory 110 includes an application program 111, middleware 112, and a failure notification and configuration control execution unit 113. The failure notification and configuration control execution unit 113 has an entity of a failure response policy program registered in a failure response policy program 776Cc described later in FIG. 9 and an execution environment thereof. The middleware 112 is at least one of hardware and software on which the application program 111 operates, and is also referred to as “middleware” in the following description.

  The redundant physical machine 100, the redundant physical machine 200, and the redundant physical machine 300 are each a kind of computer, and are named “redundant physical machine A”, “redundant physical machine B”, and “redundant physical machine”. Machine C "is also used. The redundant physical machine 100, the redundant physical machine 200, and the redundant physical machine 300 respectively include the above-described middleware 112 and the internal functions of the failure notification and configuration control execution unit 113 (the actual failure handling policy program and its Utilizing the execution environment and the function of the failure notifying unit described above), for example, information of an operation state is transmitted to the control equipment operation management device 700 as described later, or in response to a control command. Start various programs and perform configuration control.

  Note that the redundant physical machine 100, the redundant physical machine 200, and the redundant physical machine 300 are given as an example of a target to be distinguished from the entire operation management system 1000 represented by the redundant abstract concept identifier 800.

(2-3) Information User System The operation management system 1000 includes the HMI 500 as the information user system as described above. The HMI 500 is a computer like the control facility operation management device 700, has a communication IF 520, a CPU 550, and a memory 510, and is connected to a display device 580.

  These communication IF 520, CPU 550, and memory 510 are connected by an internal bus 560. In the memory 510, a setting item input section function 511, a structured ID wrapper operation section 512, and a structured ID reading section 514 are operating, and a structured ID editing table 513 is provided.

(2-4) Information Management Device The operation management system 1000 includes a control facility operation management device 700 and a recording medium 771 as the information management device described above. The control equipment operation management device 700 usually employs a redundant configuration composed of two or more units. However, for simplification of the drawing, in the example shown in the figure, it is exemplified that the control unit is composed of one unit.

  The control equipment operation management device 700 is connected to an external system via a network 400 by a communication interface (abbreviated as “communication IF” in the figure) 720. The control facility operation management device 700 further includes a CPU 750, a memory 710, and a bus 760.

  In the memory 710, a structured ID and wrapper ID management unit 711 that manages all information to be managed, and a structured ID design that designs information necessary for control equipment operation management according to the structured ID and the operation management responsibility range A program management unit 712, a configuration control execution unit 713 that externally executes configuration control on the redundant physical machines 100, 200, and 300, and a program that operates according to the determination based on the structured ID and the operation management responsibility range. And a configuration control policy program management unit 714 for managing the relationship. The structured wrapper ID management unit 711 as an example of the combination management unit includes a configuration control policy program corresponding to each component such as a control facility and an associated computer facility, and a configuration corresponding to each identifier indicating each component. It manages the combination with the conversion ID. Since the identifier management unit is required at both the design stage and the operation management stage, specific examples are shown as the structured ID design program management unit 712 and the configuration control policy program management unit 714. Note that each of the functions operating on the memory 710 can be realized by hardware by configuring a processing unit corresponding to each function as an integrated circuit.

  The control equipment operation management device 700 is different from a method using an existing relational database, and utilizes, for example, KVS (Key Value Store) data management for control system management.

  The control facility operation management device 700 includes the CPU 750 as described above, and each internal function executes a corresponding process by transmitting information, an instruction, and the like via the bus 760 by the CPU 750. Hereinafter, for the sake of simplicity, the description will be made assuming that the internal functions in the control equipment operation management device 700 are realized by a program developed on a memory.

  The control facility operation management device 700 has a recording medium interface (abbreviated as “recording medium IF” in the figure) 730, writes data to the recording medium 771 via the memory 710, and stores the data in the recording medium 771. Read completed data.

  The storage medium 771 stores the combination storage data 772 of the structured ID and the wrapper ID (corresponding to the logical inclusion identification information), the storage data 773 of the abstract structure (identifier) required for the redundant system and the wrapper ID, Structured ID data 774 of configuration and status information, accumulated data 775 of target range information of a redundant policy program, and accumulated data 776 of a failure handling policy program and target range information are recorded.

(2-5) Definition Example of Structured ID FIG. 2 shows an example of the structured ID of the entire range of the system configuration while showing the system configuration. In the illustrated example, the consistency of the entire range of the system configuration is managed. In the present embodiment, in order to handle a plurality of structured IDs having different design timings, encoding is performed by connecting the structured IDs flexibly. In the present embodiment, “encoding” mainly means that identifiers are combined to form a tree structure.

  The structured ID is a root element (parent element: higher-level element) that uses an abstract identifier representing the “system-wide ID” that symbolizes the entire management target, while considering the replacement of a part of the system configuration. And a physical identifier (child element: lower element) as a more specific identifier representing the physical component such as the control equipment and the computer equipment attached thereto.

  In the present embodiment, in such a structured ID, the control equipment corresponding to the entity identifier and the computer equipment associated therewith are not related to the component provider between the abstract identifier and the entity identifier. A wrapper ID that is logically included and modeled is inserted.

  The SI definition unit 772Aa, the wrapper definition unit 772Ab, and the entity definition unit 772Ad as the first tree structure illustrated on the upper side have a one-to-one correspondence between the SI definition unit 772Aa and the entity definition unit 772Ad in the context of the wrapper definition unit 772Ab. In this embodiment, a wrapper definition unit 772Ab is added so as to be logically connected while maintaining the relationship. This is an aspect used when information for limiting the entity definition unit 772Ad is added using the wrapper definition unit 772Ab.

  The SI definition unit 772Aa, the wrapper definition unit 772Ac, and the entity definition unit 772Ae as the second tree structure illustrated below have a logical structure identifier branched between the SI definition unit 772Aa and the wrapper definition unit 772Ac. It is an aspect. This can be defined as the entire identifier including the redundant systems 100, 200, and 300 (redundant system abstract concept identifier 800 in FIG. 1).

  An abstract concept identifier designed by a predetermined person (for example, a system integrator) is set in the SI definition unit 772Aa. In the present embodiment, when the set abstract concept identifiers are represented in a list, the SI definition unit 772Aa is represented by the name “existing definition reference unit” as described later.

  A desired wrapper ID is set in the wrapper definition unit 772Ab and the wrapper definition unit 772Ac. This wrapper ID is inserted between the abstraction identifier of the SI definition unit 772Aa designed earlier and the identifier indicating the specific component provider of the entity definition units 772Ad and 772Ae adopted later. , And logically combine these abstract concept identifiers with the identifiers indicating the component providers.

  The combination of the abstract concept identifier of the SI definition unit 772Aa and the entity identifiers of the entity definition units 772Ad and 772Ae manages control equipment having different design timings and computer equipment associated therewith by the same method regardless of the design timing. Used for In the present embodiment, the combination of these identifiers is flexibly changed as appropriate and combined with the wrapper ID to combine the identifiers into a structured ID as a whole using the concept shown in FIG. In the present embodiment, such conversion into a structured ID is also referred to as “encoding” or “regular expression formalization”.

  FIG. 3 illustrates a physical configuration example of a redundant system as an example to which the first embodiment is applied. The redundant system 800a is a dual Duplex system, and the redundant system 800b is a dual Dual system. The redundant systems 800a and 800b have the same configuration irrespective of the difference in the implementation form and the difference in the redundant policy.

  FIG. 3 illustrates a physical configuration example of a redundant system as an example to which the first embodiment is applied. The redundant system 800a is a dual Duplex system, and the redundant system 800b is a dual Dual system. The redundant systems 800a and 800b have the same configuration irrespective of the difference in the implementation form and the difference in the redundant policy.

  The redundant system 800c is an n-fold system and operates in the last one. On the other hand, the redundant system 800d is a redundant system having a so-called 2out of 3 configuration. Here, the “2 out of 3 configuration” refers to, for example, a configuration in which two out of three units are operated. The configurations are the same regardless of the difference in the mounting form of the redundant systems 800c and 800d and the difference in the redundant policy.

  This is the reason why the operation management method according to the present embodiment adopts a method of flexibly designing by separating the redundant system policy and the implementation specific failure processing.

  FIGS. 4A and 4B are conceptual diagrams each showing a structured ID defined by re-capturing the system configuration of the redundant system as a data structure.

  The abstract structure identifier 775a required for the redundant system shown in FIG. 4A requires, for example, two redundant physical machines 100 and 200. The illustrated example corresponds to FIG. 3 (A), and shows an aspect of an identifier 800a representing a duplex Duplex system and an identifier 800b representing a duplex Dual system. The configuration to which “node #” is added indicates that the configuration includes two redundant physical machines.

  For example, the redundant physical machine 100 (corresponding to the illustrated physical machine (1)) has an implementation definition identifier 774A defined by the vendor A, and the redundant physical machine 200 (corresponding to the illustrated physical machine (2)) is The implementation definition identifier 774B is defined by the vendor B. Each of the implementation definition identifier 774A and the implementation definition identifier 774B is logically associated with the abstract structure identifier 775a required for the redundant system via each wrapper ID (corresponding to the pentagonal part shown in FIG. 4A) of the wrapper definition part. Are associated with each other.

  On the other hand, the abstract structure 775b required for the redundant system shown in FIG. 4B requires, for example, three redundant physical machines 100, 200, and 300. The illustrated example corresponds to FIG. 3 (B) and shows a form of the identifier 800c representing the n-system. This example shows an example of a redundant system that requires three redundant physical machines 100, 200, and 300, for example. In the abstract structure identifier 775b required for the redundant system, the configuration with “node #” in the drawing indicates that there are three or more redundant physical machines.

  The illustrated example also shows a mode of 800d representing a so-called 2out of 3 system. This example shows an example of a redundant system that requires at least two of the three redundant physical machines 100, 200, and 300, for example.

  In the example shown in FIG. 4B, for example, the redundant physical machine 300 (corresponding to the physical machine (3) in the drawing) has an implementation definition identifier 774C defined by the vendor C. This implementation definition identifier 774C is logically linked to and associated with the abstract structure identifier 775b required for the redundant system via each wrapper ID (corresponding to the pentagonal part shown in FIG. 4B) of the wrapper definition part. Have been.

  FIG. 5 shows an example of editing a structured ID representing an abstract configuration of a redundant system. This screen 580A is displayed on the display device 580 when the structured ID is edited by utilizing the function of the setting item input unit function 511 in the above-described HMI 500 (see FIG. 1) as the information user side system. FIG.

  The screen 580A includes an abstract structure identifier required for the redundant system shown in FIG. 4A as a list 580Ab represented by a so-called drop-down selection form in a cited section 580Aa of the abstract structure required for the redundant system. 775a and an abstract structure identifier 775b required for the redundant system shown in FIG. 4B are displayed.

  This screen 580A displays an entity definition unit 580Ad as an input form to which an implementation definition can be added, in addition to the abstract structure reference unit 580Aa required for the redundant system. On the screen, the entity definition unit 580Ad is connected to the above-described abstract structure reference section 580Aa required for the redundant system in association with the abstract structure reference section 580Aa required for the redundant system. The black binding sites that suggest this are shown.

  Further, the screen 580A has a registration button 580Ae for registering and setting a desired identifier input in the input form of the entity definition unit 580Ad. When the registration button 580Ae is pressed, the input information of the entity definition unit 772Ac is registered in association with the identifier of the existing definition reference unit 772Aa as shown in FIG.

  FIGS. 6A and 6B show examples of tables set by selecting an identifier representing a redundant physical machine and registering the actual state of the program. The table to be set is, for example, a combination table 772A of the structured ID and the wrapper ID for managing the accumulated data of the combination of the structured ID and the wrapper ID shown in FIG.

  The combination table 772A of the structured ID and the wrapper ID has an existing definition reference section 772Aa, a wrapper definition section 772Ab, and an entity definition section 772Ac, and desired information is registered in these three types of definition sections 772Aa, 772Ab, and 772Ac. It is configured to be.

  As shown in FIG. 6A, the three types of definition units 772Aa, 772Ab, and 772Ac are distinguished from each other, so that the user's intention can be confirmed when setting as described later. . The record in each row represents the content corresponding to the input content set for the identifier by the user.

  The combination of the abstract concept identifier of the existing definition reference unit 772Aa and the entity identifier of the entity definition unit 772Ac is managed by the same method irrespective of the timing of designing the control equipment having different design timings and the computer equipment associated therewith. Used for In the present embodiment, the combination of these abstract concept identifiers and entity identifiers is flexibly changed as appropriate, and these abstract concept identifiers and entity identifiers are combined with the wrapper ID 772Ab to be combined with each other, as shown in FIG. Encoding is performed as a structured ID using the concept.

  On the other hand, FIG. 6B shows on the memory the storage data 773 of the abstract composition and the wrapper ID required for the emotional house on the recording medium shown in FIG. 1 and the storage data 775 of the target range information of the redundant policy program. The management table 775A indicates that the structured ID registered using the screen 580A shown in FIG. 5 is a setting including the wrapper ID of the redundant system. For clarity, for example, 775 is stored.

  In the management table 775A, stored data 773 of the abstract structure and the wrapper ID data required for the redundant system shown in FIG. 1 is stored in the redundant system control target structured ID 775Aa.

  In the illustrated stage, since the control information including the redundant system policy is not registered in the management table 775A, the structured ID list 775Ab, the redundant system policy program 775Ac, and the target range information 775Ad used for the determination are blank. I have. Note that these blanks are filled in according to the input contents on a screen 580B shown in FIG. 7 described later.

  FIG. 7 shows an example of a manner in which a redundant system policy program is set later on a structured ID representing a system configuration of the redundant system physical machines 100, 200, 300 and the like. In the quoted portion 580Ba of the abstract structure required for the redundant system, a black-filled binding site that implies that these are associated and combined with the mapping 580Bc of the redundant policy program is displayed on the screen. Have been.

  The screen 580B uses the function of the setting item input unit function 511 in the above-described HMI 500 shown in FIG. 1 to display the system structure of the already-set redundant system registration candidate represented in the abstract structure quoting unit 580Ba required for the redundant system. Is selected, and is displayed on the display device 580 when the redundant policy program is set later.

  The screen 580B has, as a so-called drop-down selection form, a cited section 580Ba of an abstract structure required for the redundant system and a list 580Bb of the set, which enable display of a set of redundant system registration candidate identifiers in a menu format. .

  The screen 580B further has a quoting unit 580Bc (corresponding to the mapping of the redundant system policy program shown), and the quoting unit 580Bc is mapped to the quoting unit 580Ba of the abstract structure required for the redundant system. Enables display of policy program candidates.

  Further, the screen 580B has a registration button 580Be for confirming and setting the identifier represented in the input form. When the registration button 580Be is pressed, the determined information is registered in the management table 775B shown in FIG. 8, as described later.

  FIG. 8 shows an example of the management table 775B. The management table 775B manages the accumulated data 775 (see FIG. 1) of the target range information of the redundant policy program after the redundant policy program is added to the structured ID representing the configuration of the redundant system.

  The management table 775B has as its items a redundant system control target structured ID 775Ba, a structured ID list 775Bb used for determination, a redundant system policy program 775Bc, and target range information 775Bd.

  In the management table 775B, as described above, the target range information 775Bd is registered by the redundant policy program that is later associated with the redundant policy program 775Bc using the screen 580B (see FIG. 7).

  The target range information 775Bd is represented in a regular expression format. As a result, even in a design stage in which the identifier indicating the site where an individual failure has occurred in the mounting state of the program is indefinite and the structured ID (hereinafter referred to as “mounted individual failure site structured ID”) is not completely determined, The structured ID can be roughly defined. The individual failure site structured ID is managed in FIG. 9 as described below.

  FIG. 9 shows an example of management of the stored data 776 of the failure response policy program and the target range information on the memory as an operation management responsibility range management table 776C. In the present embodiment, such information on a failure exceeding the operation management responsibility range is also referred to as “target range information”.

  The operation management responsibility range management table 776C has a table structure similar to the table structure of the management table 775B shown in FIG. 8, and as the column items, for example, mounting individual failure part structured ID 776Ca, structured ID list 776Cb, failure handling It has a policy program 776Cc and target range information 776Cd. The target range information 776Cd is represented in a regular expression format.

  In the operation management responsibility range management table 776C, a combination of the mounting individual failure site structured ID 776Ca and the structured ID list 776Cb necessary for determining the same is defined. By setting a plurality of such combinations, it is possible to determine the mounting individual failure site structured ID 776Ca from a plurality of pieces of information.

  The association between the failure handling policy for the individual mounting failure and the failure that exceeds the operation management responsibility range and the operation management responsibility range are determined using the target range information 776Cd as follows.

  The structured ID list 776Cd1 is, for example, a data structure longer than the wrapper ID, and includes a wrapper ID and a corresponding entity definition identifier (entity identifier) in the target range information 776Cd. Since it is within the range, it is determined that the mounted individual failure response program B registered as the failure response policy program 776Cc has the operation management authority.

  On the other hand, for example, the structured ID list 776Cd2 has a data structure shorter than the wrapper ID, and if the target range information 776Cc does not include the mounting individual failure site structured ID, the structured ID list 776Cd2 exceeds the component indicated by the wrapper ID. Indicates that the failure has occurred, or the failure cannot be handled by the mounted individual failure handling program B registered as the failure handling policy program 776Cc.

  As described above, since the operation management authority is determined to be in the configuration control policy program registered in the redundant system policy program 776Bc shown in FIG. 8, the implementation individual registration registered in the failure handling policy program 776Cc shown in FIG. Execution of the failure handling program B is not permitted.

(2-6) Operation Management Method FIG. 10 is a flowchart illustrating an example of a configuration control process from failure detection to configuration control. This configuration control process shows an example of a procedure from failure detection to configuration control. In this configuration control process, the failure response policy program registered as the failure response policy program 776Cc shown in FIG. 9 is used to execute the failure notification and configuration control execution unit 113 of the redundant physical machine 100, the failure notification and the configuration of the redundant physical machine 200, and the like. It is executed in response to a call from one of the control execution unit 213 and the failure notification of the redundant physical machine 300 and the configuration control execution unit 313.

  On the other hand, the redundant policy program registered as the redundant policy program 776Bc shown in FIG. 8 is a computer system to be managed, specifically, for example, when viewed from any of the physical machines 100, 200, and 300, Is executed in response to a call from the configuration control execution unit 713 of the control facility operation management device 700 disposed in the server.

  The failure notification and configuration control execution unit 113, the failure notification and configuration control execution unit 213, and the failure notification and configuration control execution unit 313 can each identify a failure detected at a certain failure site using a structured ID. In addition, it is possible to create failure information including a structured ID including a wrapper ID corresponding to the failure part. When such failure information is created, the failure information is transmitted to the control equipment operation management device 700 (step S1). ).

  In the control equipment operation management device 700, when the structured ID and wrapper ID management unit 711 receives the above-described failure information, it based on the structured ID (including the wrapper ID related to the failure part) included in the failure information. The failure information is included in the failure information based on the registration information of the structured ID list 776Bb and the structured ID list 776Cb (see FIG. 9) managed by the configuration control policy program management unit 714 so as to be used for the determination described below. A failure handling program that requires a failure notification of each computer facility identified by the structured ID is specified, and the failure information is distributed to the specified failure handling program (step S2). In the example of FIG. 9, the failure handling program as the registration information is one of the mounting individual failure handling program A and the mounting individual failure handling program B.

  The failure response policy program registered in the failure response policy program 776Cc can determine the failure state based on the registration information of the structured ID list 776Cb used for the determination. The specified failure handling program determines the failure state from the structured ID list used for the determination, which is specified based on the registration information of the structured ID list 776Cb (see FIG. 9), and performs such a configuration control process. The process is executed in the range of the processing target indicated by the range information 776Cd (step S3).

  The failure response policy program registered in the failure response policy program 776Cc is, as a primary evaluation of the structured ID list 776Cd in the structured ID and wrapper ID management unit 711 of the control equipment operation management device 700 (see FIG. 1), for example, The effect range when the entity of the corresponding fault response policy program is executed in any of the fault notification and configuration control execution units 113, 213, and 313 is determined, and the impact range information representing the impact range is determined by the primary evaluation. , The primary evaluation is shared with the structured ID and wrapper ID management unit 711 (step S4).

  In the control equipment operation management device 700, the structured ID and wrapper ID management unit 711 transmits the execution state of the configuration control process to the HMI 500 (step S5). Further, the configuration control execution unit 713 performs, as a secondary evaluation, whether or not the execution right is out of the range of the execution right based on the execution right range information indicating the range of the execution right of the specific failure handling policy program. It is determined whether or not a failure exceeding the operation management responsibility range has occurred (step S6).

  If the above-mentioned secondary evaluation does not exceed the operation management responsibility range (step S6: NO), the configuration control execution unit 713 ends this series of configuration control processing. On the other hand, if the secondary evaluation exceeds the operation management responsibility range (step S6: YES), the configuration control execution unit 713 determines the range of the failure part as described above, the range of the configuration control such as the execution authority, and the like. Then, the inclusive relation of the operation management responsibility range is confirmed, and the management table 775B (see FIG. 8) is searched based on the confirmation result. The configuration control execution unit 713 identifies the redundant policy program that is expected to achieve the most system recovery and stable operation, executes the identified redundant policy program (step S7), and ends.

  As described above, in the control facility operation management device 700, when the structured wrapper ID management unit 711 as an example recognizes one wrapper ID among the wrapper IDs, the wrapper ID is managed by the configuration control policy program management unit 714. , The processing target range information indicating the processing target range of the failure response policy program, the execution authority range information indicating the execution authority range of each failure response policy program, and the influence range when each failure response policy program is executed. Finally, based on the influence range information to be represented, the necessary policy program is specified from the redundant system policy programs, and as a configuration control policy program specified from a bird's-eye view of the entire control target, the system recovery is performed as described above. In addition, it is possible to execute a redundant policy program that is most expected to operate stably.

  The HMI 500 receives the execution state of the configuration control process transmitted as described above via the communication IF 520, and displays the execution state on the display device 580, for example, as illustrated in FIGS. 11A and 11B. Various messages are displayed as shown in.

  In this way, it is possible to flexibly manage the on-site control equipment and associated computer equipment, particularly the redundant physical machine 100, in consideration of the scope of operation management responsibility.

  Further, the configuration control execution unit 713 manages one component element corresponding to one structured ID recognized as described above and the specified necessary failure response policy program within the same operation management responsibility range. It is determined whether or not the execution of the specified failure response policy program or the redundant policy program is arbitrated in accordance with the result of the determination, and then executed as a necessary configuration control policy program.

  In the control equipment operation management apparatus 700, the structured ID and wrapper ID management unit 711 manages the range of responsibility of each failure handling policy program or redundant policy program using a regular expression format, and performs the operation management. Recognizes the scope of responsibility and controls configuration.

  In the control facility operation management device 700, the configuration control execution unit 713 is in an environment where the above-described failure handling policy program or redundant policy program can be executed with respect to a failure occurrence site in the control facility and the associated computer facility. Is determined, and the specified policy program is executed according to the determination result.

  Also, in the control equipment operation management device 700, the above-described structured ID and wrapper ID management unit 711 operates the same configuration element corresponding to the recognized one structured ID and the specified configuration control policy program in the same operation. It is determined whether or not the management is performed within the management responsibility range, and it is also determined whether or not there is an environment in which the specified configuration control policy program can be executed with respect to the above-described failure site in the control equipment and the associated computer equipment. When it is impossible to execute the specified configuration control policy program according to the determination result, the above-described structured ID and wrapper ID management unit 711 responds to the request including the recognized one structured ID. The notification is made so that the specified configuration control policy program can be executed.

  Further, in the control equipment operation management device 700, as each structured ID, a fixed finite model name is given in advance, and the fixed ID is determined according to the mounting state of each configuration control policy program. And the other structured ID to which another name different from the name of the finite model can be separately given. The structured ID and wrapper ID management unit 711 manages the correspondence between each configuration control policy program corresponding to each of the one structured ID and the other structured ID, and fixes the other names separately given above. The other structured ID re-recognized as the name of the fixed finite model is reset as the one structured ID to which the name of the fixed finite model is given in advance. In this way, the configuration control can be managed relatively easily with only a minimum change in the structured ID.

  In the above manner, similarly, the redundant physical machine 100 and the like can be flexibly managed, and the burden on the administrator can be reduced.

(3) Operation Management System According to Second Embodiment The operation management system according to the second embodiment includes an operation management apparatus 700 of the operation management system according to the first embodiment, in which the application programs 111, 211, and 311 are stored. This is an aspect for a hierarchical structure.

  The operating states of the application programs 111, 211, and 311 depend on the operating states of the middleware 112, 212, and 312 on which they operate, respectively. Therefore, when a failure occurs in the middleware 112, 212, 312 of the application, the application programs 111, 211, 311 may also need to be restarted.

  According to the above-described configuration, not only can substantially the same effects as those of the above-described embodiments be exerted, but also the interdependency between the application programs 111, 211, 311 and the middleware 112, 212, 312. Can also be managed using the method of the first embodiment.

(4) Operation Management System According to Third Embodiment The operation management system according to the third embodiment adopts an aspect using a structured ID as a definition method of a state relating to a complicated facility structure and a computer facility structure. ing.

  The state here is not limited to simple “live (operational state)” and “dead (stop state)”. This is complicated when the system structure and its state are important factors, which are taken into account. If a state transition table is created as in the conventional method, the number of orthogonal components increases and the state transition table cannot be stored in one table or array.

  The extended information of the state of “death” (hereinafter also referred to as “state information”) includes only “stop”, whereas the extended information of the state of “live” includes “master” and “subordinate”. There are multiple systems and application states, and they are not necessarily expanded in a balanced manner.

  In this case, since the extended information is not a definition method in which the relationship with the presupposed state is clearly specified, the extended information lacks flexibility. In the present embodiment, a structured ID and a wrapper ID are defined in the extended information. Use the definition method.

  FIG. 12A shows an example of a state information extension management table 774A, while FIG. 12B shows an example of a method in which existing definition state information representing information on an existing definition state is extended by a wrapper ID. A structured ID 774B illustrated in FIG. 12B is an example in which complicated state information is defined using a structured ID.

  On the other hand, the state information shown in FIG. 12A has items such as an existing definition state, a wrapper ID, and an extension. Specifically, for example, the state of a virtual machine constructed on a physical machine is structured. Includes an example derived and defined by ID.

  These state information apply the concept of the combination using the wrapper ID described so far, for example, as a definition method when connecting structured IDs that define the actual system structure, or, for example, It can be used as a definition method when the state information transitions on condition of a plurality of states such as master and slave states.

  On the other hand, the structured ID 772B shown in FIG. 12 (B) indicates that when a system structure having a redundant system configuration and “master system” and “slave system” exist, these “master system” and “slave system” It defines a logical configuration that allows system switching between systems.

  As described above, the control facility operation management device 700 is an example of the state information identification information of the extension 774Ac indicating the state information of each component while maintaining the relationship of the structured ID of each component as described above. Each structured ID is managed as an example of structured identification information represented by a tree structure in association with each piece of information.

  According to the above-described configuration, not only the same effects as in the first embodiment can be obtained, but also a program is defined from the beginning to define and manage a redundant system configuration. Need not be created, and can be defined by a character string, so that the flexibility in designing state information on the system structure of the redundant system is increased.

  FIG. 13 shows an example of a design mode of a structured ID including definitions of a physical machine and a virtual machine. Since the structured ID of the physical machine and the structured ID of the virtual machine have a predetermined relationship with each other, by combining the predetermined relationship as a parent-child relationship between these structured IDs, the physical machine and the virtual machine Can be defined.

  In this embodiment, the definition of the physical machine and the definition of the virtual machine are comprehensively handled, and are associated with the abstract structure 775c (see FIG. 13) required for the redundant system. The structured ID shown in FIG. 13 includes the wrapper ID of the wrapper definition part. When a virtual machine is relocated among a plurality of physical machines, change management of the redundant system configuration is performed by changing a structured ID of the physical machine from a state before the relocation to a state after the relocation. Can be.

  FIG. 14A shows an example of different branch-like structured IDs that define the relationship between a physical machine and a virtual machine. Note that this branch-shaped portion is illustrated by a broken line, similarly to the relationship between the other components. Since the definitions of the physical machine and the virtual machine have different branch-like structured IDs, the correspondence between the physical machine and the virtual machine is not included in the parent-child relationship shown in FIG.

  For this reason, in the present embodiment, the correspondence between the physical machine and the virtual machine is managed by separately providing the relation link definition table 772B shown in FIG.

  The 772Ba item of the relation link definition table indicates the structured ID of the virtual machine, and the 772Bb item stores the structured ID of the physical machine on which the virtual machine indicated by 772Ba is running. By inspecting all of the related link definition table 772B, the target range information can be grasped.

  More specifically, the relation link definition table 772B illustrated in FIG. 14B includes an abstract structure 775d indicating the correspondence of the structured ID of the redundant virtual machine (also simply referred to as “virtual machine”), and the redundant physical machine It defines an individual correspondence with an abstract structure 775e that represents a correspondence between structured IDs (also simply referred to as “physical machines”).

  Next, a case where a virtual machine is relocated between a plurality of physical machines will be described. Note that relocation refers to moving the location of a virtual machine between a plurality of physical machines.

  When the rearrangement is performed as described above, in the structured ID illustrated in FIG. 14A, the relationship link that manages the correspondence between the physical machine and the virtual machine without changing the structured ID of the physical machine or the structure ID of the virtual machine. By changing only the definition table 772B (see FIG. 14B) from the registration state before the rearrangement to the registration state after the rearrangement, the change management of the redundant system configuration can be performed.

  FIG. 15 illustrates an example of a relocation management process for relocating a virtual machine between a plurality of physical machines. Note that steps S1 and S2 in the figure are the same as steps S1 and S2 in FIG.

  When a virtual machine is relocated between a plurality of physical machines, a redundant policy program is executed. The structured ID representing a virtual machine to be moved between the plurality of physical machines includes a structured ID representing a source physical machine and a structured ID representing a destination physical machine. . This redundant system policy program changes the definition so that the structured ID representing the source physical machine and the structured ID representing the destination physical machine are partially replaced (step S10).

  The redundant policy program stores a definition including a relationship between a virtual machine to be moved between a plurality of physical machines and the plurality of physical machines in a relationship link definition table 772B on the memory 710 or the recording medium 771 (see FIG. ))) (Step S11). Thereafter, the redundant policy program updates the information indicating the relationship between the plurality of structured IDs in the relationship link definition table 772B that manages the relationship between the two (step S11). This redundant policy program changes the registered state before the relocation to the registered state after the relocation in the relation link definition table 772B (see FIG. 14B).

  In the present embodiment, the control facility operation management device 700 includes, as the structured IDs, the respective structured IDs (the physical machine identifiers 774A and 774B as the identifiers corresponding to the physical machines 100 and 200 as the computer facilities). Each of the physical machine structured identification information) and each virtual machine identifier 774A, 774B as an identifier corresponding to a virtual machine that has virtualized a part of the physical machines 100, 200. Each virtual machine structured ID including a physical machine structured identifier corresponding to a machine is managed. Furthermore, when the reallocation is performed by moving the virtual machine between the physical machines 100 and 200, the control facility operation management device 700 performs a process before the reallocation of the virtual machine included in the virtual machine structured ID. While partially changing the structured ID of the old physical machine to the structured ID of the new physical machine after this virtual machine has been relocated, The management information is reset to new various management information including the structured ID of the new physical machine after the rearrangement, and the components constituting the system are re-evaluated.

  According to the above configuration, not only can substantially the same effects as in the above-described embodiments be exerted, but also when a virtual machine is relocated between a plurality of physical machines, Even if the structured ID of the machine itself and the structural ID of the virtual machine are not particularly changed, change management of the redundant system configuration can be performed.

(5) Operation Management System According to Fourth Embodiment The operation management system according to the fourth embodiment has substantially the same configuration and functions as those of the above-described embodiments, and therefore the description will focus on the differences. .

  In the operation management system according to the fourth embodiment, the structured ID and wrapper ID management unit 711 attaches a signature while clearly indicating the operation results of each component including the control equipment and the accompanying computer equipment that constitute the system. The difference is that each structured ID is distributed.

  According to the above-described configuration, it is possible to not only exert substantially the same effects as those of the above-described embodiments, but also to construct a business model by distributing each structured ID.

(6) Other Embodiments The above embodiments are examples for describing the present invention, and are not intended to limit the present invention to only these embodiments. The present invention can be implemented in various forms without departing from the spirit thereof. For example, in the above embodiment, the processing of various programs has been described sequentially, but the present invention is not particularly limited to this. Therefore, as long as no inconsistency occurs in the processing results, the processing order may be changed or the processing may be performed in parallel.

  INDUSTRIAL APPLICABILITY The present invention can be widely applied to an operation management apparatus, an operation management method, and an operation management system for managing control equipment and associated computer equipment constituting a system.

100, 200, 300: redundant physical machines, 111, 211, 311: application programs, 112, 212, 312: middleware, 113, 213, 313: failure notification and configuration control execution unit, 400: network ,
500 HMI 580 Display device 511 Setting item input unit function 512 Structured ID wrapper operation unit 513 Structured ID editing table 514 Structured ID reading unit 700 ... Control equipment operation management device, 720, 120, 220, 320, 520 ... Communication IF, 760, 560 ... Bus, 710, 110, 210, 310, 510 ... Memory, 711 ... Structured ID and wrapper ID Management unit, 712: Structured ID design program management unit, 713: Configuration control execution unit, 714: Configuration control policy program management unit, 750, 550: CPU
730: Recording medium IF, 771: Recording medium, 772: Combined accumulated data of structured ID and wrapper, 773: Accumulated data of wrapper ID and abstract structure required for redundant system, 774: Computer Structured ID data of structure and state information, 775: accumulated data of target range information of redundant policy program, 776: accumulated data of fault response policy program and target range information, 800: redundant system, 1000 ...... Operation management system.

Claims (16)

A tree structure including the physical and logical inclusion relationships of the respective components including the control equipment and the accompanying computer equipment constituting the system, including the respective logical inclusion identification information associated with the respective configuration information indicating the respective components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing as each of the structured identification information represented by
Each configuration control policy program corresponding to each component, a combination management unit that manages a combination of each logical inclusion identification information corresponding to each configuration information indicating each component,
When recognizing one logical inclusion identification information among the respective logical inclusion identification information,
Target range information indicating the range of the processing target;
Execution authority range information indicating a range of execution authority of each of the configuration control policy programs,
Impact range information indicating an impact range when each of the configuration control policy programs is executed;
A program execution unit that specifies a necessary configuration control policy program from among the configuration control policy programs, and executes the specified configuration control policy program.
Equipped with a,
The program execution unit includes:
Determine whether one component corresponding to the recognized one structured identification information and the specified configuration control policy program are managed within the same operation management responsibility range,
An operation management device , wherein after executing arbitration regarding execution of the specified configuration control policy program in accordance with the determination result, the configuration control policy program is executed . The identification information management unit,
Manage the range of responsibility of each of the configuration control policy programs using a regular expression format,
The operation management device according to claim 1 , wherein configuration control is performed while recognizing the operation management responsibility range. The program execution unit includes:
Determining whether there is an environment in which the specified configuration control policy program can be executed with respect to a failure occurrence site in the control equipment and the associated computer equipment, and executing the specified configuration control policy program in accordance with the determination result. The operation management device according to claim 1, wherein A tree structure including the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system, including the respective logical inclusion identification information associated with the respective configuration information indicating the respective components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing as each of the structured identification information represented by
Each configuration control policy program corresponding to each component, a combination management unit that manages a combination of each logical inclusion identification information corresponding to each configuration information indicating each component,
When recognizing one logical inclusion identification information among the respective logical inclusion identification information,
Target range information indicating the range of the processing target;
Execution authority range information indicating a range of execution authority of each of the configuration control policy programs,
Impact range information indicating an impact range when each of the configuration control policy programs is executed;
A program execution unit that specifies a necessary configuration control policy program from among the respective configuration control policy programs, and executes the specified configuration control policy program.
With
The combination management unit includes:
It is determined whether or not one component corresponding to the one recognized structured identification information and the specified configuration control policy program are managed within the same operation management responsibility range. It is determined whether there is an environment in which the specified configuration control policy program can be executed with respect to the failure occurrence site in the computer equipment to be executed, and according to the determination result, if the specified configuration control policy program cannot be executed, the recognized operational management system it and performing a notification to the identified configuration control policy program can be executed in response to a request containing one structuring identity. A tree structure including the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system, including the respective logical inclusion identification information associated with the respective configuration information indicating the respective components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing as each of the structured identification information represented by
Each configuration control policy program corresponding to each component, a combination management unit that manages a combination of each logical inclusion identification information corresponding to each configuration information indicating each component,
When recognizing one logical inclusion identification information among the respective logical inclusion identification information,
Target range information indicating the range of the processing target;
Execution authority range information indicating a range of execution authority of each of the configuration control policy programs,
Impact range information indicating an impact range when each of the configuration control policy programs is executed;
A program execution unit that specifies a necessary configuration control policy program from among the respective configuration control policy programs, and executes the specified configuration control policy program.
With
The identification information management unit, as each of the structured identification information,
One structured identification information to which a fixed finite model name is given in advance,
The other structured identification information to which another name different from the name of the fixed finite model can be separately given according to the mounting state of each of the configuration control policy programs,
Is managed,
The combination management unit includes:
Manages the correspondence relationship of each of the configuration control policy programs corresponding to each of the one structured identification information and the other structured identification information,
The other structured identification information obtained by re-recognizing the other name to be separately given as the fixed finite model name, the one structured identification information to which the fixed finite model name is given in advance. operational management device you characterized in that resetting the information. The identification information management unit,
Managing the structured identification information represented by a tree structure in correspondence with the state information identification information indicating the state information of each of the constituent elements while maintaining the physical and logical inclusion relationships. The operation management device according to claim 1, wherein The identification information management unit, as each of the structured identification information,
Each physical machine structured identification information including each physical machine identification information as identification information corresponding to each physical machine as the computer equipment,
While including each virtual machine identification information as identification information corresponding to a virtual machine obtained by virtualizing a part of the physical machines of the physical machines, a part of the physical machine structured identification information corresponding to the some physical machines is included. Each virtual machine structured identification information, including
Is managed,
The combination management unit includes:
When relocation is performed by moving the virtual machine between the physical machines, the structuring of the old physical machine before the virtual machine included in the virtual machine structuring identification information is relocated. While partially changing the identification information to the structured identification information of the new physical machine after the virtual machine has been relocated, the old various management information including the structured identification information of the old physical machine before the relocation is changed. The method according to claim 4 , wherein the management information is reset to new various management information including the structured identification information of the new physical machine after the rearrangement, and the components constituting the system are re-evaluated. Operation management device. The identification information management unit,
2. The operation management according to claim 1, wherein the structured identification information is distributed with a signature attached while clearly indicating the operation results of each component including the control equipment and the accompanying computer equipment constituting the system. 3. apparatus. An operation management method in an operation management device including an identification information management unit, a combination management unit, and a program execution unit,
The identification information management unit associates the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system with the respective logical inclusions associated with the respective configuration information indicating the respective components. An identification information management step of managing each structured identification information expressed in a tree structure including the identification information, and specifying a management target by information of an identification information management unit that manages the uniqueness of each of the structured identification information; ,
A combination management step in which the combination management unit manages a combination of each configuration control policy program corresponding to each component and each logical inclusion identification information corresponding to each configuration information indicating each component;
When the program execution unit recognizes one of the logical inclusion identification information pieces of the logical inclusion identification information, the program execution unit indicates target range information indicating a range of a processing target and a range of execution authority of each of the configuration control policy programs. Based on the execution authority range information and the impact range information indicating the impact range when each of the configuration control policy programs is executed, a necessary configuration control policy program is specified from among the configuration control policy programs, A program execution step for executing the specified configuration control policy program,
Have a,
In the program execution step,
The program execution unit determines whether one component corresponding to the recognized one structured identification information and the identified configuration control policy program are managed within the same operation management responsibility range, An operation management method characterized by executing arbitration for execution of the specified configuration control policy program according to the determination result, and then executing the configuration control policy program . In the identification information management step,
The said identification information management part manages the range of responsibility of each said configuration control policy program using a regular expression form, and performs a configuration control, recognizing the said operation management responsibility range. The claim of Claim 9 characterized by the above-mentioned. Operation management method. In the program execution step,
The program execution unit determines whether or not there is an environment in which the specified configuration control policy program can be executed with respect to a failure occurrence site in the control equipment and the associated computer equipment, and according to the determination result, the specified configuration control policy The operation management method according to claim 9 , wherein the program is executed. An operation management method in an operation management device including an identification information management unit, a combination management unit, and a program execution unit,
The identification information management unit associates the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system with the respective logical inclusions associated with the respective configuration information indicating the respective components. An identification information management step of managing each structured identification information expressed in a tree structure including the identification information, and specifying a management target by information of an identification information management unit that manages the uniqueness of each of the structured identification information; ,
A combination management step in which the combination management unit manages a combination of each configuration control policy program corresponding to each component and each logical inclusion identification information corresponding to each configuration information indicating each component;
When the program execution unit recognizes one of the logical inclusion identification information pieces of the logical inclusion identification information, the program execution unit indicates target range information indicating a range of a processing target and a range of execution authority of each of the configuration control policy programs. Based on the execution authority range information and the impact range information indicating the impact range when each of the configuration control policy programs is executed, a necessary configuration control policy program is specified from among the configuration control policy programs, A program execution step for executing the specified configuration control policy program,
Has,
In the combination management step,
The combination management unit determines whether one component corresponding to the recognized one structured identification information and the specified configuration control policy program are managed within the same operation management responsibility range. Determining whether there is an environment in which the specified configuration control policy program can be executed with respect to a failure occurrence site in the control equipment and the associated computer equipment, and executing the specified configuration control policy program in accordance with the determination result. If not possible, operational management way to and performing a notification to the identified configuration control policy program can be executed in response to a request containing the recognized one structuring identification information. An operation management method in an operation management device including an identification information management unit, a combination management unit, and a program execution unit,
The identification information management unit associates the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system with the respective logical inclusions associated with the respective configuration information indicating the respective components. An identification information management step of managing each structured identification information expressed in a tree structure including the identification information, and specifying a management target by information of an identification information management unit that manages the uniqueness of each of the structured identification information; ,
A combination management step in which the combination management unit manages a combination of each configuration control policy program corresponding to each component and each logical inclusion identification information corresponding to each configuration information indicating each component;
When the program execution unit recognizes one of the logical inclusion identification information pieces of the logical inclusion identification information, the program execution unit indicates target range information indicating a range of a processing target and a range of execution authority of each of the configuration control policy programs. Based on the execution authority range information and the impact range information indicating the impact range when each of the configuration control policy programs is executed, a necessary configuration control policy program is specified from among the configuration control policy programs, A program execution step for executing the specified configuration control policy program,
Has,
In the identification information management step,
The identification information management unit, as the structured identification information, a fixed finite model name is given in advance one of the structured identification information and the fixed state according to the mounting state of each configuration control policy program And other structured identification information to which another name different from the name of the generic finite model can be separately assigned,
In the combination management step,
The combination management unit manages the correspondence relationship between the respective configuration control policy programs corresponding to the one structured identification information and the other structured identification information, respectively, and fixes the another name to be separately given to the configuration control policy program. The other structured identification information re-recognized as the name of the fixed finite model is reset as the one structured identification information to which the name of the fixed finite model is previously given. luck for the management how. The identification information management unit,
While maintaining the physical and logical inclusion relations, manages each of the structured identification information expressed in a tree structure in correspondence with each state information identification information indicating each state information of each of the constituent elements. The operation management method according to claim 9 , wherein In the identification information management step,
The identification information management unit includes, as the structured identification information, each physical machine structured identification information including each physical machine identification information as identification information corresponding to each physical machine as the computer equipment, Each virtual machine structure including each virtual machine identification information as identification information corresponding to a virtual machine obtained by virtualizing some physical machines, and including some physical machine structured identification information corresponding to the some physical machines Management information and
In the combination management step,
When the combination management unit performs the reallocation by moving the virtual machine between the physical machines, the virtual machine included in the virtual machine structured identification information before the reallocation is performed. While partially changing the structured identification information of the old physical machine to the structured identification information of the new physical machine after the virtual machine is relocated, the structured identification information of the old physical machine before the relocation is changed. Resetting old various management information including new structured information including the structured identification information of the new physical machine after the relocation, and re-evaluating each of the constituent elements constituting the system. The operation management method according to claim 12, which performs the operation management. A tree structure including the physical and logical inclusion relations of the respective components including the control equipment and the associated computer equipment constituting the system, including the respective logical inclusion identification information associated with the respective configuration information indicating the respective components. An identification information management unit that manages the uniqueness of each of the structured identification information while managing as each of the structured identification information represented by, each configuration control policy program corresponding to each of the configuration elements, A combination management unit that manages a combination with each of the logical inclusion identification information corresponding to each of the configuration information, and a range of a processing target when one of the logical inclusion identification information is recognized. Range information indicating the range of execution authority of each of the configuration control policy programs, and the effect when each of the configuration control policy programs is executed. A program execution unit that specifies a necessary configuration control policy program from among the configuration control policy programs based on the influence range information that indicates the enclosure, and executes the specified configuration control policy program. Equipment and
A user-side device that uses the control equipment and the accompanying computer equipment,
Have a,
The program execution unit includes:
Determine whether one component corresponding to the recognized one structured identification information and the specified configuration control policy program are managed within the same operation management responsibility range,
An operation management system , wherein after executing arbitration for execution of the specified configuration control policy program according to the determination result, the configuration control policy program is executed .

Images