Product lifecycle management (PLM)
An approach to managing product-related information across a product lifecycle.
Operations glossary
PLM is an approach to managing product information across its lifecycle.
This definition explains product lifecycle management, product lifecycle, and product data management—and why those terms do not select a system, process, record, or product decision.
Product lifecycle management (PLM) is an approach to managing product-related information across a product lifecycle. It can describe principles, processes, and supporting systems; it does not create a product record, validate a specification, or decide what a team should do. Read NIST’s lifecycle-support reference.
Three related terms
The terms are related, but they do different jobs.
A shared vocabulary can make a lifecycle conversation clearer without deciding how a particular product, record, or system should be managed.
Product lifecycle
The sequence of stages used to describe a product over time. The term does not prescribe a stage-gate process.
Product data management (PDM)
A related discipline concerned with product information. It is not interchangeable with every PLM process or system.
Why the distinction matters
A lifecycle term can frame a conversation. It does not settle the record.
The important distinction
A definition explains the label. It does not manage the product.
PLM is meaningful only in a particular context. The term itself cannot choose a lifecycle, system, product version, specification, supplier, reviewer, or action.
Context matters
Product information can appear in different handoffs.
Teams may discuss a formula, packaging, bill of materials, supplier document, production record, or change. The PLM label alone does not establish a source of truth, record version, approval, compliance status, or decision.
A source note
Common language helps a team describe a question.
Different teams, products, suppliers, specifications, and records can use the same lifecycle vocabulary while having different responsibilities and constraints.
Keep the term and the decision separate.
NIST describes lifecycle support as involving the creation, exchange, management, and archival of information about products and related areas. That explains the information context; it does not determine a record, process, system, or outcome for a specific business.
Glossary boundary: This page does not provide a PLM implementation, lifecycle process, product-data system, record review, change-control decision, or product recommendation.
What this glossary does not decide
This educational definition does not create, store, exchange, manage, archive, change, approve, validate, compare, version, classify, or assess a product, formula, ingredient, packaging item, specification, bill of materials, supplier/co-packer record, production record, label, document, process, lifecycle, system, workflow, or handoff; select a lifecycle stage, gate, system, supplier, co-packer, formula, specification, packaging, process, data model, record, owner, reviewer, action, price, forecast, inventory level, production plan, or launch plan; determine a record’s accuracy, completeness, version, approval, quality, safety, compliance, cost, margin, availability, suitability, readiness, or outcome; or provide legal, regulatory, food-safety, quality, accounting, tax, financial, procurement, supplier, operational, product-development, lifecycle, or implementation advice.
Source note
References for this definition
These sources support the terminology on this page. They are not a substitute for a business’s own qualified reviewers, records, or applicable authorities.
Building commercial workflows with CPG design partners
Help shape a clearer way to keep product context and operating handoffs connected.
A working prototype validated Guidance’s core operating model. The commercial rebuild is translating that proof into production-ready workflows with CPG design partners.
Apply as a Design Partner →