Configuration Management

Configuration management (CM) is the discipline of tracking and controlling the exact state of a system — knowing precisely what components are installed, in what versions, with what settings, at any point in time. In aerospace, CM ensures that every bolt, wire, and software version on an aircraft is documented and any change requires formal review, approval, and documentation. The four pillars are: identification (labeling every component with a unique identifier and version), control (no changes without formal review and approval), status accounting (maintaining a complete record of what changed, when, and why), and verification/audit (periodically confirming that the actual system matches the documented configuration).

When to use it

When managing any complex system where unauthorized or undocumented changes create risk, when you need to reproduce a system's exact state at a previous point in time, when diagnosing problems that might stem from undocumented modifications, or when ensuring that changes are reviewed before implementation.

How it can help

Configuration management thinking applies to any system where you need to know its exact state and control changes. In personal knowledge management, knowing what version of a document you're working from prevents wasted effort. In organizational policy, tracking which policies are current, which have been superseded, and what changed prevents contradictory guidance. In software deployment, configuration management (now often automated as 'infrastructure as code') prevents the terrifying situation of a system that works but nobody knows exactly how it's configured, so nobody can reproduce or fix it. The model teaches that change without documentation is a liability that compounds over time.