APS, ERP, decision tool: who does what in your supply chain
ERP, APS, decision tool: three building blocks that are often confused, and worth telling apart so you don't expect a tool to play a role that isn't its own. What each one does, and what it doesn't.
By Mansour Niang, CEO & co-founder, Clevizio·Published July 17, 2026·9 min readKey takeaway
The ERP records and executes transactions, the APS plans and optimizes the near future, and the decision layer handles the trade-offs when the plan breaks between two cycles. These three building blocks complement each other and stack on top of the same data, without replacing one another. The classic mistake is expecting the ERP or the APS to handle disruptions in real time, a role that belongs to S&OE and that neither was designed for.
The ERP: record and execute
The ERP is the management system that records transactions and runs processes: orders, inventory, invoicing, accounting. It is the backbone of the company, the source of truth about what happened and what is happening right now. But the ERP mostly looks at the present and the past. It is not built to optimize the future or to make trade-offs when something unexpected happens, and asking it to play those roles is behind half the disappointments in supply chain projects.
The APS: plan and optimize
The APS, or Advanced Planning System, sits on top of the ERP to prepare the near future. It takes forecasts, capacities and constraints, then calculates an optimized plan: production, procurement, inventory levels. Where the ERP executes, the APS anticipates and optimizes, balancing thousands of constraints no planner could keep in their head. Its defining trait is also its limit: it works in cycles and assumes the plan holds until the next recalculation.
The MES: run and trace execution on the shop floor
Between the plan and the reality of the shop floor sits a fourth building block, often missing from comparisons: the MES, or Manufacturing Execution System. It runs and traces what actually happens on the machines (cycle times, downtime, quality, lot traceability) and feeds that reality back to the other systems. The APS says what should be done, the MES records what was done. Without an MES, an APS plans on performance assumptions nobody checks, which explains why plans sometimes look disconnected from the floor.
The decision layer: handle the unexpected
The decision layer steps in exactly where the APS stops: the moment the plan breaks, between two calculation cycles. It detects the drift, quantifies the impact of possible responses in euros of margin and prepares the trade-off, then keeps a record of it for next time. It doesn't plan and it doesn't execute any transactions; it decides in the gap between the plan and reality. This is the S&OE link, long left orphaned because it falls between two stools: too tactical for planning, too decision-heavy for execution.
ERP, APS, MES, decision layer: the comparison table
These four building blocks answer four different questions, and confusing them is expensive when you go to market for software. The table below compares them on the criteria that matter, including the structural limit of each one, the one no amount of configuration will fix.
| Criterion | ERP | APS | MES | Decision layer |
|---|---|---|---|---|
| Question answered | What happened? | What is the best plan? | What is happening on the shop floor? | What do we do now that the plan is drifting? |
| Horizon | Past and present | Weeks to months | Real-time, machine level | The hours following the deviation |
| Granularity | Transaction | Resource and order | Workstation and operation | Event and trade-off |
| Capacity assumption | Not applicable | Finite capacity | Observed capacity | Actual capacity at that moment |
| Input data | Orders and movements | Forecast, capacities, constraints | Machine and operator feedback | Deviation from plan, costs, customer priorities |
| Output | Entries and documents | Optimized plan | Traceability and actual performance | Costed options and a documented trade-off |
| Structural limit | Optimizes nothing | Works in cycles | Doesn't set priorities | Replaces none of the other three |
Where does MRP fit in all this?
MRP, Material Requirements Planning, comes up constantly in these discussions, and it is not a fifth building block: it is a function, almost always included in the ERP. It explodes bills of materials to calculate component requirements from the production schedule, assuming infinite capacity. That assumption is exactly what sets it apart from the APS: MRP tells you what you need, the APS tells you what you can actually produce given your resources. So the two aren't competitors, and a manufacturer torn between an MRP and an APS is usually asking the wrong question.
Three situations that show who answers, and who doesn't
First case: a supplier announces a three-week delay on a component. The ERP records the new date, the APS will factor it into its next run, the MES sees nothing for now, and nobody says whether to source elsewhere, push back a customer or launch a substitute run. Second case: an exceptional order comes in from a strategic customer. The ERP enters it, the APS will include it in the next cycle, the MES will execute whatever it is given, and the question of what accepting it costs the other customers goes unanswered. Third case: a machine breaks down. The MES flags it immediately, the ERP logs the non-conformities, the APS will replan, and yet someone has to decide within the hour which order to sacrifice. In all three cases, each building block does its job correctly, and the gap is always in the same place.
What vendors sell under the word planning
The word planning covers such different realities that you need to ask vendors to pin it down in every software selection. An ERP vendor talking about planning usually means its MRP module, with infinite capacity. An APS vendor means constraint-based optimization, sometimes only in one area, such as demand or scheduling. An MES vendor means detailed scheduling at the workstation level. Three questions are enough to clear up the ambiguity: does your tool account for finite capacity, at what time granularity does it recalculate, and what does it do when an event occurs between two runs? The third is the one that really separates them.
Four complementary building blocks, not competing ones
These building blocks don't replace each other; they stack and read the same data. The ERP executes, the APS plans, the MES traces reality, and the decision layer absorbs disruptions. The common mistake is expecting the ERP or the APS to handle the unexpected in real time, a role neither was designed for, and one the MES doesn't take on either, since it observes without making trade-offs. As for the order in which to equip yourself, it follows from the link that hurts the most: the ERP first if your data isn't reliable, the APS if the plan is built on gut feel, the MES if you don't know what really happens on the shop floor, and the decision layer if your plans are good but margin leaks away in reacting to disruptions.
This article starts from a conviction: the perfect forecast doesn't exist, what matters is the decision that follows.
- The ERP: record and execute
- The APS: plan and optimize
- The MES: run and trace execution on the shop floor
- The decision layer: handle the unexpected
- ERP, APS, MES, decision layer: the comparison table
- Where does MRP fit in all this?
- Three situations that show who answers, and who doesn't
- What vendors sell under the word planning
- Four complementary building blocks, not competing ones
Clevizio
Clevizio is the decision layer that plugs into your existing tools: it detects disruptions, simulates your options and keeps a record of every trade-off. See how the decision copilot works.
Mansour Niang
CEO & co-founder, Clevizio
A question about your disruptions? Book 30 minutes with me to estimate what they really cost you, with no commitment.
Frequently asked questions
What is the difference between an ERP and an APS?
The ERP records and executes transactions: it covers the present and the past. The APS sits on top of it to plan and optimize the near future (production, procurement and inventory), taking into account the finite capacities the ERP ignores.
APS vs MES: what is the difference?
The APS plans and schedules before execution; the MES runs and traces execution on the shop floor, machine by machine, in real time. The APS says what needs to be done, the MES records what was done and feeds reality back to the other systems.
Can an ERP handle scheduling?
Its MRP module calculates requirements assuming infinite capacity, which is enough for simple shop floors. As soon as you need to balance finite capacities, changeover times or shared tooling, an APS or a dedicated scheduler goes much further.
Is an APS enough to handle disruptions?
No. The APS works in cycles and assumes the plan holds. Between two cycles, when a disruption calls for an immediate decision backed by costed options, you need a separate decision layer at the S&OE level.
In what order should you equip your supply chain?
Based on the link that costs you the most. The ERP if your data isn't reliable, the APS if the plan is built on gut feel, the MES if you don't know the shop floor's actual performance. And a decision layer if your plans are sound but margin leaks away in reacting to disruptions.
Do you need to replace your ERP or APS to add a decision layer?
No. A well-designed decision layer sits on top of your existing ERP and APS, with no migration, reading the same data. It adds the missing link without touching the systems already in place.
Finally put a number on what disruptions cost you every year.
Let's start by estimating what your disruptions really cost you. It's free, it takes 30 minutes, and you leave with a figure nobody in your company knows today.