In-depth analysis tagged Change Management — covering PLM history, vendor strategy, and the technical decisions reshaping engineering software.
1 article
In Product Lifecycle Management (PLM), a Configuration Baseline is a predefined set of product parameters, specifications, and attributes that serve as a reference point for changes to a product's design or configuration. It ensures consistency and accuracy across the product development process by providing a single source of truth for product information.
Configuration Management is the PLM discipline that answers the question: 'which version of the product did we ship to which customer, and what is in it?' It governs variants (different flavors of the same product line), options (customer-selectable features), and effectivity (the date or serial number at which a change applies). Configuration management ensures the as-shipped configuration of a specific unit — including the precise revision of every component — is recoverable years later for service, recall, audit, or regulatory inquiry.
An Engineering Change Order is the formal, audited record of an approved change to a product design. In PDM, changes are informal — just new file revisions. In PLM, ECOs follow a three-stage governed flow: Engineering Change Request (the problem), Engineering Change Notice (the proposed solution with impact analysis), and finally the ECO (authorization to implement with effectivity dates and affected serial numbers). ECOs create an auditable trail required by regulated industries and supply-chain accountability.
Product variants are the distinct, separately orderable configurations of a base product, each defined by a unique combination of options, features and component selections. Managing the space of valid variants is variant management, a discipline related to but distinct from configuration management.
