Product Lifecycle Management (PLM)
PLM (Product Lifecycle Management) manages product data, processes, and decisions across the full lifecycle — from design through manufacturing, service, and end of life.
Product Lifecycle Management (PLM) is the discipline and IT infrastructure for managing all product-related information and processes across the entire lifecycle of a product — from requirements and design through manufacturing, service, and end of life. In the context of variant management, PLM is the system layer where product structures, configuration models, engineering change processes, and variant documentation are managed for product families with multiple variants.
PLM is distinct from ERP (Enterprise Resource Planning): ERP manages transactional business processes — orders, inventory, finance, production. PLM manages the product itself — its definition, its design data, its structure, and how it changes over time. In companies with complex product families, PLM and ERP must be tightly integrated: the variant BOM derived from the PLM configuration model must flow into the ERP system to drive production and procurement.
What PLM manages
A PLM system is the single source of truth for the product across its lifecycle. Its core functions include:
- Product structure management — The hierarchical product structure Product Structure (ˈprä-dəkt ˈstrək-chər) n. A product structure is the hierarchical decomposition of a product into components and subassemblies — the engineering foundation for BOM management and variant documentation. (assemblies, components, parts) and all associated engineering data (drawings, models, specifications).
- Configuration management — The formal identification, control, and auditing of product configurations, including effectivity management (which version of a component applies to which product build range).
- Change management — The process of evaluating, approving, and implementing engineering changes, including impact assessment across all affected variants.
- Variant and configuration modeling — The definition of options, rules, and constraints that govern the product family’s variant space.
- Document management — Engineering drawings, 3D CAD models, simulation results, test reports, and regulatory documentation, linked to the product structure.
- Lifecycle status tracking — Whether each part or assembly is in development, released, obsolete, or under change.
PLM and variant management
For companies managing product families with significant variety, PLM is the natural home of the variant management model:
- The 150% BOM 150% BOM (ˌwən-ˌfif-tē pər-ˈsent ˌbil əv mə-ˈtir-ē-əlz) n. A 150% BOM lists all possible components across all product variants, serving as the master structure for subtractive configuration in variant management. or generic product structure lives in the PLM system, with variant rules attached to each node.
- Option definitions, characteristics Characteristics (ˌker-ik-tə-ˈris-tiks) n. pl. In variant configuration, a characteristic is a named property with a defined set of values — the core building block used to model variation points in configurator systems. , and constraint rules are managed in the PLM configuration module.
- When a customer order arrives, the PLM-resident configuration model is used to derive the specific variant BOM for that order.
- Engineering changes to shared components are managed through PLM change processes, with impact assessed across all variant combinations that use the changed part.
Without PLM integration, variant management is fragmented: configuration rules exist in CPQ systems, BOMs in spreadsheets, and engineering data in CAD file repositories — with no authoritative single source connecting them.
PLM systems
Major PLM platforms used in discrete manufacturing include:
- Siemens Teamcenter — Widely used in automotive, aerospace, and industrial machinery
- PTC Windchill — Strong in discrete manufacturing and service lifecycle management
- Dassault Systèmes ENOVIA / 3DEXPERIENCE — Dominant in aerospace, automotive, and high-tech
- SAP PLM — Integrated with SAP ERP, used where the SAP ecosystem is the standard
Smaller and mid-market companies often use Arena, Propel, or OpenBOM. The choice of PLM system shapes how variant management is implemented technically, but the underlying principles are system-independent.
PLM versus ERP in variant management
The division of responsibility between PLM and ERP for variant management data is a common source of complexity:
| Domain | PLM | ERP |
|---|---|---|
| Product structure | Authoritative source | Derived (manufacturing BOM) |
| Configuration model | Defined and managed here | Configuration rules may be replicated here (e.g., SAP LO-VC) |
| Engineering change | Managed here | Effectivity dates applied here |
| Order-specific BOM | Derived here (optional) | Derived here (from config rules) |
| Inventory and procurement | Not managed | Authoritative source |
In practice, companies choose different integration architectures: some derive the order BOM in PLM and transfer it to ERP; others maintain the full configuration model in ERP (e.g., SAP LO-VC / KMAT) and derive the BOM at order time in ERP. Both approaches have merits depending on the complexity of the variant model and the capabilities of the systems involved.
Frequently asked questions
Is PLM software necessary for variant management?
A dedicated PLM system is not strictly necessary for variant management, but it becomes practically essential as product complexity and variant count grow. Small product families can be managed in spreadsheets and shared drives. Once a product family has hundreds of variants, complex constraint rules, frequent engineering changes, and multiple engineering disciplines contributing to the product structure, the limitations of unstructured tools become the primary bottleneck. PLM provides the data structure and process governance that makes systematic variant management scalable.
What is the difference between PLM and PDM?
PDM (Product Data Management) is the predecessor to PLM and typically covers document and CAD data management — storing and versioning engineering files and managing the product structure. PLM extends this to include the full lifecycle: requirements management, project planning, configuration management, change processes, manufacturing process planning, service documentation, and end-of-life. In current usage, most PLM systems include full PDM capabilities; the term PDM is often used for simpler or legacy implementations.