Beyond the Engineering BOM: Building Data Confidence with Windchill MPMLink

An engineering BOM can be accurate, approved and fully managed in PLM, yet still leave manufacturing engineers with questions. How should components be organized for assembly? Which additional parts are needed? And does the structure represent the product configuration they are actually preparing to build?
These questions become more difficult as products grow in complexity. In aerospace, defense, automotive and industrial equipment manufacturing, engineering teams often manage multiple configurations, intricate assemblies and product information developed over many years. Moving from an approved design to a manufacturing-ready definition is an important part of the product development process and requires more than sharing the engineering BOM with manufacturing teams.
This is where PTC Windchill MPMLink comes into play. It connects engineering and manufacturing product definitions within Windchill, helping teams work with different views of the same product while maintaining the relationships between them.
In practice, “data confidence” here comes down to three things:
- manufacturing engineers can see which engineering part each manufacturing part comes from,
- they can see when the engineering side has changed,
- and they know which product configuration they are working on.
Why the Engineering Bill of Materials isn’t always enough
An engineering BOM (EBOM) is typically developed by Engineering and R&D teams during product design. Often connected to CAD drawings and models and managed within a Product Lifecycle Management (PLM) system, it organizes the components required to build a product, including custom-designed and standard parts. Part numbers, descriptions, quantities and parent-child relationships define how individual components fit into assemblies and subassemblies.
Consistent part numbering and accurate component data make it easier for teams to identify and reuse the correct information. PLM-based version control, together with established change management processes, helps keep the EBOM aligned with the approved product definition as designs evolve.
Why BOM structure matters beyond engineering
A manufacturing bill of materials (MBOM) organizes product information according to how the product will be manufactured or assembled. From an engineering perspective, the product structure reflects design intent; manufacturing teams need a structure that supports assembly planning and execution.
Consider a manufacturer developing complex industrial machinery. An engineering assembly may contain mechanical, electrical and control components grouped according to their functions. During manufacturing planning, those components may need to be reorganized into assembly groups, with additional manufacturing-specific items included where necessary.
Typical differences are very practical. The manufacturing engineer often adds structure that does not exist in the EBOM at all, for example a phantom manufacturing part inserted into the MBOM, with the relevant components linked under it so they can be assembled together as one group. Items such as paint, grease or packaging may also be missing from the EBOM entirely, yet the MBOM has to include them. In the Manufacturing view, a manufacturing part can also use the “Made From” functionality, which links it to additional parts, such as raw material and semi-finished parts.
In Windchill this separation is reflected in views. The engineering structure is built in the Design view and the manufacturing structure in the Manufacturing view. A manufacturing part is a separate object with its own lifecycle and versions, linked to its engineering counterpart, so manufacturing engineers can work on it without touching the released engineering definition.
Neither structure is incorrect. They simply serve different purposes.
The challenge is maintaining a clear relationship between them. When an MBOM is created independently, manufacturing engineers may need to compare structures manually, verify component relationships or consult Engineering to confirm the relevant product definition. These activities become harder to manage across complex assemblies and multiple product configurations.
The aim is not to make the EBOM and MBOM identical. It is to ensure that both represent the intended product and that the relationship between them can be understood and managed.
Connecting the Engineering and Manufacturing BOM with Windchill MPMLink
Windchill MPMLink supports EBOM to MBOM transformation through its BOM Transformer. Manufacturing engineers can use the engineering product structure as a starting point, reorganize components to reflect manufacturing requirements and maintain associations between corresponding engineering and manufacturing objects.
One of the mechanisms behind this is the use of equivalent links. These connect related upstream engineering and downstream manufacturing parts, helping engineers understand how the two structures correspond, even when their organization differs. The links are created when parts or assemblies are copied or dragged from the engineering structure into the manufacturing structure in the BOM Transformer. The item that appears in the manufacturing structure is a downstream part that stays linked to its engineering original.
Effective BOM Management through controlled EBOM–MBOM relationships
The BOM Transformer also supports comparing and reconciling related structures. Instead of relying on product structures maintained independently across multiple software systems, engineering and manufacturing teams can manage related definitions within Windchill, with controlled associations between them.
This matters most when Engineering changes the EBOM after the MBOM has been created. The BOM Transformer can detect discrepancies between related upstream and downstream parts and show their status, so manufacturing engineers do not have to find the differences manually. They then review each difference and decide how to resolve it: update the downstream usage quantity and attributes from the engineering structure, or bring in a new part. The engineering change itself is still managed through the usual Windchill change process – the BOM Transformer shows what it means for the manufacturing structure.
Example: an EBOM gearbox assembly contains a housing, a shaft, two bearings and fasteners. In the MBOM the manufacturing engineer inserts a phantom “shaft group” containing the shaft and the bearings, and adds grease and packaging. Later, Engineering raises the bearing quantity from two to four. The BOM Transformer flags the bearings as different from their upstream originals, and the manufacturing engineer updates the downstream quantity. The phantom group and the added grease are not affected.
This becomes particularly useful when a product contains many assemblies or when the manufacturing structure differs significantly from the engineering view. Engineers need to know which relationships are intentional, which components are represented in each structure and whether the manufacturing definition is appropriate for the work being planned.
MPMLink also supports manufacturing process planning. Its Process Plan Browser allows engineers to define operations and associate them with relevant parts and manufacturing resources (for example tooling, fixtures and equipment). Standard procedures can be reused across process plans, so engineers do not have to describe every operation from scratch. In this way, product structures and process information can be managed as related elements of the manufacturing definition.
The manufacturing BOM can also provide structured product information for downstream materials management processes. MPMLink, however, does not replace ERP or inventory management systems; its role is to manage manufacturing product definitions and associated process information within PLM.
Plant differences are another reason for a separate manufacturing structure. The same product is rarely built the same way in every plant, so MPMLink supports alternate BOMs: several manufacturing BOMs for the same manufacturing part, for example for different plants, BOM types such as production and service, or production methods. Process plans can also be defined per plant. The manufacturing definition is then transferred to ERP through integration, typically Windchill ESI or the ERP Connector, which can send plant-specific manufacturing BOMs.
These capabilities do not remove the need for engineering decisions. MPMLink does not automatically determine the best assembly approach or create a complete manufacturing process simply from an EBOM. Manufacturing engineers still define operations, select resources and account for practical constraints. What MPMLink provides is a controlled environment for managing those decisions alongside the product information on which they depend.
Managing multi-level BOMs across product configurations
The value of connected engineering and manufacturing structures becomes clearer when products have multiple configurations.
An approved part or assembly is not necessarily applicable to every product variant. Manufacturing engineers need to work with the correct configuration, not simply the latest released structure. In multi-level BOMs, this means understanding which assemblies, subassemblies and components apply to a particular product configuration. Using an incorrect configuration or incomplete manufacturing structure can lead to costly errors and production delays, particularly when discrepancies are discovered after manufacturing preparation has begun.
In Windchill, a BOM is generated from the product structure using a configuration specification, so the same EBOM can give different results depending on the filter applied. Depending on the process, that can be the latest released versions, a baseline, or an effectivity defined by date, lot or serial number. Where products have optional or variant content, options and variants allow one structure to describe many configurations.
This has different implications across industries. Aerospace manufacturers may need to prepare manufacturing definitions for specific aircraft or equipment configurations, with strict traceability requirements. Defense programs often involve controlled product baselines and program-specific configurations. Automotive manufacturers work with extensive variant combinations, while industrial equipment companies frequently adapt standard designs for individual customers.
In each case, manufacturing planning depends on understanding which engineering definition applies to the product being built.
Windchill provides configuration management capabilities, while MPMLink keeps the manufacturing structures and process information built on those configurations in the same environment, linked to the engineering definitions they come from. The result is a more consistent way to maintain the connection between product design, manufacturing structures and the applicable configuration.
Of course, that connection depends on how the PLM environment is implemented. Product structures must be modeled consistently, and configuration rules need to reflect actual engineering and manufacturing requirements.
Improving BOM Management processes in your existing Windchill environment
For manufacturers already using Windchill, introducing or extending MPMLink does not necessarily mean rebuilding their PLM environment. MPMLink is a separate module, however, so it still needs to be planned as a project: licensing, the Design/Manufacturing view model, and what to do with manufacturing structures that currently live outside Windchill.
A useful starting point is to examine how an existing engineering structure is used during manufacturing planning. Where do engineers need to reorganize components? Which manufacturing-specific items are added? How are relationships between the EBOM and MBOM maintained, and how do teams identify the correct product configuration?
Looking at a representative assembly can reveal whether the main challenge lies in the available data, the way product structures are modeled or the manufacturing process management capabilities currently in use. It can also expose gaps in component attributes, supplier information or the way externally sourced parts are represented in the product structure.
Some organizations may need to improve the consistency of their engineering data before extending it into manufacturing planning. Others may already have a solid PLM foundation but lack an effective way to develop manufacturing BOMs and related process plans within Windchill.
At Transition Technologies PSC, we help organizations develop and extend PTC Windchill environments, working across PLM data management, system integration and manufacturing process management. Our focus is on connecting the technical capabilities of the platform with the engineering processes they need to support.
For companies managing complex products, Windchill MPMLink offers a way to build on existing PLM investments and make engineering information more useful for manufacturing planning, without losing control of the underlying product definition.
