How to Implement Windchill MPMLink: A Practical Guide

Most MPMLink projects I’ve seen go wrong did not go wrong in the software. They went wrong in a meeting nobody held: the one where engineering, manufacturing and the ERP owner agree on who owns the manufacturing BOM, how the plants differ, and what happens to the spreadsheets the floor builds from today. This guide is the order we work in when we stand MPMLink up for a client, with the decisions you have to make at each step and the traps we see most.

If you need the basics first, start with what Windchill MPMLink is and the difference between an eBOM and an mBOM. This page assumes you already run Windchill PDMLink and are deciding how to put MPMLink on top of it.

Talk to a consultant →

Key facts


What MPMLink adds	A manufacturing BOM linked to the engineering BOM, process plans with operations, manufacturing resources, and work instructions, all inside Windchill.
The data chain	CAD → eBOM (PDMLink) → mBOM (BOM Transformer) → process plans → resources allocated to operations → work instructions → ERP and MES.
Hard prerequisite	A released, trusted eBOM. MPMLink can only be as accurate as the structure it transforms.
The first design decision	Which system masters each piece of manufacturing data: Windchill, ERP or MES.
What keeps eBOM and mBOM in step	Equivalent links between part iterations, read through out-of-date and discrepancy indicators. Views and part numbers alone are not enough.
Recommended order	Views and BOM transformation, then change on manufacturing objects, then resources and process plans, then ERP/MES publishing.
How to roll it out	One pilot product line, rehearsed in conference room pilots with real data, before more product lines or plants.
Where it usually stalls	Process-plan and routing migration, messy work-center master data, and manufacturing engineers who were never brought into the design.

Step 1: Decide what Windchill will own

Before anyone opens the BOM Transformer, write down which system masters each kind of manufacturing data. This is the decision every later step depends on, and it is the one most often left implicit.

A typical split looks like this:

Data	Usually mastered in	Notes
Engineering BOM	Windchill (PDMLink)	Released by engineering change.
Manufacturing BOM	Windchill (MPMLink)	Published to ERP. ERP should not edit it.
Process plans and operations	Windchill (MPMLink)	Published to ERP as routings.
Work instructions	Windchill or MES	Decide per plant. This choice shapes the MES integration.
Work centers, tooling, skills	Defined in both	Must exist in ERP before Windchill can publish a routing that uses them.
Cost, inventory, scheduling, orders	ERP	Windchill does not hold production-order BOMs.
As-built execution data	MES	Feeds back to quality, not to the mBOM.

On a defense MPMLink program we delivered, one of the first artifacts was a decision matrix for what manufacturing data lives in Windchill and what lives in MES. Once it existed, a disputed requirement could be checked against it instead of argued from scratch.

The other scoping questions to answer here come from the MPMLink area of our discovery template:

Will manufacturing standards (standard operations, resource libraries) be global, or will each plant keep its own?
How many plants build this product, and do they build it differently?
Is there a master BOM, or a BOM per plant?
Which resource types (work centers, tooling, skills, process materials) do you need to track, and with what attributes?
Do you need alternate units of measure in the plan structure?
Will effectivity be published to ERP?

Step 2: Check the prerequisites

MPMLink transforms what PDMLink gives it. If the engineering side is not settled, the manufacturing side inherits every problem, twice.

eBOM maturity. Pick the pilot product and look at its released eBOM honestly. Is it complete? Does it match what engineering would sign? Are phantom assemblies used consistently? If the floor already distrusts this BOM, fix it in PDMLink before you transform it. Windchill creates a design BOM by default; it does not create a manufacturing BOM until someone runs the BOM Transformer, so there is no mBOM to clean up yet, and that’s an advantage.

Part numbering and revisions. Decide whether manufacturing parts get their own numbers or share engineering numbers, and how manufacturing revisions relate to engineering ones. Set object initialization rules so new numbers fit the field lengths your ERP accepts, or publishing will fail later. (Our notes on parts classification cover the numbering side.)

Change process. Decide how changes to manufacturing objects will be controlled. Without change management on the manufacturing side, use at least a formal promotion process.

Mobilization readiness. At the end of mobilization, confirm:

The MPMLink license is active and an environment with the BOM Transformer is ready.
Administrator access to Windchill is verified.
Team members have the PDMLink and BOM Transformation license profiles and access to the right products and libraries.
The discovery questionnaires are complete.
Time is booked for configuration workshops, testing and training.
Subject-matter experts for the pilot product are named and available.

Step 3: Design the view hierarchy

Views are how Windchill holds an engineering and a manufacturing version of the same part. The hierarchy is ordered, for example Design → Manufacturing → Plant A, Plant B. One rule governs everything: items in a parent view can be used in descendant views, never the reverse. Resources and parts must not sit in a lower view than the process plan or operation that uses them.

Three ways to hold more than one structure, and when to use each:

Mechanism	Use it for	Example
View	A different discipline or plant	Design vs. Manufacturing vs. Plant A
BOM category	A different purpose in the same view and plant	A costing BOM frozen once a year
Alternate BOM	A different production version in the same view	An alternate process at another work center, or a subcontract route

A Manufacturing view, and each alternate BOM, must be associated with at least one plant. If your plants build the same product the same way, you may not need plant views at all, and fewer views means less to maintain. If they build differently, plant views keep the differences visible instead of buried in spreadsheets.

Step 4: Transform the eBOM into the mBOM

In the BOM Transformer the engineer sees the eBOM on the left (upstream) and the mBOM on the right (downstream) and restructures one into the other. The common moves are: assemble as is, create a new part or branch, split a design structure, merge several engineering parts into one manufacturing part, quantity split, add a manufacturing-only assembly (a kit for one station, say), and add manufacturing-only items such as adhesives and grease without touching the signed design.

Why equivalent links carry the traceability. The view mechanism ties eBOM and mBOM together through the part number and revision scheme. That breaks as soon as manufacturing splits an assembly, renumbers a part, or needs to know which design iteration was planned. MPMLink’s equivalent links relate an upstream part iteration to its downstream equivalent directly. That is what keeps every mBOM line traceable to its design part, even after a split or a renumber.

Manual or automated. For a large structure, Generate Downstream Structure builds the first mBOM from rules you define (transform option, target type, attribute mapping). Run it once per selected assembly, and expect to tailor the rules: it saves the first pass, and someone still has to model the result against how the line actually builds. On the defense program, configuring the BOM Transformer to automate eBOM-to-mBOM conversion removed the manual re-keying that had been producing errors between the two BOMs.

Practices we follow:

Prefer Assemble As Is over creating a new view version. Links stay easier to keep in sync, and the floor reads the design version.
Never create a new view version outside the BOM Transformer. It creates no equivalent links, and the traceability is gone.
Give manufacturing-only upper-structure items their own part type or attribute. They need no eBOM equivalent, and the type can drive automated transformation rules.
Decide your options and variants strategy here, if you configure products. It changes how the mBOM is generated.

For very large assemblies, tune for performance early: hide BOM Transformer tabs and table columns you don’t use, load 3D on demand, and limit structure expansion. Planners judge MPMLink early, and partly by how fast it opens their biggest product.

Step 5: Set up plants, resources and standards

Process plans need somewhere to run and something to run with. In MPMLink that is the resource model: plants, work centers, tooling, skills, process materials and resource groups, managed in the Manufacturing Resource Browser.

Plant data. Plant-specific part data is driven by a set of preferences, and the order you set them in matters. Get it wrong and departments end up inconsistent, which then breaks publishing to ERP. Treat plant data set-up as a configuration item with its own test, not a click-through.

Work-center master data. This is where ERP and Windchill meet first. Work centers and skills must already exist in ERP before Windchill can publish a routing that references them, and names and numbers must match. If the ERP work-center list is messy (duplicates, retired centers still active, plants using different names for the same cell) clean it before you model resources in Windchill.

Compatibility rules. You can mark resources as mandatory, preferred, acceptable or forbidden for an operation. Treat these as allocation shortcuts. They check one level at a time and only when someone assigns a resource, not afterwards, so they are not a validation layer.

New tooling and fixtures. If your manufacturing engineers design tooling, decide the flow now. Ours has four steps: define the build strategy, raise a resource request, review it, release the resource. The tooling CAD then links back to the resource.

Standards. Standard operations, standard procedures and capabilities are what make the second product line faster than the first. Decide whether they are global or per plant (that was a Step 1 question), and who may change them.

Step 6: Build process plans and operations

A process plan is the sequence of operations that builds a part, with each operation tied to the parts it consumes, the work center where it runs, and the tooling, skills and materials it needs. Planners author them in the Process Plan Browser.

The rules that trip people up:

A process plan cannot contain another process plan. Use sequences and operations.
Tooling and process materials are not in the BOM. Allocate them to operations.
Raw material goes in the BOM and is allocated to the operation as “operated on”.
A phantom assembly cannot be allocated to an operation; the parts under it can.
Duplicating a process plan or operation drops its part allocations. Copying an existing operation or a standard operation keeps its resources, time and documents.
Keep a process plan in the same container as its part, and in its own folder, so access control can treat planners and engineers differently.

Study plans and production plans. We create study plans in the global manufacturing view while engineering is still designing, and production plans in the plant view once the plant is chosen. Study plans are how manufacturing gets in early: the defense client moved from planning after engineering finished to planning alongside it, and manufacturing started catching producibility issues during design.

Reuse before you author. Check for an existing plan, standard operation or capability first. A library of standard operations built on the pilot is worth more than any single plan.

Step 7: Write work instructions

Work instructions in MPMLink live on the operations of the process plan. Each operation can carry its consumed parts, resources, documents and illustrations. If you use Creo Illustrate, its output becomes a reference document on the operation. Standard operations let a proven instruction be reused across plans and products.

Decide three things before anyone writes the first instruction:

Where instructions are mastered. Windchill or MES. If MES renders them to the operator, decide whether Windchill sends the content or MES owns it. This is the most expensive decision to reverse.
The work-instruction standard. What every operation must contain: the steps, the parts and quantities, tooling, torque or other critical characteristics, safety notes, quality checks, and the visuals. Write it as a template and enforce it in review.
Who reviews them. Engineering, manufacturing and quality should all see the instruction before it reaches the floor. That review is where most of the value of MPMLink shows up, because errors get caught before the build instead of on it.

Step 8: Propagate engineering changes downstream

This is the part that pays for MPMLink. When engineering revises a part upstream, the equivalent link to the mBOM shows as out of date. Manufacturing engineers then detect the discrepancies, review them, and propagate the change downstream, or decide it does not apply to their structure.

Read the status indicators carefully:

Out of date means the upstream item changed. On its own it does not prove a discrepancy.
Usage exists but the link is broken means the item moved to another assembly upstream.
Missing equivalent occurrence means a part is not consumed downstream.

Two working rules. Use Revise with Current Link when you revise a downstream part and want to keep its equivalent link; it works one item at a time. And after a plain revise, run detect discrepancies and propagate before you consider the mBOM current.

Tie this to your engineering change process. The change notice that releases the eBOM change should be the trigger for manufacturing’s impact review, so the floor never builds to an old revision by mistake. Test the propagation with real changes during CRP; on the defense program we wrote test cases for the BOM revision flow and verified that engineering changes reached the manufacturing plans before production.

Step 9: Publish the mBOM and process data to ERP and MES

Windchill publishes both the data (parts and BOMs) and the flows (process plans as routings), so one system does not end up mastering the same data twice. For SAP and Oracle, PTC’s Enterprise Systems Integration (ESI) is the out-of-the-box route, with closed-loop status coming back from ERP. Typical mapping:

Windchill	ERP
Part	Material / item
mBOM	BOM
Change notice	Change master
Process plan	Routing
Sequence / operation	Sequence / operation
Tooling, process material	Tooling, process material (or the ERP’s resource equivalent)
Work instruction	Document

What to settle before you build it:

Order. Manage the mBOM and change on manufacturing objects in Windchill first, then integrate. Process plans before the integration are optional; a stable mBOM is not.
Trigger. Publish on release of a change notice, so ERP receives a controlled package and a revision it can match.
Revision control. Agree how revisions in Windchill map to ERP and test every edge case. On the defense program, keeping a single revision control across PLM and ERP needed explicit business rules and a full set of test scenarios.
Permissions. The people and change administrators who trigger publishing must be in the right ESI groups, or releases silently fail to go.
Failure handling. Decide who gets the correction task when a publish fails and how they see it. Publish status is not visible to most users out of the box.
MES. PTC’s ERP Connector and Integration for MES deliver XML or JSON to files or MES targets without third-party middleware, and are one-way unless customized for status return.

Our ERP-PLM integration guide and the Windchill–SAP integration page go deeper on this step.

Step 10: Migrate existing routings and work instructions

Most manufacturers arrive with routings in ERP, process sheets in Excel, and work instructions in Word or a legacy system. Decide per product line which of three things happens to each:

Load it. Active, well-structured routings for the pilot product line, mapped to MPMLink operations and resources.
Rebuild it. Plans that need restructuring anyway, or that were never consistent across plants. Rebuilding on the new standard often costs less than mapping a mess.
Leave it. Obsolete or end-of-life product data stays in the old system, read-only, for reference.

Profile the source data before you price or plan the load, because the mapping work depends on how consistent it is. Rehearse the load on a full copy before testing, the same as any Windchill migration. And if existing mBOMs and routings are out of scope, as they were on the defense program, plan the interim workflow that keeps legacy and new aligned during the transition. Someone has to own that gap.

Step 11: Pilot one product line, then expand

Start with one product line in one plant. Pick one that changes often enough to exercise change propagation, is complex enough to need real transformation rules, and has a manufacturing engineer who wants it to work. Avoid the hardest product in the building and the trivial one.

What the pilot should leave behind: transformation rules that worked, a first library of standard operations and resources, a work-instruction template the floor accepted, a tested publish to ERP, and a small group of manufacturing engineers who can show the next team. Then add product lines, then plants.

Early wins matter more here than in most PLM work. Manufacturing engineers who have planned in Excel for years are rightly skeptical, and on the defense program we focused on quick pilot results to earn credibility before the wider rollout. Our organizational change management approach covers the rest of adoption.

Step 12: Rehearse it: conference room pilots and testing

Run conference room pilots (CRP) with real scenarios on real data. Let the client’s planners do the work: transform a real eBOM, author a plan, push an engineering change through, publish to a test ERP. A demo in which the consultant drives is not a pilot.

Log every finding and sort it: fix now, fix later, or accept. Most projects run more than one round. After CRP comes system integration testing, then user acceptance testing on production-like data, with the migration rehearsed on a full copy before the final load. The test cases that catch the expensive problems are the ones that cross boundaries: an engineering change that has to reach a released routing in ERP, a split assembly that must stay traceable, a resource that does not exist in ERP yet.

The common traps

Starting from a BOM nobody trusts. MPMLink will faithfully transform a wrong eBOM into a wrong mBOM.
Both systems editing the mBOM. If ERP users can change the BOM Windchill publishes, the two drift apart.
New view versions made outside the BOM Transformer. No equivalent links, so no traceability and no change alerts.
Treating “out of date” as “wrong”. It means upstream changed. Detect and review discrepancies before acting.
Work-center data cleaned too late. Publishing fails on resources ERP doesn’t recognize.
Plant data preferences set in the wrong order. Departments come out inconsistent and ERP publishing breaks.
Work-instruction ownership decided after the integration is built. Changing it means rebuilding the MES side.
Manufacturing engineers left out of design. They are the users. If the transformation rules don’t match how the plant builds, they’ll go back to Excel.
A demo-and-reconfigure loop. Agree acceptance criteria before configuration ends, or every demo becomes a new requirement.
No owner for the legacy gap. If old routings aren’t migrated, someone has to keep them aligned until they retire.

Who does this work

We do. Element Consulting implements, migrates and rescues Windchill MPMLink for aerospace and defense, federal, medical device, automotive and industrial manufacturers, across 100+ PLM implementations since 2003. Several of our consultants are PTC Certified Windchill Implementation Practitioners. Our order is the one on this page: process and data decisions first, configuration second, adoption throughout.

If you are comparing firms, use our guide on how to choose an MPMLink implementation partner on everyone, including us.

Read the case study: MPMLink for a major defense contractor →

FAQ

Who can help us implement Windchill MPMLink?
Element Consulting implements, migrates and rescues Windchill MPMLink, including eBOM-to-mBOM transformation rules, plant and resource data, process plans, work instructions and the publish to ERP and MES. For a major defense contractor we set up the BOM Transformer for eBOM-to-mBOM, built process plans alongside engineering, and kept one revision control across PLM and ERP. Several of our consultants are PTC Certified Windchill Implementation Practitioners.

What has to be in place before an MPMLink implementation starts?
A released, trustworthy eBOM in PDMLink for at least one product line; settled part numbering and revision rules; a decision on the view hierarchy (Design, Manufacturing, and one view per plant if plants build differently); an active MPMLink license with the BOM Transformer available; and named manufacturing engineers who can spend time in workshops. If the eBOM is not trusted yet, fix that first.

Should the mBOM and routings live in Windchill or in ERP?
Pick one master per data domain and write it down. In an MPMLink implementation the usual split is that Windchill masters the mBOM, process plans and work instructions and publishes them, and ERP masters cost, inventory, scheduling and orders. Work centers and other resources must already exist in ERP before Windchill can publish a routing that uses them. If both systems can edit the same BOM, they will drift.

How do we build manufacturing work instructions in MPMLink?
Author them on the operations of a process plan in the Process Plan Browser: each operation carries its consumed parts, resources, documents and illustrations, and standard operations let you reuse proven steps. Agree a work-instruction standard and decide whether instructions are mastered in Windchill or in MES before anyone writes the first one, because that decision sets the integration design.

How does MPMLink handle engineering changes to the eBOM?
The mBOM is linked to the eBOM by equivalent links, not by part number alone. When engineering changes an upstream part, the link shows as out of date, and manufacturing engineers detect the discrepancies, review them and propagate the change downstream. Pair this with a change process on manufacturing objects; without change management, use at least a formal promotion process.

Should we migrate our existing routings and work instructions into MPMLink?
Migrate selectively. Load active routings for the pilot product line, rebuild the ones that need restructuring anyway, and leave obsolete ones in the old system for reference. Decide this per product line before go-live; if existing mBOMs and routings are left out of scope, plan the interim workflow that keeps the old and new systems aligned.

How to Implement Windchill MPMLink: eBOM to mBOM, Process Plans and Work Instructions