Product life cycle management (PLM)
Also called product lifecycle management.
Product life cycle management (PLM) is the coordination of a product's information, decisions and changes from its initial idea through design, production, service and retirement. It is a business process, often supported by software, rather than just a tool.
The phrase also has a marketing meaning: managing a product's commercial life from launch to decline. PLM software usually refers to the engineering and operational discipline, not the marketing-stage model.
Key takeaways
- PLM connects specifications, bills of materials, approvals and engineering changes so teams use the correct product version.
- Its scope extends beyond engineering to manufacturing, suppliers and service teams.
- A small company needs clear ownership and revision control before it needs an enterprise PLM system.
- For a hardware startup, one preventable production error can consume money intended for the next development milestone.
How PLM works
PLM starts with product requirements. As the design develops, the team creates drawings, specifications and a bill of materials: the list of parts and quantities needed to build the product.
Changes then follow a controlled process:
- Someone proposes a change and explains why.
- Engineering, purchasing and other affected teams review its consequences.
- An authorized person approves or rejects it.
- The approved revision reaches the manufacturer and replaces the previous instructions.
PLM also preserves the history. A service team should be able to identify which component went into a particular product, even after that component has been replaced in newer versions.
Software supports these steps, but cannot decide who has authority or resolve conflicting requirements.
Cutting obsolete inventory from 2,000 boards to 500
A hardware startup is changing its circuit board. An inventory review before release lets purchasing adjust orders and the team choose a better cutover date.
All figures below are illustrative. Old boards become unusable at cutover, have no salvage value and cost $18 each. Other costs are unchanged.
| Item | Uncoordinated cutover | Controlled cutover |
|---|---|---|
| Unusable old boards | 2,000 | 500 |
| Inventory write-off | $36,000 | $9,000 |
| Incremental PLM cost for the year, including setup and administration | $0 | $12,000 |
| Combined cost | $36,000 | $21,000 |
Avoided write-off: (2,000 - 500) × $18 = $27,000.
Net benefit for the year: $27,000 - $12,000 = $15,000.
This is not a savings benchmark. The benefit comes from changing purchasing and release decisions, not merely storing drawings in a new system.
What the change record should say
ISO 10007:2017, the configuration-management guideline, describes configuration identification, change control, status accounting and configuration audits.
For a startup, those principles translate into a change record that identifies:
- The affected part numbers and revisions.
- The reason for the change and its expected consequences.
- Who approved it.
- When the new revision takes effect.
- What happens to existing stock and products already shipped.
An approval without cutover instructions leaves the manufacturer to guess which version to build.
When a spreadsheet is enough
A shared document repository and a controlled change log can work while the team has few products and limited supplier coordination. Dedicated PLM becomes more useful when revisions, product variants and handoffs become difficult to track reliably.
Question a proposed system if nobody can explain which errors it will prevent or who will maintain its records. Before buying, ask the vendor to demonstrate one complete engineering change, from request through supplier acknowledgment.
PLM versus product data management
| Product life cycle management | Product data management (PDM) | |
|---|---|---|
| Main focus | Product decisions and processes across its life | Engineering files and design data |
| Typical records | Requirements, changes, approvals and product structures | CAD files, drawings and revisions |
| Relationship | Broader discipline | Often a component of PLM |
Questions people ask
What are the 5 stages of a product life cycle?
A common five-stage marketing model is development, introduction, growth, maturity and decline. Other models count only the four market stages after development. These describe commercial performance; they are not a universal workflow for PLM software.
What is product life cycle management?
It is the process of keeping product information and changes coordinated across the people who design, build, support and retire a product. A PLM system is software used to support that process.
What is an example of PLM?
A manufacturer replaces a discontinued sensor. Engineering updates the design, purchasing checks replacement availability, manufacturing receives the approved revision, and service retains records of which shipped units contain the old sensor. Coordinating that change is PLM.
Is SAP a PLM system?
SAP is a software vendor that offers PLM capabilities. Its offerings include SAP Integrated Product Development. Check the specific product, included functions and integrations rather than assuming every SAP installation provides the same PLM features.
Sources
- IBM, "What is product lifecycle management (PLM)?"
- SAP, "What is product lifecycle management (PLM)?"
- ISO, ISO 10007:2017, Quality management: Guidelines for configuration management, 2017.
- OpenStax, Principles of Marketing, section 9.3, "The Product Life Cycle."
- SAP, "SAP Integrated Product Development."
