What Is PLM-ERP Integration? Definition and How It Works

Q: Should PLM or ERP be the system of record for the BOM?

PLM should be the system of record for the Engineering BOM (EBOM) . The Manufacturing BOM (MBOM) is typically authored in PLM with Windchill MPMLink and released to ERP, though some companies still build and keep it in ERP. ERP stays the system of record for cost and planning data. The integration layer transfers data between them at defined trigger events.

What Is PLM-ERP Integration?

PLM-ERP integration is the connection that sends part masters, bills of materials (BOMs) and approved engineering changes from a Product Lifecycle Management (PLM) system such as PTC Windchill into an Enterprise Resource Planning (ERP) system such as SAP, Oracle or Microsoft Dynamics 365, and sends cost, supplier and lead-time data back. It is software plus agreed rules about which system owns which data, so manufacturing and purchasing build and buy from the same parts and BOMs engineering released, without anyone re-keying them.

Key Fact	Detail
Data flows from	PLM → ERP (primary direction) and ERP → PLM (feedback)
Triggered by	BOM release, engineering change approval, part creation
Most common PLM	PTC Windchill, Siemens Teamcenter, Dassault ENOVIA
Most common ERP	SAP S/4HANA, Oracle Cloud, Microsoft Dynamics 365
Integration methods	Native connectors, middleware (MuleSoft, Boomi), custom API
Without integration	Manual data re-entry, BOM errors, change latency

What happens without PLM-ERP integration?

Without integration, engineers in PLM approve a BOM change, then someone manually re-enters it into ERP. This creates:

Lag time — Changes take days or weeks to reach production

Transcription errors — Manual re-entry introduces mistakes

Version mismatches — ERP may be running an older BOM revision than engineering intended

Compliance exposure — No automated audit trail of what changed, when, and why

With integration, an approved BOM change goes from PLM to ERP on a defined trigger, with a record of what changed, when and why.

What Data PLM-ERP Integration Transfers

Data Object	Direction	Description
Part master	PLM → ERP	Part number, description, UOM, source (make/buy), classification
Engineering BOM	PLM → ERP	Assembly structure, quantities, revision level
Manufacturing BOM	PLM ↔ ERP	Assembly with routing info; may originate in PLM (MPMLink) or ERP
Engineering Change	PLM → ERP	ECO metadata, affected parts, effectivity date
Document links	PLM → ERP	Drawing references, specs attached to part/BOM records
Cost data	ERP → PLM	Standard cost for parts used in PLM analytics
Procurement status	ERP → PLM	Approved supplier list, lead times for design decisions

PLM-ERP Integration Methods

1. Native Connectors
PTC provides a Windchill Connector for SAP that handles BOM and part master transfer natively. Similarly, Siemens has Teamcenter connectors for SAP. These are the lowest-risk option for supported ERP/PLM combinations.

2. Middleware Integration Platforms
Tools like MuleSoft, Dell Boomi, TIBCO, or Microsoft Azure Integration Services sit between PLM and ERP, orchestrating data flows with transformation logic. Best when you have multiple systems or need complex routing/transformation.

3. Custom API Integration
Both Windchill and modern ERPs expose REST APIs. Custom integrations built on these APIs offer maximum flexibility but require ongoing maintenance and deep technical expertise.

4. iPaaS (Integration Platform as a Service)
Cloud-native integration platforms purpose-built for manufacturing (e.g., Senseforce, Plex MES integrations) are emerging as a lower-cost middleware option for mid-market manufacturers.

Common PLM-ERP Integration Challenges

Challenge	Why It Happens	How to Solve It
Part number mismatches	PLM and ERP use different numbering schemes	Establish a master part number governance policy before integration
BOM structure differences	EBOM (engineering) ≠ MBOM (manufacturing) in structure	Define transformation rules in integration layer
Change effectivity handling	“When does this change take effect in production?” is complex	Implement date-based and serial-number-based effectivity in integration logic
Large BOM performance	Thousands of BOM lines overwhelm synchronous transfers	Use async batch processing with delta-change logic
Bidirectional conflict	Both systems claim to be the master	Establish clear ownership rules: PLM owns parts, the EBOM and (with MPMLink) the MBOM; ERP owns cost and planning data

Frequently asked questions

What is the difference between PLM-ERP and ERP-MES integration?
PLM-ERP integration connects design data (engineering) to planning and procurement data. ERP-MES integration connects planning data to shop floor execution. A complete digital thread typically requires both integrations.

How long does a PLM-ERP integration project take?
A standard Windchill-to-SAP integration using PTC’s native connector typically takes 4–9 months, depending on data complexity, custom fields, and change management requirements. Oracle, Dynamics 365 and Infor integrations run through middleware and fall in about the same 4–9 month range.

What is the Windchill Connector for SAP?
PTC’s Windchill Connector for SAP is a pre-built integration solution that automates the transfer of part masters and BOMs from Windchill to SAP. It supports both ECC and S/4HANA and handles BOM change notifications with configurable effectivity logic.

Should PLM or ERP be the system of record for the BOM?
PLM should be the system of record for the Engineering BOM (EBOM). The Manufacturing BOM (MBOM) is typically authored in PLM with Windchill MPMLink and released to ERP, though some companies still build and keep it in ERP. ERP stays the system of record for cost and planning data. The integration layer transfers data between them at defined trigger events.

What Is PLM-ERP Integration? How Engineering and Manufacturing Connect