Classification Object Types

System Type

System Type represents technical categorization of systems. Examples of standard system types are 'User System', 'Server Windows' or 'Stock'.

Configuration Item Relation Definitions are defined at the level of system types, systems of the given system type then benefit from having relations to objects of other object types preselected according to the CIRD definition.

System Class

System Classes further classify System Types, thus enabling grouping of System Types with similar characteristics. System Class examples include 'IT Workplace', 'IT Server', 'IT Terminal' etc.

System classification can be used to control the availability of dynamic fields, individual system types may provide different sets of fields according to the System Class they belong to.

System Class attributes 'Asset relevant' and 'CMS relevant' enable categorization of system types according to their field of relevance, asset stock management or configuration management, respectively.

Component Type

Component Type represents technical categorization of components with the same technical characteristics.

Components which can only be differentiated from one another (physically) by the serial number are units of the same component type. The common characteristics of such components are described by their reference to a component type. Only those characteristics that are individual for each component despite belonging to the same component type are described for the component itself, e.g. inventory number, reference to a system, serial number, color. For this reason, component type must be specified when creating a component.

Component Class

Component Classes further classify Component Types, thus enabling grouping of Component Types with similar characteristics such as monitors, keyboards etc.

Component classification can be used to control the availability of dynamic fields, individual component types may provide different sets of fields according to the Component Class they belong to.

Usage Type

Usage Type represents classification of systems according to their type of use. System can be assigned to one or more usage types, For example. Each link between a system and a usage type is called Usage Type of a System. This link is time related, comments can be attached to it and it can be used as target for one or more subordinated systems via Two Systems Relationship objects.

System Performance Group

System Performance Groups enable grouping of systems offering the same level of performance to the user. Such grouping can be use e.g. in setting a unitary accounting price for systems offering the user the same level of performance.

Component Type Performance Group

Similar to System Performance Groups, Component Type Performance Groups enable grouping of components offering the same level of performance to the user.

Documentation Type

Documentation Types provide classification for 'Documentation' objects.

Individual documentation types can be classified as relevant for selected object types. For instance, if documentation types 'Improvement Plan' or 'Quality Plan' are classified as relevant for 'Service' only, then documentations of these documentation types can be linked to objects of 'Service' object type but not to other objects. This allows for a structured, consistent approach to object type documentation.

Note: In standard Valuemation, 'Improvement Plan' or 'Quality Plan' are by default relevant for all supported object types: System, Component, Interface, Service, Ticket, Ticket Description, Release, Activity.