Previous Topic

Book Contents

Book Index

Next Topic

Asset Management In Use

Configuration Items

Individual pieces of infrastructure administered by Service Asset Configuration are referred to as Configuration Items.

The term 'Configuration Items' (CIs) covers a wide scope of business objects. Simple configuration items (Simple CI) describe end infrastructure elements which belong to/form complex configuration items (Complex CI). In some cases mandatory affiliation of simple CIs with a complex CI is applied. For instance, Components (simple CIs) belong to Systems (complex CI). Each component must belong to a system, a currently unused/unassigned component is registered as part of a 'Stock' system.

Configuration items are characterized by their attributes and their relationships to other CIs. Attribute values of a configuration item are recorded in the CI's Configuration Record. Each type of configuration item contains a specific set of attributes.

Some attributes of individual types of configuration items may require data in specific formats, for example manufacturer-specific serial numbers or varying model numbers, ISBN on books, version or edition numbers. To ensure data entry in the required format, a mask can be defined for the corresponding field via view customization. Entered data can also be automatically validated, data validation can be performed on several levels.

Configuration Items Administration

Configuration Item Creation

At the moment of entering a configuration item record, a new configuration item instance of a given type is created. The below listed use cases describe the most common scenarios of system and component creation. Other types of configuration items are created analogically using corresponding editors and catalogs.

At the time of entering a record, it is possible to directly establish relationships with other configuration items. Several types of configuration item relationships can be created.

  • Relation to one configuration item

    The relation to a single configuration item is established using a reference view in the configuration item editor. Examples include the assignment between system and (system coordinator) person or a component to the super-component where it is installed. The relations created in the reference view can be either of the n:1 relation type (cardinality). For example, a system can have only one system coordinator assigned.

  • Relation to a set of configuration items

    Relations to a set of configuration items are established using reference catalogs found in editor sections. The relations created here are either of the 1:n or n:m type. For example, a system can have many components but one component must belong to only one system (1:n), one system can have several documentation objects and each of these object can belong to more than one system (n:m).

Configuration Item Processing

The actions performed on configuration items are often referred to as IMAC (Install-Move-Add-Change) actions. Two types of IMAC actions are available in Valuemation Asset Management:

All configuration items can be edited in their object type editors, opened from the respective catalogs. Additionally, cross-object type actions are available:

  • Catalogs of components

    Right-click context menu in component catalogs provides the following cross-object type actions:

    • Edit System - opens for editing the system to which the component belongs
    • Configure Current System - opens System Configuration window with the system to which the component belongs preselected
    • Assign Contract Item - assigns contract items to components
  • Editor of system

    Create Order - button calls an action for creating an order for components of the system

Configuration Items Overview

  • Catalogs - Catalogs of configuration items can be opened via Smart Tiles or from the Sidebar. Catalogs can be filtered to display information as needed. Additionally, catalog 'My Assets' displays only systems assigned to the current user. The catalog is intended as a simplified overview and is read-only. Catalog information can be printed using Valuemation print functionality.
  • System Reports - System reports provide an overview of system quantities over the course of time, broken down by key system characteristics.

In This Chapter

System Creation

Component Creation

IMAC Service Actions

See Also

Asset Manager

Valuemation Asset Manager

Asset Management - Under the Hood