What is Manufacturing Process Planning?

What is Manufacturing Process Planning?

Manufacturing process planning is the translation step between what engineering designed and what the factory builds. Engineering hands over a product definition: the engineering BOM, the models, the drawings, the tolerances. None of that says which operation comes first, which machine does it, what fixture holds the part, what the operator checks before moving it on. Process planning decides all of that, and it writes the answer down as two artifacts: the manufacturing BOM and the routing.

It is owned by manufacturing engineering, it sits between PLM and the shop floor, and it is the step most enterprise PLM programs never quite reach. I have written about the EBOM-to-MBOM gap at length, and about why MES exists in that gap. This page is the explainer that ties them together, because "process planning" is the name of the thing that lives there.

Inputs and outputs

Inputs from engineering (PLM)	Process planning decides	Outputs to production (ERP, MES)
Engineering BOM, grouped by function	Assembly sequence and regrouping	Manufacturing BOM, grouped by work center and sequence
3D models, drawings, tolerances	Operation sequence, work center per operation	Routing with standard times
Material and finish specifications	Tooling, fixtures, gauges, setup	Tool and fixture lists
Approved engineering changes with effectivity	Where each change lands in the plan	Revised MBOM and routing, versioned
Quality requirements	Inspection points and methods	Control plan, work instructions

The regrouping in the first row is the part people underestimate. The EBOM lists a pump's motor, impeller, housing and seals the way the designer thinks about them. The MBOM lists them the way the line consumes them: a housing sub-assembly kitted at station two, seals installed at station five, a phantom assembly that never exists as a stocked item but describes what is built together. These are different documents with different parents and different owners, not two views of the same data. The EBOM vs MBOM article makes that case in detail.

Process planning is not CAM, and it is not scheduling

Three disciplines get collapsed into one word in vendor decks, and it is worth pulling them apart.

Process planning decides how a part is made across the whole factory: which operations, in which order, on which machines, with which inspections. It is largely stable across production runs.

CAM programs one of those operations on one machine. It takes the CAD geometry and produces toolpaths and G-code for a milling operation the routing has already placed at work center 14. CAM is downstream of process planning and consumes its decisions. The Best CAM Software 2026 guide evaluates that layer; the SWARF framework in it starts from the assumption that the routing already exists.

Scheduling decides when. Which work order runs on which machine on which day, given capacity and material availability. ERP and advanced planning tools schedule against the routing. Scheduling changes hourly; the routing changes when engineering or manufacturing engineering says so.

A plan without a schedule leaves parts waiting on the floor. A schedule without a good plan produces rework. CAM without a plan produces a beautiful toolpath for an operation nobody sequenced.

Where it lives: between PLM and MES

The clean architecture models three BOMs and the two translations between them. PLM hosts the EBOM, modified only through engineering change. Manufacturing engineering translates EBOM to MBOM and routing, which is process planning. ERP consumes the MBOM for procurement, cost rollup and work orders. MES executes the routing operation by operation, capturing the as-built configuration of every unit as it goes.

Neither PLM nor ERP knows the shop-floor sequence. PLM stops at design intent. ERP stops at the work order. That is the architectural reason MES is a separate system rather than a PLM feature or an ERP module, and it is why process planning is the hinge: strip out the routing and MES has nothing to execute.

In mature organizations the plan is authored in the manufacturing process management module of the PLM system (Teamcenter Manufacturing, Windchill MPMLink, DELMIA and their peers) so it stays linked to the engineering definition it derives from. The lineage of those modules is worth knowing. CIMLINC in San Diego bridged CAD/CAM systems to shop-floor execution in the 1980s, that work flowed through Tecnomatix into Siemens with the UGS acquisition, and "MP3", manufacturing process planning, became the digital factory strand of PLM. The Silicon to Systems history covers how the West Coast extended PLM from the product to the process that makes it.

What goes wrong

The failure is the same in almost every enterprise I have looked at, and the eBOM-to-mBOM article puts the frequency at roughly six deployments in ten. The EBOM-to-MBOM translation is never given an owner and a system. Manufacturing keeps a parallel MBOM in a spreadsheet because the spreadsheet answers audit and liability questions the PLM configuration ignored. An engineering change is approved in PLM and does not propagate to the plan. ERP costs one version of the MBOM. MES builds another. Six months later the warranty team is reconstructing the as-built configuration of a field unit from paperwork and photographs.

The fix is organizational before it is technical. Name the owner of the translation. Put the process plan where the ECO can reach it. Treat the MBOM release, not the EBOM release, as the event that means engineering is done. The technology to do this has existed in every major PLM suite for a decade; adoption has not.

Variants and process families

A product with five hundred orderable variants does not get five hundred process plans. It gets a process family: a master plan for the variants that share geometry and assembly logic, with variant-specific operations or parameters switched by option. This is the manufacturing counterpart of the configurable BOM, and it is the only way high-mix manufacturers keep planning tractable. It also means the plan has to be under the same configuration management discipline as the product, with effectivity and baselines, or variant plans drift the same way variant BOMs do.

What is changing

The most interesting AI work in manufacturing right now is happening in this layer, not in the CAD tool. Three threads:

• Design-for-manufacturing feedback that reads geometry and tells the designer, before release, which features will be expensive or impossible to make on the available equipment.
• Automated routing generation that proposes an operation sequence and work center assignment from the model and the plant's resource library, for a planner to review rather than author from scratch.
• Adaptive plans that re-sequence or re-route when a machine, a material lot or a supplier is unavailable. That is the case for adaptive manufacturing in one sentence, and it depends on the routing being live data rather than a document.

All three assume the process plan is inside the digital thread. Which brings the argument back to where it started: the value of PLM is realized at the MBOM and routing, not at the EBOM.

Related Concepts

• EBOM vs MBOM: What's the Difference, and Why MES Lives in the Gap
• eBOM to mBOM: Why the Translation Gap Persists and How to Fix It
• What is an MBOM?, the manufacturing BOM in detail
• MES vs PLM: Who Owns What on the Shop Floor?
• CAD vs CAM and the Best CAM Software 2026 guide
• Best MES Software 2026, the execution layer the routing feeds
• Silicon to Systems, where digital manufacturing came from
• Manufacturing Process Planning, Routing and Manufacturing BOM in the glossary

Frequently Asked Questions

What does a manufacturing process plan contain?

The operation sequence, the work center or machine assigned to each operation, the tools, fixtures and gauges each one needs, setup instructions, the materials and subassemblies consumed at each step, standard times, and the quality checkpoints with what to measure and when. Structurally it is two artifacts: the manufacturing BOM, which regroups the parts by assembly sequence, and the routing, which is the ordered list of operations and where each happens. Work instructions are the operator-facing rendering of the routing.

Who owns process planning?

Manufacturing engineering, sitting between design engineering, which owns the EBOM, and production, which executes the routing. In mature organizations the process plan is authored in the manufacturing process management module of the PLM system so it stays linked to the engineering definition it derives from. In less mature ones it is authored in spreadsheets, which is why engineering changes fail to reach the shop floor.

How is process planning different from CAM?

Process planning decides the whole route a part takes through the factory: which operations, in what order, on which machines, with what inspections. CAM programs one of those operations on one machine, generating toolpaths and G-code from the CAD geometry. CAM is downstream of process planning and consumes its decisions. The Best CAM Software guide covers the CAM side; this page is about the plan that tells CAM what to program.

How is process planning different from production scheduling?

Process planning defines how a product is made and is largely stable across production runs. Scheduling defines when each work order runs on which machine on which day and changes constantly. ERP and advanced planning systems schedule against the routing that process planning produced. A plan without a schedule leaves parts waiting; a schedule without a good plan produces rework.

Why does process planning matter for PLM?

Because it is the step that connects the product record to production. PLM owns the EBOM and the engineering change process. When an ECO is approved, the process plan must change with it, and the revised MBOM and routing must reach ERP and MES. Where that linkage is missing, manufacturing maintains its own BOM outside PLM, ERP costs one version, MES builds another, and the as-built configuration of shipped units has to be reconstructed by hand.

How do process plans handle product variants?

Through process families. A product with hundreds of variants does not get hundreds of independent plans; variants with similar geometry and assembly logic share a master plan with variant-specific operations or parameters switched by option. This is the manufacturing counterpart of the configurable BOM, and it is the only way high-mix manufacturers keep process planning tractable.