Systems Engineering - Konfigurationsmanagement

„Configuration management is a management process for preparing and maintaining a consistency of product performance and the functional and physical characteristics of the product with the requirements, product design and operational information throughout the entire product life cycle." ANSI & EIA

The purpose of configuration management is to manage the technical description of a system (and its various components), as well as all of the changes that were applied during the development of the system.
Many sub-processes in configuration management work together to successfully complete development and above all to keep the whole time an consistent overview on the workproducts.


There are four sub-areas (sub-processes) of configuration management:

• Configuration Identification (CI)
• Configuration Accounting (CAC)
• Configuration Control (CC)
• Configuration Audit (CAU)

Configuration Identification (CI): CI includes the selection of configuration items, their formation to a product structure, documentation, and reference form for the purpose of unique identification. Essential issues are related to the granularity of a configuration unit, the definition of reference configurations (Baselines) as well as the selection of a numbering system. In addition, here exist planning aspects such as the release- and baseline management.

Configuration Accounting (CAC): The process of configuration accounting has the target to create transparent documentation of configurations and configuration units. You should start with CAC already when generating the first set of configuration data. Subject of the CAC are all configuration data for identification and monitoring.

Configuration Control (CC): CC addresses problems arising from the change of a configuration. Central activity is the change management. The goal of change management is to identify, describe, classify, evaluate, approve and implement all changes to configuration items and to their associated documents. Reasonable configuration control requires a committed, formal process for dealing with changes.

Configuration Audit (CAU): A configuration audit is a formal review of configurations for the performance of contractually agreed functional and physical characteristics as well as the discovery of unrealized product and associated configuration documentation.

Change Management

Changes of requirements during the start of the project or, even worse, during development phase can lead to significant challenges. Only a well-structured and proper defined change management can deal with these challenges. Desired changes must go through a process in which they are examined, possibly implemented and verified later.

INVENSITY supports your company in order to create a change management process and accompanies you in its introduction. We prepare your staff with a workshop for the new process and coach the staff during the first few weeks.

Release Management

The release management covers the complete development of a product. On the one hand, the functional scope as well as a timetable in adjustment with the change and product management is defined. On the other hand, there is a quality control addressing the fulfillment of the selected criteria and the documentation of the various release levels will be monitored.

The experienced consultants of INVENSITY organize and monitor the exact compliance of your entire release management in an operative way.

INVENSITY is your reliable partner - talk to us. We are at your disposal for further questions.