Glossary · Engineering, integration and validation
Configuration management
Also known as: CM
German: Konfigurationsmanagement
In systems and software engineering, configuration management is the coordinated activity of identifying the configuration items of a product, controlling changes to them, recording their status and auditing that the product matches its documented configuration. It applies to hardware, software, parameters and documentation over the whole life cycle.
- Validation
- Standards
In one sentence
Configuration management identifies configuration items, controls their changes, records their status and audits that product and documentation match.
Example
For a filling machine, configuration management records which PLC program version, drive parameter set and manual revision belong to serial number 4711.
Explained in context
This term is a station of a mini course
- The medical-device evidence chain: from intended purpose to post-market evidenceStation: Variants, reuse and their boundariesStart the course
- When an AI agent crosses the line: detect, contain and restore operationsStation: CCMS, DMS and knowledge basesStart the course
Context cards connect this term with others to answer one question. Also in British English and German.
- From structured content to controlled evidence: five stages of AI-ready documentationIs structured content enough to make medical-device documentation ready for AI?UKDeutsch
- The medical-device evidence chain: from intended purpose to post-market evidenceHow do the parts of a medical device’s technical documentation connect — and what has to be in place before an AI function may answer from it?UKDeutsch
- Model version, software version, device version: three numbers that are not the sameWhat is the difference between the model version, the software version and the device version of an AI-enabled medical device?UKDeutsch
- From a locked model to planned change: documenting model updates of a medical deviceHow can an AI-enabled medical device change its model without every update becoming a new regulatory question?UKDeutsch
- Who decides which value counts: which system decides a value of product information?When product information passes through PLM, ERP, content systems, spreadsheets, portals and AI functions, how do you tell which system decides a value and which one only holds a copy?UKDeutsch
- When an AI agent crosses the line: detect, contain and restore operationsWhat has to be in place when an AI agent does something it isn’t allowed to do — in IT systems, IoT fleets, OT and on machines — and how is it detected, stopped and released again?UKDeutsch
- The agent master record as a documentation objectWhat should an agent master record for an AI agent contain?UKDeutsch
- Retrofit and substantial modification under the Machinery RegulationWhen does a retrofit make the operator the manufacturer of a machine?UKDeutsch
How it applies
- Engineering: The project defines configuration items, such as control programs, HMI projects, drive parameters, drawings and manuals, and assigns identifiers and versions to each.
- Operation: Plant owners keep the installed configuration of each machine on record, so service staff know which software and documents apply before they intervene.
- Maintenance: Changes go through Change control and create a new Configuration baseline; audits confirm that the delivered product and its records agree.
- Documentation: The documentation team treats manuals, parameter lists and safety information as configuration items with their own versions and records which document revision belongs to which product configuration.
Configuration management vs. version control
Version control tracks the history of individual files or repositories. Configuration management is the broader discipline: it decides what is controlled, how changes are approved and how the consistency of the whole product configuration is verified. A version control system is one tool that supports it.
ISO 10007 gives guidance on configuration management within a quality management system; ISO/IEC/IEEE 15288 treats it as a technical management process.