Product lifecycle management
What is PLM?
PLM stands for product lifecycle management. It is the system of record for what a product is made of, which version is current, and what changed — from the first sketch to the last production run.
A product is a set of decisions. PLM is where those decisions live, and where they are allowed to change.
Every company already does product lifecycle management. The question is whether it happens in one governed system or across a shared drive, six spreadsheets, and the memory of the person who has been there longest. PLM software makes the product record explicit: one place where a part number means something, a revision is frozen, and a change has an approver and a date.
Eight kinds of record.
Strip the category down and a PLM system is a small number of record types that reference each other. Everything else is a view over these.
Items and parts
Every physical thing gets its own record and a stable part number: finished goods, sub-assemblies, components, raw materials, packaging.
Bills of materials
What goes into what, level by level, with quantities and units. A multi-level BOM is the backbone of the whole system.
Revisions
A frozen copy of the item at a point in time, so that “rev C” means exactly one thing to engineering, the factory, and the auditor.
Change control
A proposal, a named set of approvers, an effectivity date, and an atomic apply. Changes land as decisions, not as edits someone made on a Tuesday.
Documents and files
Drawings, specs, artwork, test reports, compliance certificates — attached to the item they describe instead of a shared drive.
Suppliers and cost
Who makes each part, at what price, under which approval, and what the finished product costs once the BOM rolls up.
Lifecycle status
Draft, in review, active, obsolete. Status is a field the whole company can filter on, not a colour someone applied to a row.
Where-used
Every place a component appears, upward through the structure. This is the question you ask the morning a part goes end-of-life.
It is a loop, not a line.
Diagrams draw the product lifecycle left to right, which is the one thing it never does. A product reaches production and then something moves — a supplier, a cost, a regulation — and the work goes round again. Handling that return is most of what PLM is for.
-
Concept
The idea becomes a record with a number, a type, and an owner. It is thin, and that is fine.
-
Design
Specs, attributes, and structure take shape. The bill of materials appears and starts to change daily.
-
Validate
Samples, first articles, lab dips, tests. Results attach to the item, so a failure is traceable to a version.
-
Source
Suppliers quote, alternates get approved, costs roll up the structure and the margin becomes real.
-
Release
The design is frozen at a revision and handed over. From here, changing it costs money and needs a decision.
-
Produce
The released revision is what gets built, batch after batch, with lots and genealogy recorded against it.
-
Change
A part goes obsolete, a cost jumps, a test fails, a regulation moves. Something always has to change.
-
Back to 02
The change is designed, validated, costed, and released as a new revision — while the old one stays readable, because something out there was built to it.
Eventually the product retires. The record has to outlive it anyway: for warranty claims, for recalls, and for the next product that borrows half its structure.
PLM, PDM, PIM, ERP.
These overlap enough to argue about and differ enough to matter. The short version: PLM defines the product, ERP transacts it, PIM sells it, PDM stores the drawings. The bill of materials is where they meet.
| Acronym | Stands for | Owns | In practice |
|---|---|---|---|
| PDM | Product data management | CAD files and their versions | The vault under engineering. PLM grew out of PDM and kept the versioning, then added the process around it. |
| PLM | Product lifecycle management | Parts, BOMs, revisions, changes | The definitive answer to what the product is, and the governed process for changing it. |
| PIM | Product information management | Descriptions, images, channel copy | The customer-facing half: marketing attributes, translations, and assets, fed out to storefronts and marketplaces. |
| ERP | Enterprise resource planning | Orders, inventory, production, invoices | The transactional half. It plans and buys against the BOM that PLM released; it is not where the BOM is decided. |
When teams move to PLM.
Almost nobody adopts PLM because of a category. They adopt it in the week after one of these, when the cost of not having it finally arrives as an invoice or a delay.
- Two people are holding different versions of the same BOM, and both are confident.
- Nobody can say for certain which revision the factory built last season.
- A component went end-of-life, and working out what it affected took a week of opening files.
- A cost change had to be re-keyed into four spreadsheets, and one of them was missed.
- An auditor asked who approved a change and on what date, and the answer was an email thread.
- Onboarding someone means explaining a folder structure and the reason behind FINAL_v3_use_this.xlsx.
When you don't need it
If you build one product, you are the only person who edits the bill of materials, and it fits on a screen, a spreadsheet is genuinely fine. Buying PLM before that point mostly buys you a migration. The honest trigger is a second editor, an outside party who has to trust your revision, or a change you cannot reconstruct six months later.
PLM that bends to your product.
Most PLM systems ship with a fixed idea of what a product is, shaped around the industry they grew up in — usually electronics or mechanical assemblies. ManyRows makes the model yours: you define the types and the fields, then get the PLM machinery — multi-level BOMs, revisions, change requests with named approvers, where-used, costing — over whatever you defined. It matters most when your product is a garment, a formula, or several different kinds of thing at once.
Compared with the incumbents
Questions
- What does PLM stand for?
- Product lifecycle management. It refers both to the practice of managing a product from concept to retirement, and to the software used to do it.
- What is PLM software?
- A system of record for product data. It holds items and part numbers, multi-level bills of materials, revisions, documents, suppliers and costs, and it governs how any of that changes through a change-control process with named approvers and an audit trail.
- What is the difference between PLM and ERP?
- PLM defines the product; ERP transacts it. PLM is where the bill of materials is decided, revised, and released. ERP is where that released BOM is used to buy materials, plan production, and manage inventory. Most companies run both, with the BOM as the handover point.
- What is the difference between PLM and PIM?
- PLM manages the internal truth of a product — structure, revisions, suppliers, changes. PIM manages the outward description of it — marketing copy, images, and channel-specific attributes for storefronts and marketplaces. PLM feeds PIM, not the other way around.
- Is PLM only for manufacturing?
- No. The mechanics of a bill of materials, a revision, and a change request apply anywhere a product is composed of other things. Apparel, food and beverage, cosmetics, and cannabis all run on PLM, though the vocabulary changes: a formula instead of an assembly, a size spec instead of a tolerance, a season instead of a model year.
- Do small teams need PLM?
- Not always. One product, one editor, and a BOM that fits on a screen is a spreadsheet problem. The move usually happens at the point where a second person edits the same data, or where someone outside the team has to trust which version is current.
- What is a bill of materials?
- A structured list of everything that goes into a product, with quantities and units. Multi-level means the list contains sub-assemblies that have their own lists, so a finished product explodes down through its assemblies to raw materials, and costs and quantities roll back up.
- How much does PLM software cost?
- Traditional PLM is sold on a quote, and the licence is usually the smaller half of the number once implementation, configuration, and training are included. Newer tools publish per-seat pricing you can read without a call — ManyRows lists its plans on the pricing page.