APS — Advanced Planning and Scheduling

APS (Advanced Planning and Scheduling) is a class of planning software that resolves production schedules under finite-capacity constraints — unlike classic MRP, which assumes infinite capacity. APS computes feasible schedules that respect machine availability, tooling, setup times and shift patterns simultaneously. In mid-market manufacturing with multiple bottleneck resources, APS replaces the planner's spreadsheet-based capacity workaround with a deterministic, repeatable optimisation.

When APS pays off

APS becomes valuable when production runs at 80%+ capacity utilisation, multiple resources compete for shared capacity, setup-times are sequence-dependent and large enough to optimise around (typical in machining, plastics, food production), or order-mix changes frequently. Below these thresholds, MRP plus sensible manual scheduling is sufficient and cheaper.

How APS works

APS reads the open production plan from the ERP, fetches resource capacity, applies a planning algorithm — typically a combination of constraint propagation, genetic algorithms and heuristics — and produces an executable schedule with start and end times per operation. The planner reviews, adjusts manually where needed, and releases. Re-planning runs daily or on demand. Output flows back to ERP as updated production orders.

Leading APS vendors in the DACH market

Standalone: Asprova, PSI Penta APS, Quintiq (Dassault), Siemens Opcenter APS (formerly Preactor). Embedded in ERP: SAP S/4HANA (PP/DS), proALPHA APS, IFS Cloud, Epicor Kinetic. Pricing varies from 30,000 EUR/year for SMB embedded APS to several hundred-thousand EUR for enterprise standalone deployments.

APS, MRP and MES — drawing the boundaries

Three planning layers are routinely confused. MRP (Material Requirements Planning) explodes the bill of materials against forecast and firm demand under the assumption of infinite capacity. It answers what to procure and produce, and when. APS adds the finite-capacity constraint and produces a sequenced, feasible schedule per resource. MES (Manufacturing Execution System) takes the released APS schedule and runs it on the shop floor: dispatching work, capturing actuals, managing operator interactions with machines. In modern DACH manufacturing, the data flow is MRP → APS → MES → back to ERP for inventory and cost-accounting updates. Each layer has its own master data, but the boundary is well-defined: MRP-relevant routings live in ERP, finite-capacity resource calendars and changeover matrices live in APS, machine-level execution logic lives in MES. Mid-market companies often start with MRP-only, add APS once capacity becomes the binding constraint, and add MES once shop-floor data capture justifies the integration effort.

Selection criteria and DACH-mid-market case examples

When evaluating APS for a DACH manufacturer, the editorial shortlist of selection criteria has roughly seven items. (1) Modelling fidelity: does the platform accurately represent your bottleneck constraints — setup matrices, parallel resources, alternative routings, tool availability, maintenance windows? (2) Solver behaviour: deterministic and reproducible (changing the same input gives the same output) versus heuristic with run-to-run variation. (3) Integration robustness: real-time bidirectional sync with the ERP, conflict-resolution on master-data changes during a planning run. (4) Planner experience: Gantt manipulation, what-if scenarios, exception flagging. (5) Master-data hygiene support: data-quality monitors, audit trails on master-data changes. (6) DACH-language localisation: German planner UI, documentation. (7) Vendor presence in the region for support and consulting. Two practical mid-market examples: a German plastics injection-moulder with 35 machines uses Siemens Opcenter APS integrated with SAP S/4HANA Public Cloud (project around 600,000 EUR, 9 months). A Swiss food producer with sequence-dependent cleaning cycles between allergen runs uses Asprova on top of IFS Cloud (350,000 EUR, 7 months). Both report 8–15% on-time-delivery improvement post go-live.

Data quality as the make-or-break factor

APS outcomes are dominated by master-data quality, not solver sophistication. Three categories of master data drive feasibility. Routings: operation sequence per item, with processing time per quantity, setup time per changeover, and skill or tool requirement. Routings that record only nominal times miss the difference between fast and slow product variants, leading the solver to underbook capacity. Resource calendars: shift patterns, planned maintenance, holidays, and historical OEE (Overall Equipment Effectiveness) factor. Optimistic calendars overpromise; pessimistic ones underutilise. The DACH practice is to back-test the calendar against last quarter's actual production volume before going live. Setup matrices: time and material cost to change a resource from product A to product B. In plastics, food, chemicals and surface treatment, sequence-dependent setups are the single largest planning lever — getting the matrix right typically reduces total setup time by 15–30%. Before procurement, candidates should be assessed on their ability to import, edit and validate these data sets. The pre-go-live data-cleansing phase typically consumes 40–60% of project effort. Companies that under-budget this phase routinely see APS adoption stall within 3–6 months of go-live as planners revert to spreadsheets. Companies that invest disproportionately in data quality see APS become embedded in operations within the same time window, with measurable inventory and OTIF improvement. The discipline carries over to MES rollout, where the same routing data underpins shop-floor dispatching.

Frequently Asked Questions

What is the difference between MRP and APS?

MRP calculates material requirements assuming infinite capacity — it tells you what to order and when. APS schedules under finite capacity — it produces a sequence of operations that respects real-world constraints. In mature ERP setups, MRP feeds demand into APS, which determines the actual production schedule.

Can the ERP handle scheduling without APS?

For simple assembly with abundant capacity and few products, yes. For complex make-to-order machine engineering, plastics with shared moulds, or food production with cleaning sequences, no — the manual workarounds become a bottleneck themselves.

How long does APS implementation take?

Embedded APS in existing ERP: 2-6 months including master-data cleanup. Standalone APS with ERP integration: 6-18 months for a single plant. Master-data cleanup is usually the longest phase — APS only works with accurate setup times, processing times and resource requirements.