Configuration management



The objective of Configuration management process is:

  • To identify, record and control configuration items including their versions, properties and relations.
  • To ensure integrity of configuration items during their whole life cycle in order that only authorized items are used and only authorized changes of items are performed.

Administrator IS, CSOB Leasing:

ObjectGears Configuration management enabled us to interconnect incidents, planned work and documentation with real configuration items like hardware, applications, databases or network elements.

Configuration items can vary in type - from service, hardware device to software and documentation. Configuration items are stored in Configuration database CMDB).

Configuration management process interfaces number of other entities and processes.

Configuration management identifies, records and controls configuration items in a Configuration database (CMDB).

ObjectGears Configuration management records relation to configuration items at these main entities:

  • Project (project scope meaning added, modified and removed configuration items)
  • Task (affected items - subject of the task)
  • Work schedule (planned activities with stating affected items)
  • Knowledge Base (items concerned in the article in the Knowledge Base)
  • Incident, Problem and other entities of the Incident and Problem management process (items related to Incident/Problem and other entities)
  • Release (items that are part of the release package)
  • Changes (items that are subject of changes)

When the user displays a configuration item in ObjectGears, he/she can immediatelly see all the above stated connections.


Watch a video showing synergic effects of Configuration management with Processes and Resource planning and reporting time spent on projects, tasks, incidents etc.

Examples of screens

(Examples stated hereinafter represent only a sample from the whole number of configuration items types.)

Hardware device

This entity is used for servers, enclosures, disk storages, back up libraries, switches and other network elements, printers, projectors and other physical devices. Key attributes are vendor, device type, serial number, owner, inventory number, location, purchase date, end of support date, environment...

Hardware device detail

Machine (OS server, System)

Machine (OS server) detail

Server running on hardware device - operating system. Key attributes of the entity are operating system, name, FQDN, type (server, workstation, cluster, cluster service, farm, appliance...), farm, on which the system runs as virtual machine, or hardware device, on which system runs as physical (native) server, membership in farm/cluster, IP address, the way of getting IP address (DHCP reservation), Windows domain, CPU, RAM, disks, environment, security zone...

Database server

Database server providing particular databases, that runs on Machine (OS server) - see above stated example of configuration item. Key attributes are instance name, database server version and Machine, on which the database server is installed.

Database server detail


Database detail

Database containing application data. Key attributes are name, database server handling the database, recovery model, collation, date of the last back up, size, compatibility mode...

Relationships between entities depend on your situation and needs. You can see the default model of system, hardware, application or e.g. project layer in the documentation. The model is adapted to your needs at the time of implementation. Entities and properties that are not necessary are hidden. New features are are added or current ones modified.