product lifecycle management (PLM)

Product lifecycle management (PLM) commonly refers to the coordinated governance of product-related data, processes, and decisions across the entire life of a product, from initial concept and design through manufacturing, service, and end-of-life.

What PLM includes

In industrial and regulated manufacturing environments, PLM typically covers:

• Product definition data, such as CAD models, drawings, bills of material (BOM), specifications, recipes, and design history.
• Change and configuration management, including engineering change requests (ECR), engineering change orders (ECO), revisions, variants, and configuration baselines.
• Process and manufacturing definition, such as manufacturing BOMs, routings, work instructions, and tooling definitions, often handed off to MES and ERP.
• Collaboration workflows across engineering, quality, supply chain, and manufacturing, including controlled approvals and reviews.
• Traceable records that show how the product definition evolved, which versions were released, and what was authorized for production.

PLM is often supported by a PLM software platform that integrates with CAD, MES, ERP, QMS, and document control systems. In regulated industries, it may be used as part of the controlled environment for design history files, device master records, or similar regulated artifacts, but it does not replace quality or regulatory systems.

How PLM is used operationally

Operationally, PLM acts as the source of truth for the product definition before and during production:

• Engineering authors and maintains product structures and specifications in the PLM system.
• Approved revisions and change orders are released from PLM to downstream systems such as MES and ERP.
• Manufacturing uses PLM outputs (e.g., released BOMs, routings, 3D models, approved work instructions) as inputs for planning, scheduling, and execution.
• Quality and regulatory teams reference PLM records to understand design intent, approved configurations, and change history when investigating nonconformances, performing impact assessments, or preparing for audits.

Common confusion

• PLM vs. PDM: Product data management (PDM) usually focuses on controlling engineering files (CAD, drawings) and revisions. PLM is broader, managing end-to-end product structures, processes, and cross-functional workflows, not just file vaulting.
• PLM vs. MES: PLM manages the definition of the product and related changes. A manufacturing execution system (MES) manages the execution of production on the shop floor, including orders, routing execution, data collection, and traceability.
• PLM vs. ERP: ERP focuses on planning, finance, inventory, and order management. PLM focuses on product definition and change control. The two typically synchronize BOMs, material masters, and sometimes routing data.
• PLM vs. QMS: A quality management system (QMS) manages quality processes such as CAPA, nonconformances, audits, and complaints. PLM may integrate with QMS, and may store design-related quality records, but it is not the same as a QMS.

Relation to standards and security

PLM itself is a product and process governance concept. It is not a security or quality standard. In regulated manufacturing it often coexists with:

• Information security standards (for example, an ISMS based on ISO 27001) that govern how PLM data and systems are protected.
• Industrial cybersecurity frameworks (such as IEC 62443) that may apply when PLM connects to OT and plant systems.
• Manufacturing and quality standards (for example, those defining design controls, documentation, and traceability) that rely on PLM-managed records as part of evidence.

When PLM systems are integrated with MES, ERP, and other OT/IT components, organizations typically define clear scopes and interfaces to ensure that product data, change records, and access controls remain consistent across the lifecycle.