Configuration Management tables

The information displayed on the Configuration Item form is the result of the device, attribute, and join files working together.

File or record	Definition
Asset record	A record that stores details about a piece of equipment or other component.
Device type file	Each asset in the Configuration Management database has a Configuration Item (CI) type. The CI type (the devtype file) contains one record for each CI defined. When you define a new CI type, the devtype file adds a new record.
Device file	Contains all asset records. Each record contains the unique name of the asset and the pointers to other files. For example, serial.no and vendor/supplier are common fields for both the server and modem device types.
Attribute file	Contains data specific to an asset, depending on its device type. If an attribute file exists for a device type, each asset record for that device type has a corresponding attribute record in the device type’s attribute file. For example, a storage device type has an attribute file named storage and contains fields that are specific to a storage asset, such as storage.type. A software license device type has an attribute file named softwarelicense that contains fields that are specific to a software license asset, such as product.pool.
Join file	A record that displays information from the device file and attribute file for the specified device type. If you make changes to the data, Configuration Management writes the information into the corresponding records in the device file and attribute file. For example, a server device type has a join file named deviceserver. It contains fields that are a combination of the device file and the relevant attribute file, such as serial.no and vendor/supplier from the device file and printer.queues from the server file.

Configuration item relationships

Service Manager tracks upstream and downstream relationships between configuration items (CIs). A relationship between CIs means that there is some dependency between CIs. If an upstream CI has an interruption of service, Service Manager assumes that all CIs with a downstream relationship to the affected CI also have an interruption of service. For example, if a network router has an interruption of service, then all servers and PCs that connect to that router also have an interruption of service.

Any given CI typically has one upstream relationship and one or more downstream relationships. CIs can have logical or physical relationships based on the logical name of the configuration item. CI relationships are independent of baseline, actual, or managed states.

Device table

The device table is the central repository for Configuration Item (CI) information. The table contains a record for each CI (hardware or software). These records provide information to populate forms used by other Service Manager applications, such as Incident Management.

When you view asset records, the form tabs and field data vary, depending on the asset selected. Only information common to all network components is stored in the device table. Asset records are identified by the logical.name field.

Characteristics of the device table:

• Only one device table.
• One logical record in the device table for every tracked asset or CI.
• logical.name field is the unique identifier in the dbdict for the device table.

Devtype table

The devtype table contains a record for each type of CI that you are tracking.

Depending on the CI component type, each logical component in the device table may have a corresponding record in a separate attribute table. Attribute tables define all common and unique attributes that appear when you select a CI type.

Cigroup table

The cigroup table consists of all information used to define items in a CI group and a list of items included in the group. There is one record for each CI group defined.

Characteristics of the cigroup table:

• Contains the group name.
• The logical.name field is the unique identifier in the dbdict for the cigroup table.
• For list-based groups, contains a list of members.
• Baseline groups and Query-based groups are dynamic and therefore do not contain members.
• Specifies a group type, such as a query-based group, a list-based group, or a baseline group.
• If the group is a baseline group, it contains the baseline version and state. This does not apply to list-based or query-based groups.

Attribute tables

Most hardware or software Configuration item (CI) types have a set of descriptive attributes. Generally, each CI type has attributes that are organized into logical attribute records in an Attribute table. There are exceptions. Not all CI types have attribute tables, and, although the CI type records are different, a class of CI types can have the same attributes. The attribute record links to the CI record using the same identifier in the logical.name field. All other information in the attribute record and the CI record is unique.

Characteristics of attribute tables:

• There is one attribute table for every CI type.
• Attribute tables have the same name as their CI type.
• The logical.name field is the unique identifier in the dbdict for the attribute table.

For example, the following is a list of the out-of-box attribute tables for standard network components:

• bridge
• circuit
• controller
• CPU
• FEP
• modem
• multiplexer
• path
• peripheral
• port
• switch
• workstation

Join tables

A join table is a temporary logical table that has the following properties and functions:

• Resides only in memory
• Contains no records
• Is not written to the database
• Points to the data in the device table and related attribute table.
• Does have a dbdict

The join table temporarily joins the fields in the device table record with the fields in the attribute table. Join tables are never populated. They only serve as pointers to fields that are extracted from the device table and the attribute tables and they display the joined data in a form. When you make changes to the join table by making changes to the data in a form, Service Manager writes the changes to the original device and attribute tables.

As a rule, the join table name hasdevice as a prefix and the attribute table name as the suffix. For example, the join table name for a PC component is devicepc. The form that displays the joined data is named device.attribute, for example, device.pc.

Join tables are named according to the following conventions:

• Join table name is a combination of the device table name and its attribute table name (device.attribute.name).
• Logical.name field is the unique identifier in the dbdict for the device and attribute tables.

Creating subtables from an array of structures

Service Manager enables a dbdict administrator to manage data more effectively by creating subtables of unique and non-unique attributes within an array of structures. You can use this feature to achieve the following benefits:

• Improve mapping to external SQL database tables.
• Implement a more cost-effective solution for managing attribute information.
• Simplify queries.

The dbdict administrator can identify two subtable names for each array of structures in the dbdict. One table contains the names of unique attributes. The second table names non-unique attributes. A pop-up utility dialog box enables you to identify which attributes are unique.

The subtable feature helps you create queries that can return detailed information. This type of available detail can improve business and management decisions. You can create subtables for an array of structures in any dbdict. Service Manager provided out-of-box subtables already created for all arrays of structures in the inventory dbdicts.

Configuration Management forms

Configuration Management uses three types of forms.

Form	Description
Device	The forms device and device.g display query results for fields common to all CI types. For example, a PC record may appear using device.g.
Attribute	There is one form for each attribute file. The form displays detailed attribute data. The form name matches the attribute file name. For example, if the attribute file name is circuit, the form name is circuit.
Join	There is one form for each join file. The form enables you to view, populate, and update fields in both device and attribute files. Normal functions are available to add, delete, and update the records. Special functions are available to access parents and children. For example, if the join file name is devicecircuit, the form name is device.circuit.

Configuration item types and subtypes

Service Manager includes the following out-of-box Configuration Item (CI) types and subtypes.

Type	Subtype
Application	Anti-Virus / Security Back-up Business Development Tools Entertainment Graphics Internet/Web Networking Operating System Reference Other
Business Service	Application Service Business Service Infrastructure Service
CI Group	Ad hoc Baseline
Computer	Desktop Dumb Terminal Host Laptop Logical Partition MAC Mainframe Server Terminal Server Tower Unix VAX Windows
Display Device	Monitor Projector
Example	Template of common device fields that you can use to create a new device type.
Furnishings	Armoire Artwork Bookcase Chair Computer Desk Desk Collection File Cabinet Meeting Table
Hand Held Devices	Blackberry Device Cell Phone GPS Device Pager PDA
Mainframe	Controller FEP Host CPU LPAR NCP
Network Components	ATM Switch Concentrator Firewall Gateway Hub LB Modem Network Component Network Interface Card RAS Router Switch Router Switch
Office Electronics	Calculator Camera Copy Machine Fax Machine Multifunction Net Printer Paper Shredder Printer Speaker Television Typewriter UPS VCR Word Processor
Software License	DBMS License Development Tool License Enterprise Management License Operating System License Outlook Productivity Tools License Project Management License Utility Software License
Storage	CD Burner CDRW Direct Attached Storage (DAS) HDD Network Attached Storage (NAS) Storage Area Network (SAN) ZIP
Telecommunications	Desk Phone Flush Wall Mount Headsets and Accessories NBX Paging Solution PBX Surface Mount