Your ERP calculates component requirements flawlessly. It cascades production orders, respects lead times, integrates stock levels. And yet on the shop floor, delays persist, emergencies pile up, and your production lines run in firefighting mode. The problem is not your ERP — it is what your ERP deliberately ignores: the actual capacity of your workshops.
This is the structural limit of MRP II, and it is precisely what an APS (Advanced Planning and Scheduling) system is designed to solve.
The MRP II Limits Your ERP Does Not Advertise
MRP Calculates Requirements but Ignores Real Capacity Constraints
MRP II rests on a convenient assumption: production capacity is infinite. In practice, the requirements-planning engine generates a plan assuming that machines, operators, and tooling are always available — no conflicts, no downtime, no maintenance windows.
This assumption drastically simplifies the calculation, but it disconnects the plan from shop-floor reality. As Siemens’ own planning documentation notes, MRP reasons in “infinite capacity before handing off to more specialised finite-capacity planning modules.” The resulting plan is theoretically sound but industrially impossible to execute.
Concretely: MRP may schedule 500 parts on the milling machine between Monday 8 am and Wednesday noon, unaware that the machine is in preventive maintenance on Tuesday, the qualified operator only works mornings, and the supplier batch does not arrive until Wednesday afternoon. The plan looks fine on paper and falls apart in production.
Symptoms of an Overloaded Planning Process: Chronic Delays, Overstock, Firefighting
If your organisation shows the following signs, MRP II’s structural ceiling is likely the root cause:
- Chronic delays on orders that appeared correctly scheduled
- Component overstock coexisting with stockouts on other references — a sign that the plan ignores real load patterns
- Weekly emergency meetings to re-prioritise work orders by hand
- Parallel spreadsheets maintained by shop-floor supervisors to manage the actual day
- Customer service levels that stagnate despite ERP investments
These symptoms do not mean your ERP is broken. They mean you are using a requirements-planning tool to solve a resource-scheduling problem — two fundamentally different challenges.
What Is an APS?
Definition and Functional Scope
An APS (Advanced Planning and Scheduling) is an optimisation engine that plans materials and capacity simultaneously, accounting for the full set of real constraints: machines, labour, tooling, supplier lead times, customer priorities, and sequencing rules.
Where MRP asks “what do I need?”, APS answers “how can I produce all of this within available time, with real resources?” It does not replace the ERP — it complements it. The APS takes the requirements calculated by MRP and generates an industrially feasible production programme.
A typical APS covers:
- Finite-capacity scheduling of work orders
- Scenario simulation (what if machine 3 breaks down?)
- Simultaneous handling of multiple priorities and constraints
- Disruption management (breakdowns, absences, material delays) via dynamic replanning
Tactical APS vs Operational APS: Two Distinct Families
The term “APS” covers two functionally distinct families operating at different time horizons and levels of granularity.
Tactical APS (S&OP / Sales & Operations Planning) works on a 3-to-18-month horizon. Its role is to balance supply and demand at enterprise or group level: which product families to produce, on which sites, with what global capacity? It is a strategic management tool for industrial directors and supply chain managers.
Operational APS (finite scheduling) works on a horizon of today to D+30. It sequences each work order, operation by operation, machine by machine, accounting for precise technical constraints. It is the tool of the shop-floor supervisor and production planner.
Poorly scoped APS projects frequently conflate the two levels — deploying an S&OP tool to solve a daily scheduling problem, or vice versa.
Finite vs Infinite Capacity: The Fundamental Distinction
The essential distinction: MRP plans at infinite capacity (assuming resources are available on demand), while APS plans at finite capacity (modelling real available resources and allocating only what is physically possible).
In practice, finite-capacity planning transforms a theoretical plan into an executable shop programme. It accounts for: machine calendars, changeover times between runs, skills required per operation, available tooling and fixtures, and customer delivery priorities. The result is a schedule that “holds” — without requiring constant manual adjustments.
Leading APS Solutions on the Market
Native ERP Modules: SAP PP/DS, Oracle ASCP, Infor CloudSuite Planning
The world’s major ERP vendors have developed their own advanced scheduling modules, natively integrated into their suites:
SAP PP/DS (Production Planning and Detailed Scheduling) is SAP S/4HANA’s detailed scheduling module. It benefits from native integration with SAP production data (routings, work centres, production orders) and enables finite-capacity scheduling with configurable priority rules. Its main advantage: zero interface development for SAP customers. Its key risk: configuration is complex and requires PP/DS-specialist consultants, distinct from standard PP consultants.
Oracle ASCP (Advanced Supply Chain Planning) plays an equivalent role in the Oracle SCM Cloud ecosystem. Oracle is positioned as a Leader in both editions of the 2026 Gartner Magic Quadrant for Supply Chain Planning Solutions (discrete and process industries), confirming the offer’s maturity (Oracle, August 2026).
Infor CloudSuite Planning is Infor’s answer for CloudSuite Industrial (SyteLine) and M3 customers. Relevant for mid-market manufacturers already standardised on the Infor ecosystem.
Specialist APS: Opcenter, DELMIA Ortems, o9 Solutions
For companies running an ERP without a mature native APS module, or those with highly specific scheduling requirements, specialist APS solutions offer deeper functional coverage at the cost of an integration project.
Siemens Opcenter APS (formerly Preactor) is one of the most widely deployed solutions in Europe and North America for mid-market manufacturers, particularly in metalworking and plastics. It connects to most ERP platforms through standard connectors. Its modular architecture enables progressive deployment: simple scheduling first, then simulation and advanced optimisation. Siemens positions Opcenter APS as part of its Xcelerator portfolio, facilitating integration with the Opcenter Execution MES (Siemens).
DELMIA Ortems is Dassault Systèmes’ APS solution, particularly present in process industries (chemicals, food and beverage, pharmaceuticals) and automotive tier-one suppliers. Its position within the 3DEXPERIENCE ecosystem simplifies integration with Dassault PLM and simulation tools.
o9 Solutions is the newest entrant on this list and the fastest growing. Positioned as a Leader in both 2026 Gartner MQ reports for Supply Chain Planning (discrete and process industries), o9 targets large enterprises with a unified planning engine covering S&OP, demand planning, and scheduling (o9 Solutions, 2026). Less relevant for a 200-person mid-market manufacturer; highly relevant for a multi-site industrial group.
Kinaxis is also a Leader in both 2026 Gartner MQ reports, cited as “highest on Ability to Execute” for discrete industries (Kinaxis, 2026). Oriented toward concurrent planning at medium-to-long horizons; less focused on detailed shop-floor scheduling.
Selecting by Company Profile and Sector
| Company profile | Recommended solution |
|---|---|
| Mid-market 50–500 employees, SAP ERP | SAP PP/DS (native module) |
| Mid-market 50–500 employees, non-SAP ERP (IFS, Infor, Sage) | Siemens Opcenter APS or DELMIA Ortems |
| Process industries (chemicals, pharma, food & beverage) | DELMIA Ortems or OMP |
| Multi-site group, S&OP + operational horizon | o9 Solutions or Kinaxis |
| Small business <50 employees, basic scheduling needs | Built-in scheduling modules from SMB ERP vendors |
Integrating an APS with Your ERP: The Technical Project
Data Flows Between ERP and APS
ERP-APS integration is bidirectional. Understanding exactly which data flows in which direction is the first step of any project.
ERP to APS (downstream): the ERP sends the APS planned work orders, operational routings with standard times per operation, bills of materials, resource calendars (machine and labour capacity), available stock, and customer priorities. The APS receives the “what to produce” and “how” — it does not access the ERP database directly.
APS to ERP (upstream): the APS returns the scheduled plan — each work order with its start and end date per operation, per work centre, with recalculated priorities. The ERP updates its production orders with these dates and communicates them to shop-floor supervisors via production documents.
The quality of this integration determines 80% of project success. An APS fed with overly aggregated data (no detailed routings) or stale data (daily synchronisation) will produce plans no better than the original MRP output.
Synchronisation Frequency and Disruption Management
ERP-APS synchronisation raises a key question: how often? The answer depends on the production context.
In a stable environment (repetitive production, rare disruptions), synchronisation every 4 to 8 hours is sufficient. In highly reactive environments (make-to-order, high variability), hourly or near-real-time synchronisation becomes necessary.
Disruption management is the ultimate test of an operational APS system. When machine 3 breaks down at 10 am, the APS must replan the entire programme within minutes and propose a feasible alternative. This requires the breakdown event to reach the APS immediately — either via the MES or through direct supervisor input.
Data Prerequisites: The Number-One Success Factor
ERP data quality is the non-negotiable prerequisite for any APS project. An APS does not fix bad data — it optimises it, which can amplify errors.
Critical prerequisites:
- Reliable operational routings: every operation must carry a real standard time, not a theoretical or approximate one. Routings with times “rounded to the nearest quarter-hour” will produce unrealistic schedules.
- Changeover times: series changeovers (switching between two different products on the same machine) must be modelled. Missing this parameter systematically underestimates the load.
- Up-to-date resource calendars: machine availability (planned maintenance, technical stoppages) and operator availability (leave, training, shift patterns) must be current in the ERP before transmission to the APS.
- Consistent stock levels: phantom stock (items recorded in stock but physically absent or quality-blocked) distorts material availability calculations.
Field experience shows that an APS project launched without a prior data audit spends 30–40% of its budget correcting data rather than configuring scheduling logic.
ROI and Real-World Results
Typical Gains Observed on Industrial Sites
Industry publications converge on consistent order-of-magnitude benefits for a well-deployed APS. Two levels of analysis are worth distinguishing.
At the broader supply chain organisation level, McKinsey (Industry 4.0 analysis) documents gains of 10 to 30% throughput increase and 20% inventory reduction for companies deploying advanced planning tools coupled with autonomous execution (McKinsey via DecisionBrain APS Statistics 2026).
At the specific APS scheduling level, field results reported by specialist integrators (Siemens, DELMIA) fall within the following ranges — to be treated as benchmarks, not contractual guarantees:
- Delivery lead time reduction: 15 to 30% depending on initial planning complexity
- Customer service level improvement (OTD): 5 to 15 percentage points
- Work-in-progress (WIP) reduction: 10 to 25%, driven by fewer emergency batches and reduced queue time on the shop floor
These gains typically materialise between 6 and 18 months after go-live, once teams are trained and data is stabilised.
Deployment Timeline and Critical Success Factors
A standard APS project (mid-market scope, one to three workshops, connected to an existing ERP) runs 4 to 9 months depending on routing complexity and data state.
Factors that shorten the timeline:
- Clean, up-to-date routing data before the project starts
- A pilot on one workshop or product family before full rollout
- A client-side project manager with 30–50% of their time dedicated to the project
- An executive sponsor who enforces data discipline (routings do not improve without management pressure)
3 Common Mistakes in APS-ERP Integration
Mistake 1: deploying APS without cleaning the data. The temptation is to run the APS project in parallel with data remediation. In practice, planners will not use an APS whose outputs they do not trust. The data audit must precede deployment, not run alongside it.
Mistake 2: underinvesting in planner training. An APS is an expert tool. A planner who has only ever worked with spreadsheets or standard ERP reports needs 2 to 4 weeks of training to understand scheduling logic and correctly interpret the generated plans. Training is often the first cost cut when the budget tightens — a strategic mistake.
Mistake 3: trying to optimise everything in one step. APS solutions offer dozens of priority rules, optimisation criteria, and configurable constraints. First-time implementation teams often try to model the full complexity of real operations from day one. The result: a model too complex to maintain and whose decisions no one understands. Start simple, demonstrate results, then refine.
Checklist — Is Your Site Ready for an APS?
Before launching a request for proposals or a proof of concept, answer these 5 questions honestly:
-
Are your operational routings entered and up to date in the ERP, with real standard times? If more than 20% of your routings carry “estimated” or unverified times from the last 3 years, fix these first.
-
Does your shop floor have more than 5 to 8 constraining resources (bottleneck machines or specialist operators) that need simultaneous sequencing? Below this threshold, manual or semi-automated scheduling is sufficient. Above it, APS delivers real value.
-
Does your re-planning rate (orders reprogrammed after launch) exceed 25% per week? If so, your MRP is generating plans the shop floor cannot honour — the classic symptom.
-
Do you have a production or supply chain manager who will champion the project internally? An APS project without an operational sponsor on the client side consistently fails.
-
Is your current ERP stable and up to date (no ERP migration planned in the next 18 months)? Deploying an APS on an ERP being replaced is wasted effort — wait for stabilisation.
If you answer no to 3 or more questions: start with a data improvement and MRP stabilisation initiative before investing in APS.
If you answer yes to 4 or 5 questions: you are in the maturity zone for an APS project. The next step is a 3-month proof of concept scoped to a single product family or workshop, to validate value before scaling.
To go further on production planning within your ERP, read our ERP and manufacturing guide: MES, IoT and Industry 4.0, our ERP Lean manufacturing analysis: kanban, OEE and kaizen and our industrial ERP comparison: SAP S/4HANA vs IFS Cloud vs Infor CloudSuite for mid-market manufacturers.
