CI Schemas

In the CMDB schema configuration stage several schemas can be consolidated. On one hand, the CI schemas and the corresponding types are configured, on the other hand, zone schemas and the default hierarchy of the zones is managed.

 

The Difference Between CI-Schemas and CI-Types

Just like in a ticket schema, all settings, fields, actions, and Service Level Agreements for CIs to be based on this schema later on can be defined and saved in a CI schema.

The distinction between schemas and types has been made mostly due to clarity. While all configurations of the CIs are made in the CI schema, the configuration of the types determines, which tabs and fields will be displayed in the CIs later on.

Note:

A CI schema contains all definitions necessary for creating CIs. Thus, the attributes (fields) and field types have to be planned thoroughly - subsequently modified field types may lead to problems with the field value compatibility. For identifying a CI, it is advisable to create a logical pattern.

 

Schema Hierarchy

The hierarchy of the CMDB schemas can be created as a flat or a deep hierarchy. In contrast to zones and their hierarchy, a subdivision into various types and subtypes of items is established via the schema hierarchy. The deeper and more precise the hierarchy, the less defining is required for the individual CIs later on.

Example: Flat Hierarchy

• Devices

– Computer

Example: Deep Hierarchy

• IT devices

– Computer

∗ DELL

· Precision 380

Tip:

Drag and drop can be used for the schema configuration. When an element is moved, the inheritance will be adjusted automatically.