What is a PPS system? Definition and boundaries to MES, ERP and APS
A PPS system is the planning and control layer of manufacturing. It covers production program planning, material and capacity requirements planning, order release and sequence control. In DACH mid-market companies, it is either a module inside an ERP system or a standalone solution connected to the ERP. The boundary to MES, ERP and APS is methodologically central — and it determines the right cut between tools.
PPS stands for "Produktionsplanung und Steuerung" (production planning and control). The system covers the territory between commercial order intake and executing manufacturing. The classical task list includes production program planning, quantity planning (with MRP logic from BOM explosion), scheduling and capacity planning, order release, and sequence and detailed scheduling.
Five tasks distinguish a complete PPS system from a simple purchasing suggestion list: production program planning (demand derivation from sales planning and customer orders), quantity and material requirements planning (secondary demand from BOM explosion, inventory and procurement suggestions), scheduling and capacity planning (order flow against available resources, bottleneck consideration), order release and sequence control (readiness check, sequencing based on the setup matrix), and feedback and target-actual comparison (data flow from MES and shop-floor data collection back into planning).
The VDI guideline 5600 Part 1 on Manufacturing Execution Systems defines the task-oriented boundary between MES and PPS: the MES handles detailed scheduling on the shop floor and machine-data acquisition; the higher-level PPS/ERP remains responsible for program planning, material disposition and scheduling and capacity planning. An ERP system additionally holds the commercial master data and accounting functions. An APS system (Advanced Planning and Scheduling) extends PPS logic with constraint-based optimisation — useful where bottleneck machines and sequence-dependent setup times dominate.
Why PPS systems matter in DACH mid-market manufacturing in 2026
Requirements for on-time delivery, variant manufacturing and order throughput are rising — driven by variant explosion in machinery, Industry 4.0 connectivity and an ERP modernisation wave. A fitting PPS system in 2026 is less a tool decision than an architecture decision.
First: variant diversity is rising. Machinery and component builders in the DACH region increasingly deliver customer-specific configurations, while lead times are expected to fall. Without clean BOM maintenance and routing logic inside the PPS, this equation does not solve.
Second: Industry 4.0 connectivity is becoming standard. According to the Bitkom Industry 4.0 Study Report 2025, 71 % of surveyed industrial companies use Industry 4.0 applications, and nearly half are planning IoT-platform rollouts. With that, the demand on PPS shifts: it is no longer only about quantity planning, but about integration with machine data, sensors and energy management. A PPS chosen today without these layers in mind will be rebuilt in the next investment cycle.
Third — and this is the toughest financial lever: ERP modernisation in machinery manufacturing is happening now. According to the DSAG Investment Report 2026, the machinery, plant and component manufacturing sector is the largest segment among the surveyed DACH member companies, and a significant share is planning relevant investments in S/4HANA and Private Cloud deployments. Skipping the PPS question during this modernisation window risks an expensive remediation two years later.
Case study: mid-size machinery manufacturer with variant production, about 380 employees
In a PPS turnaround project with a southern German machinery manufacturer, we saw what happens when PPS selection is driven purely by feature scope — and the ERP-PPS integration layer is checked too late. The correction took nine months and a complete redefinition of routings.
A southern German machinery manufacturer with variant production (around 6,000 finished-product variants from modular configuration, three plants) had introduced a dedicated PPS that had ranked first on the feature comparison. After eight months of live operation, on-time delivery was worse than before, not better. We were called in for diagnosis and turnaround.
The cause was not in the PPS. It was in the data chain. BOMs had been maintained historically in two different structures — engineering BOM in the PDM system, manufacturing BOM in the ERP — and were not consistently married. Routings were partly ten years old, with setup times that no longer matched the current machine park. The setup matrix for sequence-dependent setup times did not exist at all — sequencing in the new PPS therefore ran against flat-rate values. From a Dreher perspective, a classic pattern: the tool had been chosen well, but the data foundation did not carry it.
We then retrofitted what we do first in every PPS project: a complete check of the ERP-PPS data chain — BOM, routing, setup matrix, material master — against the planned PPS function logic. The engineering and manufacturing BOMs were cleanly married through the PDM system, the routings were updated throughout, and the setup matrix for the twelve bottleneck machines was built for the first time. The result after nine months of rework: on-time delivery stable above the prior state, significant lead-time reduction in the ATO (Assemble-to-Order) order type, and a routing structure that could for the first time be called reliable. The lesson for managing directors: PPS selection follows the data-chain check, not the feature matrix. Architecture before software.
What most PPS guides leave unsaid
Three points that rarely surface in PPS comparison guides, but decide between project success and project abandonment in DACH machinery manufacturing — mirrored across more than 1,200 ERP and manufacturing-IT projects.
1. Integration before function — PPS selection is mostly an ERP integration problem
In most failed PPS projects we have analysed after the fact, software feature scope was not the problem. The problem lay in the ERP-PPS data chain: unmaintained BOMs, outdated routings, missing setup matrices, inconsistent material master data. The Trovarit Study ERP in Practice 2024/25 documents repeatedly that data quality and interfaces are among the most frequently named pain points in DACH ERP projects. From our experience in machinery manufacturing, we therefore put a data-chain check ahead of every PPS selection. Whoever skips this preparation buys a tool into unsuitable ground.
2. MES vs. PPS vs. APS — the decision logic is missing in most guides
The common PPS reference works list MES, PPS and APS side by side without delivering a credible decision matrix for mid-market manufacturers. From a Dreher perspective, the following framework applies to series and variant manufacturers in DACH machinery: A PPS module inside the ERP is typically sufficient where order volume is manageable and manufacturing depth is not strongly bottleneck-driven. An APS add-on becomes useful for sequence-dependent setup times at bottleneck machines and high variant diversity. A dedicated MES system becomes mandatory only where machine-data connectivity, shift management and tight target-actual feedback at the shop floor are required. The VDI 4400 Part 2 on logistics indicators for production provides the methodological basis for evaluation — on-time delivery, lead time, inventory turn and utilisation as decision-relevant indicators.
3. Data chain BOM–routing–setup matrix before tool selection
Most PPS vendors advertise algorithms, cloud delivery and AI-driven planning. From a Dreher perspective, the reliable data chain of BOM, routing and setup matrix is the actual lever — and what is most often missing during preparation. A properly maintained setup matrix for bottleneck machines is in practice often more valuable than an APS algorithm, because the sequencing logic then operates on reliable inputs for the first time. The Fraunhofer IPA PPS 4.0 study has repeatedly described this pattern: digitalisation of order processing in the German mid-market fails primarily because of master-data quality and interfaces — not because of missing software.
Our reading
A PPS without a verified ERP-PPS data chain, without a clear boundary to MES and APS, and without an up-to-date setup matrix for the bottleneck machines is an expensive investment on a shaky foundation. These three points belong in the preparation phase, not in remediation.
How we approach PPS selection in machinery manufacturing
We approach PPS projects in four phases: data-chain check before feature evaluation, requirements specification before tender, vendor-neutral selection across multiple vendors, pilot with measurable logistics indicators. Methodological clarity decides, not the tool.
In our vendor-neutral ERP and systems consulting, we do not consider PPS in isolation but as part of the manufacturing and ERP architecture. Methodologically, a four-stage approach has proven itself in our work:
Phase 1 — Data-chain check BOM–routing–setup matrix. Completeness, currency, consistency. Before any feature discussion. Phase 2 — Architecture decision PPS-in-ERP vs. dedicated / APS add-on / MES layer — based on order volume, variant complexity, bottleneck situation and machine-data needs. Phase 3 — Vendor-neutral selection with a requirements comparison across several vendors in the DACH market and a TCO framework over five years. Phase 4 — Pilot with logistics indicators per VDI 4400 Part 2, one production line, defined KPIs (on-time delivery, lead time, inventory, utilisation). Only then full rollout.
A supporting process-mining analysis often provides the reliable fact base: actual lead times, idle times and waiting situations become visible before PPS requirements are formulated. The essential difference to other consulting offers: we recommend vendor-independently. From our experience, the effort of vendor-neutral selection pays off — otherwise the company buys the consultant's favourite solution, not the solution that fits its machine park.
Common mistakes in PPS implementation
Four error patterns recur in mid-market PPS projects. All of them are avoidable — if they are addressed before tool selection. Three are organisational (data chain, role model, pilot approach), one is methodological (indicator measurement). None of the four has its root in the software itself.
Mistake 1 — Feature comparison before data-chain check. The company selects a PPS because a vendor was particularly convincing or offered many modules. The data-chain questions — BOM, routing, setup matrix — are deferred to the implementation phase and block it there. From Dreher practice: the leading issue in more than half of all turnaround projects.
Mistake 2 — Role model unclear. Who maintains the BOMs, who the routings, who the setup matrix? Who decides on conflicts between planning and shop-floor control? Without clear responsibilities — part of a credible integration test — the new PPS inherits the old chaos.
Mistake 3 — Big-bang rollout without pilot. The PPS is rolled out simultaneously for all plants, all order types and all production lines. Data-quality issues only surface during mass use — and are then expensive to fix. We recommend a pilot line with a clearly defined runtime and pre-agreed abort criteria.
Mistake 4 — No indicator measurement. Without KPIs per VDI 4400 Part 2 (on-time delivery, lead time, inventory turn, utilisation), project success remains a matter of opinion. These indicators can be collected in DACH mid-market companies if reporting is planned in from day one.
Frequently asked questions
The ERP holds commercial and accounting-relevant master data and processes — articles, prices, orders, accounting, inventory on the balance-sheet level. The PPS manages planning and control of manufacturing — quantity planning, scheduling and capacity planning, order release, sequence control. In the DACH mid-market, the PPS is often a module inside the ERP. With high variant complexity or bottleneck-driven manufacturing, a standalone PPS or APS solution connected to the ERP becomes a candidate. The architecture question belongs before the feature discussion.
From a Dreher perspective, the following heuristic applies to DACH machinery and component manufacturers: the PPS module inside the ERP is typically sufficient for manageable order volumes, low to medium variant diversity, and without strongly bottleneck-driven sequencing. An APS add-on becomes useful for sequence-dependent setup times at bottleneck machines and high variant diversity. A dedicated PPS or an MES layer becomes mandatory where machine-data connectivity, shift management and very fine target-actual feedback are required. The credible decision requires a data-chain check and a bottleneck analysis before the vendor conversation.
From our experience, a serious PPS implementation in DACH machinery manufacturing typically takes between nine and eighteen months, depending on the number of plants, variant complexity and the state of the ERP data chain. If BOMs, routings and setup matrices are already in a decision-grade quality, the runtime can be held at the lower end. Without this preparation, the implementation phase often doubles because data-chain work has to be done ad hoc. We recommend four to eight weeks of data-chain checking, then requirements specification and tender, then pilot, then a staged rollout.
Total cost of ownership varies widely by vendor, delivery model (on-premises, private cloud, SaaS), number of users, number of plants and integration effort. Realistic ranges for DACH machinery and component manufacturers with one plant and medium variant complexity sit in the low six-figure range over five years; with several plants and APS/MES additions, considerably higher. Implementation — and especially the data-chain work — dominates total cost, not the licence. We calculate TCO over five years, not over the first licence year, and explicitly include preparation cost in the calculation.
Variant production in machinery is the stress test for every PPS. From a Dreher perspective, the position of the Order Penetration Point — the point at which a customer-neutral pre-manufactured part becomes a customer-specific order — is decisive. We deliberately move this point according to operational logic and check the PPS against exactly that configuration. A PPS that does not cleanly support an ATO mode (Assemble-to-Order) — anonymous pre-manufacturing, customer-specific final assembly — fails in DACH machinery manufacturing. This check belongs in the requirements specification, not in the implementation contract.
Next steps
Before selecting a PPS system, a four-to-eight-week preparation phase is usually worth the effort — data-chain check (BOM, routing, setup matrix), architecture decision PPS-in-ERP vs. dedicated vs. APS add-on, and a bottleneck check in the machine park. Whoever skips this step buys software into an unchecked data foundation and risks a turnaround project after twelve to eighteen months. Background in our Insights and under independent ERP consulting.
30 minutes with Dr. Harald Dreher
A structured assessment of your PPS starting position — vendor-neutral, from more than 1,200 ERP and manufacturing-IT projects.
