Skip to main content

PLM — Product Lifecycle Management

Product Lifecycle Management (PLM) is the software category that manages a product’s technical record from concept through engineering, manufacturing, service, and retirement. Where ERP is the system of record for orders, inventory, and money, PLM is the system of record for product data: CAD models, engineering bills of materials, specifications, drawings, and change history. In discrete manufacturing the two systems are complementary — and the interface between them, above all the question of who owns the bill of materials, is one of the most consequential integration decisions a mid-market manufacturer makes.

What PLM covers

Core PLM capabilities include item and part-number management, CAD file vaulting with version control, authoring of the engineering BOM, engineering change management (change requests and change orders), document control for drawings and specifications, and compliance data such as RoHS, REACH, and conflict-minerals declarations. US mid-market manufacturers typically evaluate cloud PLM products such as Arena, Autodesk Fusion Manage, or Propel; larger engineering organizations run Siemens Teamcenter or PTC Windchill. Defense and aerospace suppliers add a further constraint: access to technical data must be controlled under US export regulations (ITAR/EAR), which shapes both hosting choices and permission models.

Who owns the bill of materials?

The standard governance answer: engineering owns the eBOM (engineering view) in PLM, and manufacturing owns the mBOM (manufacturing view) in ERP. The eBOM describes the product as designed — functional structure, reference designators, approved manufacturer lists. The mBOM restructures that content for execution: phantom assemblies, packaging materials, plant-specific alternates, and alignment with routings and work centers. A controlled release process moves data from PLM to ERP at defined change points. The anti-pattern is two editable copies with no release discipline: MRP then explodes stale structures, purchasing buys to obsolete revisions, and the shop floor builds from outdated drawings. Whatever the tooling, exactly one system must be the authoring environment for each BOM view (see Bill of Materials (BOM)).

Engineering change management

Engineering change management (ECM) is the workflow that keeps product data trustworthy over time. An engineering change request (ECR) documents a problem or improvement; an engineering change order (ECO) authorizes the change, lists affected items and documents, and carries approvals. Effectivity dates — by calendar date or serial number — define when the change takes effect, and disposition rules decide what happens to inventory on hand: use up, rework, or scrap. On ECO release, item and BOM updates propagate to ERP, and the next MRP run plans against the new structure. In regulated industries such as medical devices and aerospace, documented design and change control is a compliance requirement, which makes the PLM change history part of the audit record.

CAD integration

Direct CAD connectors are a defining PLM feature. Integrations for SolidWorks, Autodesk Inventor, Creo, or NX check files in and out of the vault, keep versions consistent, and derive item records and the eBOM structure directly from the CAD assembly tree. Neutral formats (STEP for geometry, PDF for released drawings) serve suppliers and downstream consumers. The practical value is eliminating manual re-entry of part data — historically the largest single source of BOM errors in mid-market manufacturing.

ERP-PLM interface patterns

Three patterns dominate in the US mid-market. One-way release: PLM pushes items, eBOM structures, and documents to ERP when an ECO is released; ERP owns everything downstream. This is the most common and the easiest to govern. Bidirectional sync: ERP additionally returns cost, inventory status, and where-used data to PLM so engineers see business context; more useful, but harder to keep consistent. Embedded PLM or PDM module in the ERP suite: adequate for document and revision control in less engineering-intensive businesses, but usually thin on CAD management and change workflows. Transport runs over vendor connectors, REST APIs (see REST API), or an iPaaS. Downstream, the released mBOM and routing feed execution systems (see MES).

Selection criteria for US buyers

  • BOM handoff design first: before comparing PLM features, decide where the eBOM-to-mBOM transformation happens and who performs it. This decision drives the interface scope more than any product capability.
  • Native CAD connector for your systems: verify a maintained connector exists for your exact CAD product and version cadence — connector lag after CAD upgrades is a recurring operational pain point.
  • Change-workflow fit: model one real ECO end to end in the demo, including effectivity dates and inventory disposition, rather than reviewing workflow screenshots.
  • Prebuilt ERP integration: prefer documented, supported integrations to your ERP over custom middleware; ask for reference customers running the same ERP-PLM pair.
  • Export-control and access model: if you serve defense or aerospace customers, confirm the hosting and permission model supports controlled technical data before shortlisting.

Comparable terms

PDM (product data management) is the CAD-vaulting subset of PLM; many mid-market companies start with PDM and grow into PLM. Master data management governs shared business objects across systems, of which the item master is one. MES consumes released manufacturing data on the shop floor. A digital twin extends the product record into operation with live sensor data. The broader goal behind all of them is a single source of truth for product information.

Related Topics