Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A Configuration Management Database (CMDB) allows manage Configuration managing Configuration Items (CIs) including identifying, gathering, recording, maintaining, controling controlling, and reporting. CMDB collects and stores the following items as configuration records:

  • IT services Services and their individual components components required for a service delivery as Configuration Items
  • CI Types such as an IT Service or with other custom values determining , determining CI business logic and the set of various attributes;
  • CI Relationships between CIs with their general and specific aspects describing types and interraction mechanism as CI Relationships, specifying types of interactions, and dependencies between CIs.

CMDB records, therefore, describe your CIs with their Relationships, types of dependencies, and various characteristics.

Tip

To indentify identify your CI in your SimpleOne solution, use the CMDB features, and follow the steps below:

  1. Define Within the CI Types list, define a type of the an IT service Service component that is considered as a CI, and determine it within the CI Types list;
  2. Specify CI composing attributes with accurate and reliable information filling in the Configuration Item form;
  3. Describe and establishing relationships with other CIs by adding CI Relationships records.

The Service Model visualizes CIs and their relationships are visualized by the Service Model view which clearly demonstrates CIs current statuses and interractions on a Dependency Mapwith a Dependency Map view, which demonstrates CIs current statuses and interactions.

CI Type


Within SimpleOne, IT Services are considered as Configuration Items in the SimpleOne solution, along with constituent components required for a proper service delivery. The CI Type selection specifies a set of the CI attributes, its place, and hierarchical position on the Service Model structure.

To identify your CI either as an IT Service or as a custom CI, at first, determine your CIs diversity with the CI Types list that stores the records with type names.

Add a new CI Type

To create a new CI Type, navigate to CMDB → CI Types, and push the New button. Fill in the Name field with desired the Type name, and then push the Save or Save and Exit button. A haven created CI Type will be is added in to the end of the CI Types list. 

Since each type CI Type defines the hierarchical level of the Service Dependency Map, creating a new type will result one results in adding a new the next lower level of this model.

Configuration Item


Create, identify, configure, and manage your CIs and their parameters with the records in the list of the Configuration Items. These records keep all detailed information about CIs such as CI Type and set of attributes with their values depending on it. 

Identify To identify your CI as an IT Service or other required to manage as an IT Service component by selecting , select the CI Type value from the list and filling out fill in the form. In general, the  A set of form fields for the IT Service differs from fields on the CI form is different for an IT Service and the CIs of another type value, except for the common description fields.

Push the Connection button next to the Primary IT Service field to see the hierarchical place of your CI on the Service Dependency map.

Add a new CI

To add a New Configuration Item, navigate to the CMDB → Configuration Items menu and push the New button. Fill in the CI record form with the following fields:

Field

Description

Number

Automatically assigned to a record when having been created.

Name

A name of a Configuration Item.

CI Type

Select a type value from the list specifying your record as an IT Service or other custom CI.  

Description

Contains all necessary information details.

Service Owner

Assign a responsible person from the Users list as a Service Owner.

State

Select one of the two possible values:

  • Active;

  • Inactive.

Operational State

Determines an IT Service availability with the following possible statuses:

  • Available - a proper level of a service delivery is provided;

  • Degradated - a quality of an IT Service delivery does not correspond to the established agreements because of the ;

  • Unavailable - an IT Service is completely anavailable;

  • Maintenance - a service is not available due to the maintenance activities.

IT Service Attributes


Service Type

Desribes a type of a delivered Service.

Select one of the following values in a drop-down list to fill in the field:

  • Business - IT Service is provided from Service supplier to customer;

  • Operational - one of the company's departments delivers IT Service as a provider;

  • Underpinning - an IT Service is delivered to a Service provider by the third party;

  • Request - IT Service is provided on request.

Master Service

Specifies a primary IT Service if necessary.

Assign a Master Service choosing it from the list of the CI Items with the IT Service type value.

Service Specification

Defines internal and external articles described in the Knowledge Base, e.g., SLA records, Service Description, and other articles related to the IT Service. 

Business Criticality

Specifies an IT Service cruciality to a business with one of two values:

  • High - has a big impact on business;

  • Low - has a little effect on business.

Custom CI Attributes


Serial Number

Automatically assigned to a record when having been created.

Name

A name of a Configuration Item.

Primary IT Service

Specify an IT Service to be delivered selecting it from the list of the CI Items with an IT Service type value.

Serial Number

Enter a serial number of your configuration component if it has one.

IP Adress

Enter the IP number of your configuration device if it has one.

DNS

Enter the DNS adress of your CI if it has one.

Location

Define the CI location selecting it from the Location list.

Push the Save button to apply the changes or Save and Exit button to save new CI and leave the form.

Related Lists:

  • External Service Specification - all the external service specifications bound to a particular CI;
  • Internal Service Specification - all the internal service specifications bound to a CI;
  • Outgoing CMDB Relationship - all the relationships with the CIs comming coming from this CI;
  • Incoming CMDB Relationship - all the relationships with the CIs comming coming to this CI;
  • Child Service - all the Services which this CI as a Master Service;
  • Related CI - a list of CIs which have this one as a Primary IT Service;
  • ITSM Event - a list of ITSM Events related to this CI;
  • Incident - a list of Incidents that are related to a current CI;
  • Problem - all the problems related to this CI;
  • Change Request -all Change Requests related to the CI;
  • Request - all the Requests that are related to a current CI;
  • Approval - all the related Approvals.

To extend or to customize your CI set of attributes depending on the CI Type, use the CMDB Expansion features.

CI Relationships


A CI Relationship describes a connection between two Configuration Items by determining the attributes of this relation.

CI Relationships are represented with unidirectional and bidirectional single-directional and bi-directional arrows connecting the CIs with each other on the Service Dependency Map.

Push the Connection button next Dependency Map button Image Added next to the Source CI or the Recipient CI field to open the Dependency Map view.

CI Relationship direction

Determine an impact direction of the CI Relationship, when choosing a source CI and a recipient one. If In case any of the source CI degrades or becomes degraded or unavailable,  it will have a negative impact on the recipient CI through is adversely affected according to the established relationship.

If both source and recipient CIs have this kind of impact on each other, set the Bilateral Relation checkbox active. 

CI Relationship Condition

A negative impact from the Source CI can lead to an immediate degradation of the Recepient Recipient CI regardless of the conditions or other supporting Source CIs. The Operational Status Transfer Type with the Unconditional value allows specifying the CI Relationship as such an impact. The Relationship weight of this type of connection is equal to 1.

In case a other cases, Recipient CI status is provided by few Source CIs and stays should stay active even after a the degradation of one of these CIs, the Operartional them. To apply this kind of CI Relationship, specify the Operational Status Transfer Type should be specified with the Conditional value. Depending on amount of this kind of CI Relationships from the Source CIs to a particular Recipient CI, the Relationship Weights have the same values, in total equal to 1The Weights of these relationships have the same value - 1/n, where n is their total number.

Add a new CI Relationship

To establish a new CI RelationshiRelationship, go to the CMDB → CI Relationships menu, and , then, push the New button. Please, Then fill in the form:

Field

Description

Source CI

Select a CI from the list to make a relationship outcoming from it.

Recipient CI

Select a CI from the list to specify a relationship as incoming.

Bilateral Relation

Switch this checkbox on to make the CI Relationship come in both directions: from a source CI to a recipient, and conversely.

Operational Status Transfer Type

Choose one of the possible values describing the type of the operational impact:

  • Conditional;
  • Unconditional.

Relationship Weight

Defines a CI Relationship weight with a decimal number, equal to or less than 1.

Weight on change


To save a created CI Relationship record, push the Save or Save and Exit button. 

Service Dependency Map


A Service Dependency Map is a Service Model represented by an hierarchical structure of the CIs with an IT Service on the top and their current operational states as coloured marks. 

All CIs related to an IT Service are arranged by hierarchical levels that are determined by CI Types. Since each CI Type defines the hierarchical level of the Service Dependency Map, creating a new type will result in adding a new lower level of this model. 

CIs are presented as model elements with colour-coded frames depending on their current Operational State values. The following table shows colour and state accordance:

CI Frame ColourCI Operational State
GreenAvailable
YellowDegraded
RedUnavailable, Maintanence

CI Relationships are visualized with unidirectional or bidirectional arrows depending on an impact direction. 

Push the Connection button next to the Primary IT Service field Dependency Map button Image Added next to the Source CI or the Recipient CI field of the CI Relationship to see the hierarchical place of your CI on the Service Dependency map.

Create a CI Relationship

You can add a new CI Relationship from the Dependency Map view. Right-click on the desired CI and choose Create Relationship option in the popup menu, then select one of the possible values:

  • Incoming - to create an incoming connection to your CI;
  • Outgoing - to create an outgoing connection from your CI. 

Fill in the form of a new CI Relationship and push the Save or Save and Exit button.

Change a CI Operational State

You can change the CI Relationship State right from the Dependency Map view. Right-click on the desired CI and and select Change Operational State option in the popup menu, then, choose one of the possible CI Operational state values:

  • Available - CI with this state value are marked with the green frame on the map view;
  • Degraded - marks CI with yellow frame;
  • Unavailable - marks CI with red frame;
  • Maintenance - also marks CI with red frame, as CI is not available while in maintenance state.


Table of Contents
maxLevel3
classfixedPosition