Terms & Definitions
Versions, variants and configurations
Although these terms are sometimes used as synonyms, they can be clearly differentiated from each other. To understand a Global Configurations scenario, it is essential to use these terms correctly and unambiguously.
These are widely used definitions of Configuration Management, Version Management and Variant Management.
Configuration
Management
Management of all configuration components of a product throughout the entire lifecycle, across all engineering disciplines and tools.
- Complete systems
- IT infrastructure
- Mechanics
- Electrical engineering
- Software
Version
Management
Management of different development statuses or changes on the timeline, related to individual artifacts or systems.
- Software development
- Document management
Variant
Management
Management of parallel variants of a product with a differentiated view of common and different components, with the least possible effort in terms of maintaining changes.
- Product line management
Configuration Management
Definition:
Configuration management deals with the management and control of all components of a product or system throughout its entire lifecycle. It ensures that all components are correctly documented, traceable and consistent.
Typical tasks:
- Definition and management of configuration elements (e.g. software, hardware, documentation)
- Tracking changes and their effects
- Ensuring consistency between different development and operational phases
- Traceability of changes through configuration control
Application example:
Version Management
Definition:
Version management is a sub-area of configuration management and deals with the management of different development statuses of an artefact (e.g. software or a document). It enables tracking of changes, rolling back to older versions and parallel working in a team.
Typical tasks:
- Management of different versions of a product or file
- Preventing loss of data through change tracking
- Merging of parallel development branches (branching & merging)
- Provision of historical statuses for error analysis or reproduction
Application example:
A software development team uses Git to manage different versions of software. Every developer can make changes and it is documented who has changed what.
Variant Management
Definition:
Variant management deals with the management of different product variants. It is irrelevant whether these variants exist in parallel, sequentially or overlapping. It enables product variants to be developed, maintained and documented in a controlled manner. The reuse of common components is very important here, as is the management of individual differences between variants of a product.
Typical tasks:
- Systematic organisation of product variants (e.g. different versions of a car)
- Modularisation and reuse of components to increase efficiency
- Ensuring consistency between different variants
- Support in deciding which variants should be offered
Application example:
A car manufacturer offers a vehicle model in different variants (e.g. diesel, petrol, electric). These variants share many components, but have specific differences (e.g. drive, battery size, software functions).
Please contact us:
We talk Global Config
Do you have questions about Global Configuration Management?
Tap into our decades of experience from many successful projects.
Contact us by email or phone: