The Different Meanings of "Configuration"
Configuration means different things to different people: variant selection, baseline management, or software parameters. Here is how to tell them apart.
Glossary
Variant Management
Configuration Management
n. (kən-ˌfi-gyə-ˈrā-shən ˈma-nij-mənt)
Related terms
Definition
Configuration management is the systematic process of tracking and controlling changes to a product or system across its lifecycle in PLM and engineering.
Configuration management refers to the systematic process of tracking, documenting, and controlling changes to a product, system, or software across its entire lifecycle. It ensures that all components, documents, and interfaces remain consistent, traceable, and aligned with authorized requirements at every point in time.
What configuration management does
Configuration management answers three fundamental questions about any product or system:
- What is it? — Configuration identification defines and documents the product’s structure, components, and their relationships (the configuration baseline).
- What changed, and why? — Configuration control governs how changes are proposed, evaluated, approved, and implemented. No unauthorized change reaches the product.
- What is its current state? — Configuration status accounting provides a continuous, auditable record of what version each component is at and what changes have been applied.
- Is it what it’s supposed to be? — Configuration audits verify that the physical product matches its documented configuration.
These four activities — identification, control, status accounting, and audit — are the classical pillars of configuration management as defined in standards such as EIA-649 and ISO 10007.
Configuration management in PLM and variant management
In product lifecycle management, configuration management is particularly important when products exist in multiple variants or are modified across generations. A failure in configuration management can mean that the physical product delivered to a customer does not match the engineering specification — or that a change to one variant inadvertently breaks another.
In the context of variant management, configuration management provides the traceability layer: which components belong to which variant, which changes have been authorized, and which product version is currently in series production.
Configuration management is closely related to — but distinct from — variant configuration Configuration (kən-ˌfi-gyə-ˈrā-shən) n. Configuration has three distinct meanings in PLM: variant configuration, configuration management, and parameterization — each describing a different kind of joining. . Variant configuration selects options to define what a product is. Configuration management tracks and controls how it changes over time.
Tools and systems
Configuration management is typically supported by:
- PLM systems (e.g., Siemens Teamcenter, PTC Windchill, SAP PLM) — manage product structures, BOMs, and change processes
- Version control systems (e.g., Git) — in software-heavy products, provide fine-grained change tracking at the artifact level
- Change management workflows — engineering change requests (ECR), engineering change orders (ECO), and approval processes
Note: In software development, “configuration management” is often used informally to mean version control. In systems and mechanical engineering, it has a broader and more formal meaning encompassing physical products, documentation, and cross-functional change governance.
Frequently asked questions
What is the difference between configuration management and change management?
Configuration management is the system that defines the authorized state of a product and tracks its history. Change management is the process within configuration management that governs how authorized changes are proposed, reviewed, approved, and implemented. Change management is a subprocess of configuration management, not a separate discipline.
Why is configuration management critical in variant management?
In a multi-variant product environment, a change to a shared component can affect dozens or hundreds of variants. Configuration management ensures that such changes are evaluated against all affected variants, approved by the right stakeholders, and implemented consistently — preventing the unintended introduction of defects or incompatibilities across the product portfolio.