JP6061777B2 - Configuration management apparatus, configuration management method, and program - Google Patents

Description

  The present invention relates to configuration management of IT (Information Technology) services.

ITIL (Information Technology Infrastructure Library) is a framework that summarizes the best practices of IT service management and has become the de facto standard for operating IT services.
In the configuration management process of ITIL, it is described that all elements constituting the IT service are objects of configuration management.
The configuration information is expressed by relationship information indicating a relationship between configuration items (CIs) and CIs.
Configuration information expressed by CI and relationship information is stored and managed in a configuration management database (CMDB: Configuration Management Database).

Accurate maintenance management of configuration information contributes to the efficiency of other processes (for example, incident management process) of ITIL that refers to configuration information, and leads to improvement of the quality of IT services.
On the other hand, if maintenance of the correct configuration information cannot be performed, the IT service is provided based on the incorrect configuration information, so the quality of the IT service is degraded.
For example, if the network configuration information managed by the CMDB is incorrect, it may take extra time to identify the fault location in the incident management process when a fault occurs.
Therefore, it is very important to correctly maintain and manage configuration information in configuration management.

As a method for performing accurate configuration management, there is a method called discovery in which configuration information is collected directly from an actual system to be managed and stored in the CMDB.
In the discovery, information is directly collected from devices constituting the management target system using ICMP (Internet Control Message Protocol), SNMP (Simple Network Management Protocol), WMI (Windows (registered trademark) Management Instrumentation), or the like.
Generally, a discovery function is attached to a CMDB product, and it is devised so that accurate configuration information can be easily maintained and managed.
However, in order to collect detailed configuration information by executing discovery, there is a restriction that a user ID and password with administrator authority of the device are required.
In an information system department that manages the configuration of its own system, this restriction may not be a problem.
However, this is a big hurdle for IT service providers who manage the configuration information of customer systems as well as their own systems.
In many cases, the administrator authority of the customer system cannot be obtained and the discovery function cannot be used.

When performing configuration management without using the discovery function, for example, the configuration information to be managed in a spreadsheet is written and arranged in the format of CI and relationship information, and this is used using API (Application Programming Interface) provided by the CMDB. To the CMDB.
Such manual management of configuration information is likely to cause registration errors and omissions of configuration information, particularly related information.

In the prior art, a method of extracting a definition omission candidate of relational information not corresponding to the constraint condition based on a constraint condition defined in advance has been proposed (for example, Patent Document 1).
In addition, a conventional technique that automatically generates a constraint condition based on configuration information that is managed is proposed (for example, Patent Document 2).

JP 2011-138406 A JP 2012-198642 A

When an IT service provider performs configuration management, if the constraint condition is uniquely determined for a plurality of services by applying the prior art as it is, the accuracy of extracting configuration information error candidates is reduced. was there.
There are two reasons.
The first reason is that IT service providers provide a number of services with different configuration characteristics.
For example, in the hosting service, a device prepared by the IT service provider is installed at the base of the IT service provider and provided to the customer.
Therefore, the configuration for providing the hosting service has a characteristic that it is a fixed configuration with a low degree of freedom.
On the other hand, in the housing service, a system is constructed by bringing a customer-prepared device to an IT service provider base.
Therefore, the structure of the housing service is characterized by a highly flexible structure that is completely different for each customer.
The second reason is that not only the configuration information of the own system that provides the IT service but also the configuration information of the customer system that uses the IT service must be managed depending on the service provision form.
For example, when an IT service provider provides a SaaS (Software as a Service) type service, the IT service provider designs all hardware, nodes, software, etc., and manages the design information as part of the configuration information. .
On the other hand, when providing an IaaS (Infrastructure as a Service) type service, IT service providers provide hardware and physical nodes (host OS), and customers who use the service can freely create virtual nodes (guest OS). Create or install software.
The IT service provider does not need to manage configuration information such as virtual nodes that are freely created by the customer.
However, for example, there are many cases where it is necessary to manage customer configuration information together with the configuration information of the company by contracts such as operation monitoring of virtual nodes.

  For the above reasons, the IT service provider needs to manage the configuration information mixed with the characteristics of different configurations and customer system information. Therefore, if the constraint conditions are uniquely determined for a plurality of services, The extraction accuracy of configuration information error candidates due to the constraint condition is lowered.

As a method in consideration of the above problems, a method of creating a constraint condition for each service is conceivable.
In this case, since the constraint conditions can be defined in consideration of the characteristics of the configuration of each service, the above problem is solved.
However, it is necessary to manually define the constraint conditions for all the services one by one while considering the characteristics of the configuration, and the definition of the constraint conditions is likely to be missed.
For example, in the case of the SaaS type service, the person in charge of the SaaS type service is always aware of the configuration information related to the software provided, so that the constraint condition can be correctly defined.
However, it is usually not so conscious about the configuration lower than the software such as the node or hardware in which the software is installed, and the definition is likely to be omitted.

  The main object of the present invention is to solve the above-mentioned problems, and it is a main object of the present invention to prevent omission of a constraint condition that is a reference value that is referred to when an IT service configuration is analyzed. .

The configuration management device according to the present invention is
The reference value that is referenced when analyzing the configuration of the IT service using the configuration management information in which the configuration of the IT service is defined according to the configuration management model that is a model of the configuration of the IT (Information Technology) service is the configuration management model. A configuration management device that performs reference value setting processing that is set in units of a set of configuration items included in
Configuration management model information that stores configuration management model information in which a corresponding configuration management model is defined by a set of a plurality of configuration items that are types of components of the IT service for each service provision mode that is an IT service provision mode A storage unit;
A corresponding service provision form is defined for each type of IT service, and among the configuration items included in the corresponding configuration management model information, a configuration item that is a target for setting a reference value is set for each service provision form. A service provision form information storage unit for storing service provision form information defined as a target configuration item;
When the reference value setting process is performed, based on the definition of the service provision form information, the corresponding service provision form is identified for each type of IT service, and the setting target configuration item of the identified service provision form is A configuration item extraction unit that extracts from the configuration management model information a configuration item that is extracted from the service provision form information and is paired with the extracted setting target configuration item;
For each type of IT service, the configuration management apparatus user is notified that the set of the configuration target configuration item and the related configuration item extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set. And a setting target group presentation unit to be presented.

  According to the present invention, a set of configuration items for setting a reference value can be presented to the user for each type of IT service, so that the user can grasp the reference value to be defined. The definition omission can be prevented.

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. FIG. 6 is a diagram showing an example of service provision form information according to the first embodiment. FIG. 6 is a diagram showing an example of service provision form information according to the first embodiment. FIG. 3 is a diagram illustrating an example of a configuration management model according to the first embodiment. FIG. 4 is a diagram illustrating an example of configuration management model information according to the first embodiment. FIG. 6 is a diagram showing an example of constraint condition information according to the first embodiment. The figure which shows the operation example at the time of the new service addition of the configuration management apparatus which concerns on Embodiment 1. FIG. FIG. 4 is a diagram illustrating an operation example when a constraint condition is input by the configuration management apparatus according to the first embodiment. The figure which shows the operation example at the time of the configuration information update of the configuration management apparatus which concerns on Embodiment 1. FIG. FIG. 6 is a flowchart showing an operation example of a constraint condition item generation unit according to the first embodiment. FIG. 6 is a flowchart showing an operation example of a constraint condition item generation unit according to the first embodiment. The figure which shows the example of the spreadsheet which fills in the structure information registered or updated to CMDB which concerns on Embodiment 1. FIG. The figure which shows the example of the spreadsheet which fills in the structure information registered or updated to CMDB which concerns on Embodiment 1. FIG. FIG. 5 is a flowchart showing an operation example of a constraint condition confirmation unit according to the first embodiment. FIG. 5 is a flowchart showing an operation example of a constraint condition confirmation unit according to the first embodiment. FIG. 5 is a flowchart showing an operation example of a constraint condition confirmation unit according to the first embodiment. The flowchart figure which shows the constraint condition production | generation procedure for every customer which concerns on Embodiment 1. FIG. FIG. 3 is a diagram illustrating a hardware configuration example of the configuration management apparatus according to the first embodiment.

Embodiment 1 FIG.
In the present embodiment, a configuration management device is described that enables defining constraint conditions for extracting configuration information error candidates without omission when managing configuration information manually.
More specifically, in the present embodiment, based on service provision form information that defines a range of configuration information to which a constraint condition is applied for each service provision form, and information on a configuration management model that is managed by CMDB. The configuration management device automatically generates constraint condition items for each IT service.

The constraint condition is a reference value that is referred to when an error candidate of configuration information is extracted by analyzing the configuration of the IT service.
The constraint condition item is a set of configuration items (CI) for setting the constraint condition.
A configuration item (CI) is a type of a component of an IT service.
For example, when a certain IT service includes “service”, “system”, “hardware”, “physical node”, “virtual node”, and “software” as configuration items, the configuration management apparatus For example, as a constraint condition item, a set of “hardware” and “physical node”, a set of “physical node” and “virtual node”, and a set of “virtual node” and “software” are extracted.

Thus, according to the present embodiment, it is possible to generate the constraint condition items to be defined for each IT service without omission.
Since the person in charge of setting the constraint condition only needs to set the value of the constraint condition in accordance with the constraint condition item generated by the configuration management apparatus, the constraint condition can be defined without omission.
In the above example, the person in charge is a set of “hardware” and “physical node” presented by the configuration management device, a set of “physical node” and “virtual node”, “virtual node” and “software”. Constraints can be defined for each of the sets.
Since the constraint condition is defined for each service, it is possible to define the constraint condition with high accuracy as compared with the constraint condition uniquely defined for all the configuration information.
By extracting configuration information error candidates and presenting the results based on the defined constraint conditions, accurate configuration information maintenance management is promoted.
In other words, it leads to improvement of the quality of IT services.

FIG. 1 shows a system configuration example according to the first embodiment.
The system according to the first embodiment includes a client device 10 and a configuration management device 20.

The client device 10 is a terminal device used by a person in charge of configuration management (configuration manager).
The person in charge of configuration management uses the configuration management apparatus 20 by using the client apparatus 10.

The configuration management apparatus 20 is a configuration management system that manages configuration information.
The configuration management apparatus 20 is a system that manages configuration information such as storing configuration information and referring to and updating stored configuration information.
Further, when the person in charge of configuration management updates configuration information to the configuration management apparatus 20, extraction of configuration information error candidates based on constraint conditions and display of the results are also performed.
The configuration management device 20 includes an information processing device 201 and an information storage device 202.

The information processing apparatus 201 performs processing such as storing configuration information in the information storage device 202, acquiring configuration information from the information storage device 202, and extracting configuration information error candidates in accordance with the input from the client device 10.
In addition, the information processing apparatus 201 displays the processing result on the client apparatus 10.
Details of the configuration of the information processing apparatus 201 will be described later.

The information storage device 202 is a device that stores configuration information input from the client device 10 and information such as constraint conditions used to extract configuration information error candidates.
The information storage device 202 includes a CMDB 2021 and a constraint condition DB 2022.

The CMDB 2021 is a configuration management database that stores configuration information.
The configuration information is expressed by relationship information representing the relationship between CIs and CIs, and management is performed.
The constraint condition DB 2022 is a database that stores constraint conditions for extracting error candidates for the configuration information input by the configuration manager.
The constraint DB 2022 includes service provision form information 20221, configuration management model information 20222, and constraint condition information 20223.
Details of these information will be described later.
The constraint condition DB 2022 corresponds to an example of a service provision form information storage unit and a configuration management model information storage unit.

Next, the configuration of the information processing apparatus 201 will be described.
The information processing apparatus 201 includes a screen display unit 2011, a configuration information acquisition unit 2012, a configuration information update unit 2013, a constraint condition item generation unit 2014, a constraint condition update unit 2015, and a constraint condition confirmation unit 2016.

The screen display unit 2011 generates a screen to be displayed on the client device 10 when the person in charge of configuration management uses the configuration management apparatus 20.
The person in charge of configuration management uses the configuration management apparatus 20 from the client apparatus 10 using the screen displayed by the screen display unit 2011.
Further, the screen display unit 2011 generates a screen for displaying the constraint condition item (a set of CIs for setting the constraint condition) generated by the constraint condition item generation unit 2014, and presents the constraint condition item to the person in charge of configuration management.
The screen display unit 2011 corresponds to an example of a setting target group presentation unit.

The configuration information acquisition unit 2012 searches and acquires configuration information from the CMDB 2021 based on the designated search key.
An API or the like that obtains configuration information from the CMDB provided by the CMDB product can also be used as this function.

The configuration information update unit 2013 updates the configuration information stored in the CMDB 2021 with the configuration information input by the configuration manager.
An API or the like that obtains configuration information from the CMDB provided by the CMDB product can also be used as this function.

The constraint condition item generation unit 2014 reads the service provision form information 20221 and the configuration management model information 20222, generates a constraint condition item for each IT service based on the service provision form information 20221 and the configuration management model information 20222, and creates a constraint condition. Saved as information 20223.
The constraint condition item generation unit 2014 corresponds to an example of a configuration item extraction unit.

  The constraint condition update unit 2015 stores, in the constraint condition information 20223, the constraint condition value input by the configuration management person through the client device 10 for the constraint condition item generated by the constraint condition item generation unit 2014.

Based on the constraint condition information 20223 created by the constraint condition item generation unit 2014 and the constraint condition update unit 2015, the constraint condition confirmation unit 2016 extracts error candidates for the configuration information updated by the person in charge of configuration management.
The constraint condition confirmation unit 2016 corresponds to an example of a configuration analysis unit.

  Next, details of the service provision form information 20221, the configuration management model information 20222, and the constraint condition information 20223 will be described.

The service provision form information 20221 has a data structure shown in FIGS.
The configuration management model information 20222 has the data structure shown in FIGS.
The constraint condition information 20223 has a data structure shown in FIG.
In FIG. 2 to FIG. 6, “(A) Description of item” describes the item name of each data and the content of each item, and “(A) Example of data” indicates an example of actual data content. Show.

As shown in FIGS. 2 and 3, the service provision form information 20221 is information on the service name of the IT service provided by the IT service provider and the form of provision.
The service provision form information is composed of two types of information: “(1) Correspondence between service name and service provision form” (FIG. 2) and “(2) Restriction condition application range for each service provision form” (FIG. 3). The

“(1) Correspondence between service name and service provision form” shown in FIG. 2 is information indicating the correspondence between the name of the IT service provided by the IT service provider to the customer and the provision form of the IT service.
Item names are shown in (a).
The item is composed of a service name and a service provision form.
The service name is the name of the IT service provided by the IT service provider, and the service provision form is the name of the provision form of the IT service provided by the IT service provider.
An example of data is shown in (a).
When the mail service (cloud type) is a service that provides software to a customer as a service, a SaaS type service is defined as a service provision form in the mail service (cloud type).
Further, when the hosting service is a service that provides a server to a customer, an IaaS type service is defined as a service providing form in the hosting service.
In the data example, one of SaaS type service, PaaS (Platform as a Service) type service, IaaS type service, and housing service is defined as a service provision form, but other provision forms may be defined. .
For example, a name indicating a service provision form such as “IaaS type service + operation monitoring service” may be freely given.
In the present embodiment, since the service provision form is used as a pattern name of the provision form to the last, it can be defined with a unique name that matches the service provision form.

“(2) Restriction condition application range for each service provision form” illustrated in FIG. 3 is information that defines, for each service provision form, a range in which error candidates are extracted based on the restriction condition when the configuration information is updated.
Even if the IT service provider manages the configuration information that the customer has freely determined the configuration, it will be excluded from the extraction range due to the constraints, and only the range designed by the IT service provider will be checked It is a definition to make it possible.
When it is desired to perform error extraction based on the constraint condition for the customer range, the range may be set as such.
Item names are shown in (a).
The item is composed of a service provision form and one or more CI type names.
The service provision form is the same as the service provision form of (1) in FIG.
The CI type name is a CI type name managed by the CMDB 2021, and is, for example, a node, hardware, or the like.
Here, the CI type name as the item name is the CI type name that is the target of error candidate extraction based on the constraint condition, and therefore, one or more CI type names are equal to or less than the number of CI types that are managed.
For example, if there are 10 CI type names to be extracted as error candidates, the number of CI type name items is 10.
An example of data is shown in (a).
Here, four candidate types are extracted as candidates for CI, namely, hardware, physical node, virtual node, and software.
The constraint condition application range is represented by three patterns of “」 ”,“ ◯ ”, and“ × ”.
“◎” is a CI designed by an IT service provider, and the relationship information (number of relationship information) to other CIs is also uniquely determined.
“O” is a CI designed by the IT service provider, and the relationship information to other CIs is not uniquely determined, but the CI of the relationship information is determined.
“X” is a CI designed by a customer who uses the service, and is a CI for which no tendency to information related to other CIs has been determined.
CIs in which “◎” and “◯” are described are CIs that are targets of constraint condition items, and correspond to examples of setting target configuration items.

For example, in the SaaS type service, when the relation information of the software to be provided is uniquely determined, but the virtual node, the physical node, and the hardware are designed but not uniquely determined, the data example of (a) As shown, the hardware is “O”, the physical node is “O”, the virtual node is “O”, and the software is “◎”.
In the PaaS type service, hardware and physical nodes are uniquely determined, but virtual nodes are not uniquely determined. For software, if the customer who uses the service designed it uniquely, Is “◎”, the physical node is “◎”, the virtual node is “◯”, and the software is “×”.
In the IaaS type service, the hardware is uniquely determined, but the physical node is not uniquely determined. For the virtual node and software, if the customer who uses the service originally designed the hardware, Is “◎”, the physical node is “◯”, the virtual node is “×”, and the software is “×”.
Note that these are merely examples, and do not mean that all SaaS type services, PaaS type services, and IaaS type services fall within such an application range.
“◎”, “◯”, and “×” are not limited to these three types, and other writing methods may be used as long as the information can be determined.
There may be more than two patterns.

FIG. 4 is an example of a configuration management model of configuration information managed by the CMDB 2021.
The ellipse represents the CI type name, the arrow represents the relationship information, the source of the arrow is the source CI, and the destination of the arrow is the target CI.
The relationship between the source CI and the target CI is 1 to N (0 or more).

An example of FIG. 4 will be described.
As shown in FIG. 4 (1), there are a plurality of systems constituting the service under the service provided by the IT service provider.
From (2) of FIG. 4, there are a plurality of physical nodes and virtual nodes under the system.
From (3) of FIG. 4, a plurality of virtual nodes exist on the physical node.
From (4) of FIG. 4, a plurality of software exists on the virtual node.
From (5) of FIG. 4, there are a plurality of physical nodes on the hardware.
In the description of the configuration management model information 20222, FIG. 4 is used as an example of the configuration management model.

FIG. 5 is an example of the configuration management model information 20222.
Item names are shown in (a).
An item is composed of a source CI and a target CI.
An example of data is shown in (a).
The data example represents the configuration management model shown in FIG. 4 in a tabular format.
(1) in FIG. 4 corresponds to the service (source CI) -system (target CI) in FIG.
Similarly, (2) in FIG. 4 is a system-physical node, system-virtual node, (3) in FIG. 4 is physical node-virtual node, (4) in FIG. 4 is virtual node-software, and (5) in FIG. ) Corresponds to a hardware-physical node.

FIG. 6 is an example of the constraint condition information 20223.
The constraint condition is a constraint condition used for extracting an error candidate of configuration information that the configuration management person is trying to update.
Item names are shown in (a).
The items are service name, source CI, target CI, minimum value of relationship, maximum value of relationship, and specified value of relationship.
The service name, source CI, and target CI are as described above.
The minimum value of the relationship is the minimum number of target CIs related to one source CI, the maximum value of the relationship is the maximum number of target CIs related to one source CI, and the specified value of the relationship is one source A uniquely determined number of target CIs related to the CI.
An example of data is shown in (a).
For example, in the mail service (cloud type), it is assumed that there are three, three, five, and eight physical nodes created.
In this case, the minimum value of the relationship between the physical node (source CI) and the virtual node (target CI) is 3, the maximum value of the relationship is 8, and the number of relationships is not uniquely determined, so “−”.
Actually, the service name, source CI, and target CI are generated as the constraint condition items by the constraint condition item generation unit 2014. The minimum value of the relationship, the maximum value of the relationship, and the specified value of the relationship are the configuration values. Not generated for input from the administrator.

  Next, the overall operation of the configuration management apparatus 20 will be described.

In configuration management using the configuration management apparatus 20, it is necessary to define constraint condition information 20223 in the constraint condition DB 2022 in advance before registering or updating configuration information.
As a procedure for using the configuration management apparatus 20, first, when the IT service provider starts providing a new service, the service name and service provision form ((1) Service name and service provision form in service provision form information 20221) ) Is input to the configuration management apparatus 20.
When there is no service provision form information corresponding to the new service, the service provision form information and its restriction condition application range ((2) Restriction condition application range for each service provision form of service provision form information 20221) are also defined. To do.
When the configuration management apparatus 20 is used for the first time, it is necessary to define the configuration management model information 20222, but once defined, there is no need to update unless the configuration management model of the CMDB 2021 is changed.
Based on these pieces of information, the configuration management device 20 generates constraint condition items.
The person in charge of configuration management sets the value of the constraint condition for the constraint condition item (constraint condition information 20223).
The advance preparation is now complete.
Based on the predefined constraint information 20223, configuration information error candidates are extracted when the configuration information is updated.

  FIG. 7 shows that when the IT service provider starts providing a new service, the person in charge of configuration management inputs information on the service name and the service provision form to the configuration management apparatus 20, and the service provision form information 20221 and the configuration management model information FIG. 8 is a diagram showing a function related to processing for generating a constraint condition item based on 20222 (thick line portion in FIG. 7).

The screen display unit 2011 first displays a screen for adding new service information to the service provision form information 20221.
For example, a screen that allows the input of a service name to be added, selection of a service provision form, and the like is displayed.
The input service name and service provision form are temporarily stored in the service provision form information 20221 through the constraint condition item generation unit 2014.
In the constraint condition item generation unit 2014, a constraint condition item is generated based on the service provision form information 20221 and the configuration management model information 20222 that have just been added, and is stored as the constraint condition information 20223.
The operation of the constraint condition item generation unit 2014 will be described later in detail using a flowchart, and is omitted here.
As a result of the processing, the screen display unit 2011 displays the generated constraint condition items.
The person in charge of configuration management can check the generated constraint condition items through the client device 10.

FIG. 8 is a diagram showing functions related to the restriction condition items generated in FIG. 7 when the person in charge of configuration inputs the value of the restriction condition (the bold line portion in FIG. 8).
The person in charge of configuration management defines the value of the constraint condition for the generated constraint condition item based on the design document or the like.
The screen display unit 2011 displays a screen for inputting the value of the constraint condition, and the person in charge of configuration management inputs the value of the constraint condition from the client device 10.
The input value is registered in the constraint condition information 20223 by the constraint condition update unit 2015.
The screen display unit 2011 displays the updated constraint condition information 20223 as a result of the processing.
The person in charge of configuration management can confirm through the client device 10 that the value for the constraint condition item has been set.

FIG. 9 is a diagram showing functions related to newly registering or updating configuration information after the definition of the constraint condition is completed according to FIGS. 7 and 8 (the bold line portion in FIG. 9).
When newly registering configuration information or updating configuration information managed by the CMDB 2021, the configuration manager in charge prepares configuration information to be registered or updated in a form such as a spreadsheet.
The prepared configuration information is input from the client device 10 to the configuration management device 20 through a screen for updating the configuration information provided by the screen display unit 2011.
The input configuration information is stored in the CMDB 2021 by the configuration information update unit 2013.
The constraint condition confirmation unit 2016 acquires the constraint condition information 20223 and extracts error candidates for the configuration information input to the configuration management apparatus 20.
In the constraint condition confirmation unit 2016, the relationship between the CIs of the input configuration information based on the minimum value and the maximum value of the relationship between the source CI and the target CI set in the constraint condition information 20223 or the specified value. To check whether the constraint condition is satisfied.
If not, it is extracted as an error candidate.
The operation of the constraint condition confirmation unit 2016 will be described in detail later using a flowchart.
The extracted result is displayed by the screen display unit 2011.
The person in charge of configuration management can confirm error candidates by using the screen display unit 2011.
Further, the configuration information registered in the CMDB 2021 can also be confirmed.
In the update to the CMDB 2021 by the configuration information update unit 2013, the CMDB 2021 may be updated only when there is no error candidate, or the CMDB 2021 may be updated even if there is an error candidate.

Next, the operation of the constraint condition item generation unit 2014 will be described.
FIG. 10 is a flowchart of the constraint condition item generation unit 2014.
The operation of the constraint condition item generation unit 2014 will be described in detail with reference to FIG.
In addition, an example of generating constraint condition items for the mail service (cloud type) will be described together with the description of the operation.

In S01, the constraint condition item generation unit 2014 uses the service name of the new service input from the configuration manager as a key, and (1) from the correspondence between the service name and the service provision format of the service provision format information 20221 of the constraint condition DB 2022 , To obtain the service provision form.
For example, when a mail service (cloud type) is input from the person in charge of configuration management, the service provision form of the mail service (cloud type) is a SaaS type service from the data example of (1) (a) in FIG. To get.

In S02, the restriction condition item generation unit 2014 uses the service provision form name acquired in S01 as a key, and the application range of the corresponding service provision form from (2) restriction condition application range for each service provision form in the service provision form information 20221. To get.
For example, in the case of the SaaS type service, from the data example of (2) (a) in FIG. 3, the applicable range of restriction conditions for each CI is “◯” for hardware, “O” for physical nodes, and “O” for virtual nodes. ”, The software gets“ ◎ ”.

In S03, the constraint condition item generation unit 2014 determines whether constraint condition items have been generated for all the CI type names acquired in S02.
If all the CI type names have been generated, the process proceeds to S09.
If it has not been generated, the process proceeds to S04. S03 is a loop process based on the CI type name acquired in S02.
For example, in the case of the constraint condition application range acquired in S02, it is determined whether or not the constraint condition item has been generated for each of the CI type name, that is, hardware, physical node, virtual node, and software. In each case, the process proceeds to S04.

In S04, the constraint condition item generation unit 2014 determines whether the value of the constraint condition application range of the CI type name is “◯” or “◎”.
In the case of “◯” or “◎”, the process proceeds to S05.
Otherwise ("x"), the process returns to S03.
For example, in the case of a SaaS type service, first, the hardware having the first CI type name is confirmed.
Since the hardware of the SaaS type service is “◯”, the process proceeds to S05.
As another example, in the case of a housing type service, since the hardware is “x”, it is not necessary to create a constraint condition.
Therefore, the process returns to S03, and the process proceeds to confirmation for the physical node that is the next CI type name.
Note that the CI whose constraint condition application range value is “◯” or “◎” in S03 corresponds to an example of a setting target configuration item.
In S03, a CI with a constraint condition application range value of “×” corresponds to an example of a configuration item that is not a setting target.

In S <b> 05, the constraint condition item generation unit 2014 obtains the relationship information whose source is the CI type name of the constraint condition application range from the configuration management model information 20222.
In the case of hardware of SaaS type service, the relationship information that the source CI is hardware and the target CI is a physical node is acquired from (a) data example of the configuration management model definition example of FIG.
Depending on the configuration management model, a plurality of relation information may be acquired.

In S06, the constraint condition item generation unit 2014 determines whether a constraint condition item has been generated for each target CI of the relationship information acquired in S05.
If it has not been generated, the process proceeds to S07 each time.
If it has been generated for all target CIs, the process returns to S03.
S06 is a loop process by the target CI of the relationship information acquired in S05.
For example, when the source CI is hardware and the target CI is a physical node, it is determined whether or not a constraint condition item has been generated for the physical node that is the target CI.
If it has not been generated, the process proceeds to S07.

In S07, the constraint condition item generating unit 2014 determines whether the value of the constraint condition application range of the target CI is “◯” or “◎”.
In the case of “◯” or “◎”, the process proceeds to S08.
In other cases ("x"), the process returns to S06, and the process moves to the next target CI.
In the case of the SaaS type service, since the physical node is “◯”, the process proceeds to S08.
Note that the CI whose constraint condition application range value is “◯” or “◎” in S07 corresponds to an example of a related configuration item.

In S08, the constraint condition item generation unit 2014 generates a constraint condition item from the relationship information and the value of the constraint condition adaptation range.
Details will be described later with reference to FIG. After the constraint condition item is generated, the process returns to S06.

In S 09, the constraint condition item generation unit 2014 stores all the generated constraint condition items as the constraint condition information 20223 in the constraint condition DB 2022.
In the case of a mail service (cloud type), the three rows from the top shown in the data example (a) of FIG. 6 are stored in the constraint DB as constraint items.
At this point, the minimum / maximum value and the specified value of the relationship are blank. In FIG. 6, numerals are shown to show examples of values.

  FIG. 11 is a flowchart for generating the constraint condition item from the relationship information in S08 and the value of the application range of the constraint condition.

In S10, the constraint condition item generation unit 2014 determines whether the values of the constraint condition application ranges of the source CI and the target CI of the relationship information are both “◎”.
If both are “◎”, the process proceeds to S11.
Other than that (the source CI is “」 ”and the target CI is“ ◯ ”, or the source CI is“ ○ ”and the target CI is“ ◎ ”, or the source CI is“ ○ ”and the target CI is“ ○ ”) If yes, go to S12.
For example, since the source CI is “◯” and the target CI is “◯”, the hardware and physical node, which are the relationship information of the SaaS type service, proceed to S12.
As another example, since both the hardware and the physical node, which are the relationship information of the PaaS type service, are “」 ”, the process proceeds to S11.

In S11, the constraint condition item generation unit 2014 uses the source CI and the target CI of the relationship information as constraint condition items, and inputs “−” as the minimum value and the maximum value of the relationship.
This is because the design specifications of the source CI and the target CI are both determined in a single way, and the value of the constraint condition can be set with a specified value.
For example, in the relationship between the hardware and the physical node of the application platform service that is a PaaS type service, the source CI is the hardware and the target CI is the physical node as shown in the fifth line of the data example in FIG. The minimum value and the maximum value of the relationship are “−”.
In the example of FIG. 6, a value is included in the specified value of the relationship, but is blank when the constraint condition item is generated.

In S12, the constraint condition item generation unit 2014 uses the relationship information source and target CIs as constraint condition items, inputs "-" as the specified value, and allows the minimum and maximum values of the relationship information to be set. .
For example, in the relationship between the hardware of the SaaS type service mail service (cloud type) and the physical node, the source CI is the hardware and the target CI is the physical node as shown in the first line of the data example in FIG. The specified value of the relationship is “−”.
In the example of FIG. 6, the minimum value and the maximum value of the relationship contain values, but are blank when the constraint condition item is generated.

Before describing the operation of the constraint condition confirmation unit 2016, an example of the format of configuration information registered or updated in the CMDB 2021 from the configuration management person in charge through the client device 10 will be described with reference to FIGS.
12 and 13 show the configuration information registration / update format corresponding to the example of the configuration management model shown in FIG.
One sheet corresponds to one CI and related information, and is an example of a registration / update format of configuration information composed of a plurality of sheets.
The registration / update format is not limited to this example.

An example sheet is shown in FIG.
As described above, it is an example of a configuration information registration / update format corresponding to the example of the configuration management model shown in FIG.
FIG. 4 shows a management model composed of 6 pieces of CI and 6 pieces of relational information, and therefore, here is an example comprising 12 sheets in total (6 pieces of CI + 6 pieces of relational information).
Since the sheet name, the number of sheets, and the type differ depending on the configuration management model, it is not necessary to be as described above.
An example of data is shown in FIG.
Here, an example of services, hardware, and physical nodes that are CIs and hardware / physical nodes that are related information is shown.
The CI information is composed of a primary key and attributes.
The example of the service sheet shows an example in which the service name is the primary key and the management unit signature is used as an attribute.
The attribute is an item to be managed in each CI and varies depending on the purpose of configuration management. Therefore, the attribute does not have to be as in this example, and any attribute other than the management unit signature may be managed.
Regarding the relationship information, the primary key information of the source CI and the primary key information of the target CI are managed.
For example, in the (a) data example of FIG. 13, the service sheet is an example in which the management unit signature of the mail service (cloud type) is the A department.
The hardware sheet is an example in which the manufacturer of the A product is company A, the model number is aaa01, the serial number is 12345678, and the firmware version is firmware 05.
The physical node sheet is an example describing that the OS name of node01 is XXX, the OS version is 3.5.7, the CPU model is CPU1, and the built-in disk capacity is 500 GB.
The hardware / physical node sheet is an example in which the A product is used as hardware of the node 01 and node 02, and the B product is used as the node 03 hardware.

Next, the operation of the constraint condition confirmation unit 2016 will be described.
FIG. 14 is a flowchart of the constraint condition confirmation unit 2016.
The operation of the constraint condition confirmation unit 2016 will be described in detail with reference to FIG.

In S <b> 21, the constraint condition confirmation unit 2016 reads the service name from the configuration information described in a format such as a spreadsheet input from the client device 10.
For example, in the example shown in FIGS. 12 and 13, “email service (cloud type)” and “application platform service” are read from the service name that is the primary key of the service sheet.

In S22, the constraint condition confirmation unit 2016 determines whether extraction of error candidates has been completed for all read service names.
If completed, the process proceeds to S27.
If not completed, the process proceeds to S23.
S22 is a loop process based on the service name acquired in S21.

In S23, the constraint condition confirmation unit 2016 acquires the constraint condition of the corresponding service from the constraint condition DB using the service name as a key.
For example, when the service name is “mail service (cloud type)”, the service name is three conditions of “mail service (cloud type)” from the data example of (a) in the constraint condition example of FIG. The minimum value of the hardware-physical node, physical node-virtual node, virtual node-software relationship, the maximum value of the relationship, and the specified value of the relationship are acquired.

In S <b> 24, the constraint condition confirmation unit 2016 determines whether the configuration information input from the client device is newly registered or updated.
The update here includes not only the change of the configuration information stored in the CMDB 2021, but also the addition and deletion of nodes and the like to the service and system stored in the CMDB 2021.
The determination of registration and update may be determined by adding flag information for determining new registration and update in the spreadsheet, or by performing a search on the CMDB 2021 and confirming by any method, for example. Good.
In the case of new registration, the process proceeds to S25. In the case of updating, the process proceeds to S26.
In S25, the constraint condition checking unit 2016 extracts error candidates based on the constraint conditions for the newly registered configuration information.
After the processing is completed, the process returns to S22.
Details of the processing of S25 will be described with reference to FIG.

In S26, the constraint condition checking unit 2016 extracts error candidates based on the constraint conditions for the configuration information to be updated.
After the processing is completed, the process returns to S22.
Details of the processing of S26 will be described with reference to FIG.
In S27, the extracted error candidate is transferred to the screen display unit 2011.
The error candidates passed to the screen display unit 2011 are displayed on the screen display unit 2011 toward the person in charge of configuration management.

  FIG. 15 is a flowchart for extracting error candidates at the time of new registration.

In S28, the constraint condition confirmation unit 2016 determines whether extraction of error candidates using all the acquired constraint conditions has been completed.
If completed, the process ends.
If not completed, the process proceeds to S29.
S28 is a loop process based on the constraints acquired in S23.
When the service name is “mail service (cloud type)”, the loop processing is repeated in the order of hardware-physical node, physical node-virtual node, virtual node-software, which are the acquired constraint conditions.

In S <b> 29, the constraint condition confirmation unit 2016 acquires a list of primary key values of the spreadsheet corresponding to the constraint condition source CI.
For example, when the constraint condition is hardware-physical node, since the source CI is hardware, the hardware product name as the primary key is acquired from the hardware sheet.
In the case of the data example in FIG. 13A, information “A product” and “B product” is acquired.

In S <b> 30, the constraint condition confirmation unit 2016 determines whether error candidate extraction for the acquired primary key value is completed.
If completed, the process returns to S28.
If not completed, the process proceeds to S31.
S30 is a loop process using the primary key acquired in S29.
For example, error candidates are sequentially extracted from “A product” and “B product”.

In S31, the constraint condition confirmation unit 2016 acquires relationship information in which the value of the spreadsheet source of the relationship information corresponding to the constraint condition matches the value of the primary key acquired in S29.
For example, when the constraint condition to be confirmed is hardware-physical node and the value is “A product”, the relationship where the primary key is “A product” from the hardware / physical node sheet which is the corresponding relationship information Get information.
In the case of the data example in FIG. 13A, two pieces of relational information are acquired in which the primary key of the hardware that is the source is “A product” and the target physical nodes are “node01” and “node02”.

In S32, the constraint condition confirmation unit 2016 counts the number of relation information acquired in S31.
For example, in S31, when two pieces of relationship information are acquired in which the primary key of the hardware that is the source is “A product” and the target physical nodes are “node01” and “node02”, the number is two. .

In S33, the constraint condition confirmation unit 2016 determines whether or not the counted number of relation information satisfies the constraint condition.
If satisfied, the process returns to S30.
When not satisfy | filling, it progresses to S34.
For example, in the case of the hardware-physical node relationship of the mail service (cloud type) in the example of (a) data in FIG. 6, since the specified value of the relationship is 1, there is a restriction if the number counted in S32 is not 1 It is determined that the condition is not satisfied, and the process proceeds to S34.

In S34, the constraint condition confirmation unit 2016 stores, as an error candidate, configuration information that does not satisfy S33 as temporary data.
For example, “product A-node01” and “product A-node02” are stored as error candidates as hardware-physical node relationship information.
This information becomes the processing result of S25, and finally passed to the screen display unit 2011 at S27 for display.

FIG. 16 is a flowchart for extracting error candidates at the time of updating.
The flow of processing is the same as that at the time of new registration described with reference to FIG. 15, but in the case of update, not only the configuration information input from the client device 10 but also error candidates including the configuration information already stored in the CMDB 2021. The point that must be extracted.

  In S35, the constraint condition confirmation unit 2016 determines whether extraction of error candidates using all the acquired constraint conditions has been completed (similar to S28).

In S36, the constraint condition confirmation unit 2016 determines whether there is an update of the relationship information corresponding to the constraint condition.
If there is an update, the process proceeds to S37.
If there is no update, the process returns to S35.
For example, when the constraint condition to be confirmed is a hardware-physical node, it is confirmed whether information to be updated is entered in the hardware / physical node sheet of the input configuration information.
This is based on the premise that only the configuration information to be updated is entered in the spreadsheet, but a spreadsheet including the configuration information that is stored in the CMDB 2021 and is not updated this time is prepared, and only the information to be updated is flagged. You may judge by.

In step S <b> 37, the constraint condition confirmation unit 2016 acquires a list obtained by removing duplication from the value of the source primary key from the relationship information sheet corresponding to the constraint condition to be confirmed.
For example, when the constraint condition to be confirmed is a hardware-physical node, the primary key of the hardware that is the source is acquired from the hardware / physical node sheet of the input configuration information.
In the case of the data example (a) in FIG. 13, “A product”, “A product”, and “B product” are removed, and “A product” and “B product” are acquired by removing duplicates.

In S <b> 38, the constraint condition confirmation unit 2016 determines whether error candidate extraction for the source value acquired in S <b> 37 has been completed.
If completed, the process returns to S35.
If not completed, the process proceeds to S39.
S38 is a loop process based on the acquired source value (for example, “A product”, “B product”).

In S39, the constraint condition confirmation unit 2016 acquires the relationship information in which the source value of the relationship information sheet corresponding to the constraint condition matches the source value acquired earlier.
For example, in the case of trying to extract error candidates for the A product, from the data example (b) in FIG. 13, two pieces of relationship information with the source “A product” and the targets “node01” and “node02” are obtained. get.

In S <b> 40, the constraint condition confirmation unit 2016 acquires relationship information that matches the source value acquired from the relationship information stored in the CMDB 2021.
Information is acquired from the hardware / physical node table in the CMDB.

In S41, the constraint condition confirmation unit 2016 sums up the number of relations acquired in S29 and the number of relations acquired in S30.
For example, if the number of relationships acquired from the CMDB is 1, the total number of relationships is 3.
If one of the update information is a request to delete the related information stored in the CMDB, it is canceled out and the total is 1.

In S42, the constraint condition confirmation unit 2016 determines whether the counted number of relation information satisfies the constraint condition (same as S33).
If satisfied, the process returns to S38. When not satisfy | filling, it progresses to S43.

  In S43, the constraint condition confirmation unit 2016 stores the configuration information as temporary data as the error candidate (same as S34).

Since the customer determines all the configurations as in the housing type service, there are cases where the error candidate check for the configuration information cannot be performed in the flowchart of the constraint condition item generation unit shown in FIG.
In that case, it is also possible to generate a constraint condition from actual configuration information for each customer and perform error candidate check.

FIG. 17 shows a case where, in a certain service, one or both of the source CI type name of the constraint condition to be generated and the constraint condition application range value of the target CI type name are found to be “x”. It is a flowchart which produces | generates the constraint conditions for every customer from a structure information.
For example, in the housing type service of (a) data example of the constraint condition application range for each service provision form in FIG. 3, the hardware, physical node, virtual node, and software are all customer-specific configurations.
In this case, in any of the hardware-physical node, physical node-virtual node, and virtual node-software relationships, the value of the constraint condition application range of the source CI type name and the target CI type name is “x”.

FIG. 17 shows that one of the source CI type name of the constraint condition to be generated and the value of the constraint condition application range of the target CI type name or both of them are found to be “x” in a certain service. Since the flowchart is based on the premise, the determination as to whether or not the value is “x” is not included in FIG.
Actually, the processing may be performed as one flowchart combining FIG. 10 and FIG.
The customer management is not included in the configuration management in the configuration management model example in FIGS. 4 and 5 and the constraint condition example in FIG. 6. However, when generating constraint conditions for each customer, it is necessary to add the item. is there.
In the configuration management model of FIGS. 4 and 5, for example, a customer is placed above the service, and the relationship information of service-customer is defined.
In the example of the constraint condition of FIG. 6, a customer name column is added so that the constraint condition for each service name and customer name can be managed.

  In S50, the constraint condition confirmation unit 2016 determines whether all constraint condition generation for each customer has been completed. If completed, the process proceeds to S57. If not completed, the process proceeds to S51.

In S51, the constraint condition confirmation unit 2016 acquires a list of primary key values of the configuration information sheet corresponding to the source CI.
For example, when a constraint condition for each customer for the hardware-physical node is generated, a primary key list is acquired from the hardware configuration information sheet as the source CI.
In the case of FIG.12 and FIG.13, "A product" and "B product" are acquired from a hardware sheet as a list.

In S <b> 52, the constraint condition confirmation unit 2016 determines whether the count of the number of pieces of related information for the acquired primary key value has been completed.
If completed, the process proceeds to S55.
If not completed, the process proceeds to S53.
S52 is a loop process based on the list value acquired in S51. When the count of “A product” is completed, it is repeated as “B product”.

In S <b> 53, the constraint condition confirmation unit 2016 acquires the relationship information in which the value of the source CI of the relationship information sheet corresponding to the source CI type name and the target CI type name matches the acquired primary key.
For example, in the case of a hardware-physical node, the relationship information is acquired from the hardware / physical node sheet.
In the case of FIG. 13, two pieces of relational information are acquired in which the source is “A product” and the targets are “node01” and “node02”.

In S54, the constraint condition confirmation unit 2016 counts the number of acquired relationship information.
In the case of the example shown in S53, the number of related information is two.
After the process of S54, the process returns to S52.

In S55, the constraint condition confirmation unit 2016 obtains the minimum value and the maximum value from the counted number of relation information.
For example, when the number of pieces of related information with the source CI “A product” is 2, and the number of pieces of related information with the source CI “B product” is 1, the minimum value is 1 and the maximum value is 2.

In S56, the constraint condition checking unit 2016 generates a constraint condition in which the obtained minimum value and maximum value are set.
For example, the service name is “housing type service”, the customer name is “Company A”, the source CI is “hardware”, the target CI is “physical node”, the minimum value of the relationship is “1”, and the maximum value of the relationship is “ 2 ”and the specified value of the relationship is“ − ”.
In S57, the generated constraint condition is stored in the constraint condition DB.

Also for the constraint conditions for each customer, the constraint condition confirmation unit 2016 extracts error candidates in the same procedure as in FIGS.
If the extracted error candidate is correct, the minimum value and the maximum value of the constraint conditions generated in the flowchart of FIG. 17 may be updated.

  Through the above processing, the constraint condition items for each service are generated based on the service provision form information and the configuration management model information.

According to the present embodiment, it is possible to generate the constraint condition items to be defined for each service without omission.
Since the person in charge who sets the constraint condition only needs to set the value of the constraint condition in accordance with the constraint condition item generated according to the present embodiment, the constraint condition can be defined without omission.
Since the constraint condition is defined for each service, it is possible to define the constraint condition with high accuracy as compared with the unique constraint condition defined for all pieces of configuration information.

  As described above, according to the present embodiment, it is possible to set constraint conditions considering the service provision mode for configuration information registered or updated in the CMDB, and check configuration information error candidates based on the constraint conditions. A configuration management device capable of doing so has been described.

  Also, it has a constraint condition item generation unit for creating a constraint condition item from configuration information to be registered or updated in the CMDB input from the user, service provision form information stored in the constraint condition DB, and a configuration management model of the CMDB. A configuration management device has been described.

  Also, a configuration management device having a constraint condition checking unit that checks error candidates for configuration information input from the user based on the value of the constraint condition set for the constraint condition item created by the constraint condition item generating unit Explained.

  In addition, configuration management with a constraint item generation unit that can automatically generate constraint conditions for each customer when the customer who uses the service makes their own design within the constraint condition application range for each service provision mode The apparatus has been described.

  Further, the configuration management apparatus having the constraint condition confirmation unit that checks error candidates for the configuration information input from the user based on the constraint conditions for each customer automatically created by the constraint condition item generation unit has been described.

Finally, a hardware configuration example of the configuration management apparatus 20 shown in the present embodiment will be described with reference to FIG.
The configuration management apparatus 20 is a computer, and each element of the configuration management apparatus 20 can be realized by a program.
As a hardware configuration of the configuration management device 20, an arithmetic device 901, an external storage device 902, a main storage device 903, a communication device 904, and an input / output device 905 are connected to the bus.

The arithmetic device 901 is a CPU (Central Processing Unit) that executes a program.
The external storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or a hard disk device.
The main storage device 903 is a RAM (Random Access Memory).
The CMDB 2021 and the constraint condition DB 2022 illustrated in FIG. 1 are realized by, for example, the external storage device 902 or the main storage device 903.
The communication device 904 is, for example, a NIC (Network Interface Card).
The input / output device 905 is, for example, a mouse, a keyboard, a display device, or the like.

The program is normally stored in the external storage device 902, and is loaded into the main storage device 903 and sequentially read into the arithmetic device 901 and executed.
The program is a program that realizes a function described as “unit” shown in FIG.
Further, an operating system (OS) is also stored in the external storage device 902. At least a part of the OS is loaded into the main storage device 903. ”Is executed.
In addition, in the description of this embodiment, “determination of”, “determination of”, “extraction of”, “acquisition of”, “setting of”, “specification of”, “reference of” ”,“ Analysis of ”,“ total of ”,“ selection of ”,“ generation of ”,“ input of ”,“ output of ”, etc. Data, signal values, and variable values are stored in the main storage device 903 as files.
Further, the encryption key / decryption key, random number value, and parameter may be stored in the main storage device 903 as a file.

18 is merely an example of the hardware configuration of the configuration management apparatus 20, and the hardware configuration of the configuration management apparatus 20 is not limited to the configuration illustrated in FIG. Also good.
Further, the configuration management method according to the present invention can be realized by the procedure shown in the present embodiment.

  DESCRIPTION OF SYMBOLS 10 Client apparatus, 20 Configuration management apparatus, 201 Information processing apparatus, 202 Information storage apparatus, 2011 Screen display part, 2012 Configuration information acquisition part, 2013 Configuration information update part, 2014 Restriction condition item generation part, 2015 Restriction condition update part, 2016 Restriction condition confirmation unit, 2021 CMDB, 2022 Restriction condition DB, 20221 Service provision form information, 20222 Configuration management model information, 20223 Restriction condition information.

Claims (9)

The reference value that is referenced when analyzing the configuration of the IT service using the configuration management information in which the configuration of the IT service is defined according to the configuration management model that is a model of the configuration of the IT (Information Technology) service is the configuration management model. A configuration management device that performs reference value setting processing that is set in units of a set of configuration items included in
Configuration management model information that stores configuration management model information in which a corresponding configuration management model is defined by a set of a plurality of configuration items that are types of components of the IT service for each service provision mode that is an IT service provision mode A storage unit;
A corresponding service provision form is defined for each type of IT service, and among the configuration items included in the corresponding configuration management model information, a configuration item that is a target for setting a reference value is set for each service provision form. A service provision form information storage unit for storing service provision form information defined as a target configuration item;
When the reference value setting process is performed, based on the definition of the service provision form information, the corresponding service provision form is identified for each type of IT service, and the setting target configuration item of the identified service provision form is A configuration item extraction unit that extracts from the configuration management model information a configuration item that is extracted from the service provision form information and is paired with the extracted setting target configuration item;
For each type of IT service, the configuration management apparatus user is notified that the set of the configuration target configuration item and the related configuration item extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set. A configuration management apparatus comprising a setting target group presentation unit for presentation. The service provision form information storage unit
For each service provision form, store service provision form information in which a plurality of setting target configuration items are defined,
The configuration item extraction unit
Determining whether the extracted related configuration item corresponds to any of the setting target configuration items other than the extracted setting target configuration item defined in the service provision form information;
The setting target group presentation unit
When the configuration item extraction unit determines that the related configuration item corresponds to one of the other configuration target configuration items,
The configuration management device presenting a user of the configuration management device that a set of a configuration target configuration item and a related configuration item extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set. The configuration management apparatus according to claim 1. The service provision form information storage unit
For each configuration target configuration item, store service provision form information in which it is defined whether the number of reference values is one or more,
The configuration item extraction unit
When it is determined that the extracted related configuration item corresponds to one of the setting target configuration items other than the extracted setting target configuration item defined in the service provision form information,
Based on the service provision form information, it is determined whether the number of reference values of the extracted configuration target configuration item is one or plural, and whether the number of reference values of the extracted related configuration item is one or plural To determine whether
The setting target group presentation unit
When the configuration item extraction unit determines that the number of reference values of the configuration target configuration item and the number of reference values of the related configuration item are both one,
A set of a configuration target configuration item and a related configuration item extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set, and one reference is made to the set of the configuration target configuration item and the related configuration item Presenting the value to be set to the user of the configuration management device;
When the configuration item extraction unit determines that at least one of the number of reference values of the configuration target configuration item and the number of reference values of the related configuration item is plural,
The set of the configuration target configuration item and the related configuration item extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set, and a plurality of references to the set of the configuration target configuration item and the related configuration item The configuration management apparatus according to claim 2, wherein a value is set to a user of the configuration management apparatus. The service provision form information storage unit
For each service provision form, store service provision form information in which a plurality of setting target configuration items are defined,
The configuration item extraction unit
When the reference value setting process is performed, based on the definition of the service provision form information, a corresponding service provision form is identified for each type of IT service, and a plurality of setting target configuration items of the identified service provision form Is extracted from the service provision form information, for each of the extracted plurality of setting target configuration items, a related configuration item is extracted,
The setting target group presentation unit
Use of the configuration management apparatus that, for each type of IT service, a set of a plurality of setting target configuration items and related configuration items extracted by the configuration item extraction unit is a set of configuration items for which a reference value is set. The configuration management device according to claim 1, wherein the configuration management device is presented to a user. The configuration management device further includes:
A configuration for analyzing the configuration of the IT service by using the configuration management information of the IT service to be analyzed and referring to the reference value corresponding to the type of the IT service after the reference value is set by the reference value setting process The configuration management apparatus according to claim 1, further comprising an analysis unit. The configuration item extraction unit
For each type of IT service, determine whether the configuration management model information of the corresponding service provision form includes a configuration item that is not a setting target that does not correspond to the setting target configuration item,
Regarding the types of IT services in which the configuration item not included in the configuration management model information of the corresponding service provision form is included, the configuration item paired with the configuration item not included in the configuration is related from the configuration management model information. It extracts as a configuration item, analyzes configuration management information of the IT service corresponding to the type of the IT service, and generates a reference value for a set of the configuration item not to be set and the related configuration item The configuration management device according to claim 1. The configuration management device further includes:
The configuration management information of the IT service corresponding to the type of IT service for which the reference value is generated by the configuration item extraction unit is used, and the configuration of the IT service is configured by referring to the reference value generated by the configuration item extraction unit. The configuration management apparatus according to claim 6, further comprising a configuration analysis unit that performs analysis. The reference value that is referenced when analyzing the configuration of the IT service using the configuration management information in which the configuration of the IT service is defined according to the configuration management model that is a model of the configuration of the IT (Information Technology) service is the configuration management model. A configuration management method by a computer in which a reference value setting process for setting in units of a set of configuration items included in a computer is performed,
For each service provision form that is an IT service provision form, the corresponding configuration management model is configured to store, from a predetermined storage area, configuration management model information that is defined by a set of a plurality of configuration items that are types of IT service constituent elements. A configuration management model information reading step read by the computer;
A corresponding service provision form is defined for each type of IT service, and among the configuration items included in the corresponding configuration management model information, a configuration item that is a target for setting a reference value is set for each service provision form. Service provision form information reading step in which the computer reads out service provision form information defined as the target configuration item from a predetermined storage area;
When the reference value setting process is performed, the computer specifies a corresponding service provision form for each type of IT service based on the definition of the service provision form information, and the setting target of the identified service provision form A configuration item extraction step for extracting a configuration item from the service provision form information and extracting a configuration item paired with the extracted setting target configuration item as a related configuration item from the configuration management model information;
The use of the computer in which, for each IT service type, the set of the configuration target configuration item and the related configuration item extracted by the configuration item extraction step is a set of configuration items for which a reference value is set. A configuration management method comprising: a setting target group presentation step presented to a person. The reference value that is referenced when analyzing the configuration of the IT service using the configuration management information in which the configuration of the IT service is defined according to the configuration management model that is a model of the configuration of the IT (Information Technology) service is the configuration management model. In the computer where the reference value setting process to set in the unit of the set of configuration items included in
For each service provision form that is an IT service provision form, the corresponding configuration management model reads configuration management model information defined by a set of a plurality of configuration items that are types of IT service constituent elements from a predetermined storage area. A configuration management model information reading step;
A corresponding service provision form is defined for each type of IT service, and among the configuration items included in the corresponding configuration management model information, a configuration item that is a target for setting a reference value is set for each service provision form. Service provision form information reading step for reading out service provision form information defined as the target configuration item from a predetermined storage area;
When the reference value setting process is performed, based on the definition of the service provision form information, the corresponding service provision form is identified for each type of IT service, and the setting target configuration item of the identified service provision form is A configuration item extraction step for extracting from the configuration management model information a configuration item that is extracted from the service provision form information and paired with the extracted setting target configuration item;
For each IT service type, the computer user is notified that the set of the configuration target configuration item and the related configuration item extracted by the configuration item extraction step is a set of configuration items for which a reference value is set. A program for executing a setting target group presentation step.

Images