APS vs MES software: what each one does and which you need first
A practical guide for mid-size manufacturers: what an APS solves, what an MES solves, how both differ from ERP and MRP, and in which order to implement them.

Almost every conversation with a plant manager starts the same way: “we have an ERP, but scheduling lives in Excel and we don't really know what happens on the floor”. That's where two acronyms show up: APS and MES.
They are not competitors. They solve different moments of the same process: APS decides what will be produced and when; MES records what was actually produced. This guide explains the difference without buzzwords, plus criteria to decide where to start.
What an APS (Advanced Planning & Scheduling) does
APS is the planning brain. It takes demand — firm orders, forecast, target stock — and turns it into a realistic sequence of production orders, respecting finite capacity for every resource: machines, molds, people, shifts and available materials.
The difference with a spreadsheet is that APS never assumes infinite capacity. If mold 4 can only run three references per shift, the plan honors it. And when a rush order lands, it reschedules in seconds and shows the impact on every other promised date.
- ▸Finite-capacity scheduling with real constraints (setup, sequence, tooling).
- ▸Interactive Gantt: drag an order and see the ripple effect.
- ▸What-if scenarios: overtime, extra shift, subcontracting.
- ▸Reliable delivery promises for the sales team.
- ▸Prioritization by margin, key account or commitment date.
What an MES (Manufacturing Execution System) does
MES lives on the shop floor. Operators report start and end of operation, good and scrap quantities, downtime with root cause, changeovers and material consumption. Its value is truth: there are no longer competing versions of what happened during the shift.
That capture produces the indicators that actually move the needle: OEE (availability × performance × quality), scrap by cause, real setup time, schedule adherence and actual cost per order versus standard.
- ▸Real-time production reporting from tablet, kiosk or barcode scanner.
- ▸OEE by machine, line, shift and product.
- ▸Downtime logging with root cause and micro-stops.
- ▸Lot traceability: which material went into which order and which customer.
- ▸Alerts when an order runs late or scrap crosses a threshold.
APS vs MES vs MRP vs ERP in one table
The most common mistake is asking an ERP to schedule the plant. ERP is transactional and financial; MRP calculates material needs; APS sequences against capacity; MES executes and measures.
| System | Question it answers | Horizon | Key data |
|---|---|---|---|
| ERP | What did I sell, buy and invoice? | Months | Transactions and costs |
| MRP | What material do I need and when? | Weeks | BOM, stock, lead time |
| APS | Which machine, in what order, at what time? | Days / hours | Finite capacity and constraints |
| MES | What was actually produced and how efficiently? | Minutes / real time | OEE, downtime, scrap, traceability |
How to decide which one comes first
The rule we use with clients is simple: look at where the money hurts most.
- ▸Missing delivery dates, replanning three times a day, nobody knows the current version → start with APS.
- ▸No idea what your OEE is, arguing about shift quantities, scrap surfacing at month end → start with MES.
- ▸Buying late, running out of raw material or sitting on dead inventory → start with MRP tied to APS.
- ▸If the gap is management visibility rather than data capture, a BI dashboard on your current sources can deliver in weeks.
The full loop: plan, execute, measure, reschedule
The real value shows up when both talk to each other. APS hands the schedule to MES; MES returns actual progress, downtime and consumption; APS reschedules against reality instead of assumptions. That closed loop is what turns a reactive plant into a predictable one.
In our implementations, APS and MES connect to the ERP via API (SAP, Odoo, Dynamics, Siesa, Siigo, World Office) so item, customer and order masters are never duplicated.
Why implementations fail
- ▸Starting with invented routings and standard times: with bad data, APS schedules fiction.
- ▸Asking operators for ten fields per order: if reporting takes more than 20 seconds, it won't happen.
- ▸Measuring OEE before agreeing what counts as planned downtime.
- ▸Buying a giant suite to use 8% of it: mid-size plants do better with a tailored module that grows in phases.
Frequently asked questions
Can I run MES without APS?+
Yes. Many plants start with MES to get real OEE and adherence data, then feed those real times into APS later. It is a perfectly valid order and usually shows results in the first month.
Does APS replace MRP?+
No. MRP calculates which materials you need and when; APS decides the sequence against real capacity. They work together: if material slips, APS must reschedule the order.
How long does an implementation take?+
With a phased scope, a first productive module usually goes live in 6 to 12 weeks: routing and work-center discovery, master data load, pilot on one line, then rollout.
Does it work if I keep using Excel for some things?+
Yes, and that's normal at the start. What matters is that scheduling and production reporting stop living in loose files; ad-hoc analysis can still go to Excel or Power BI.
Keep reading
Sources and references
Want to see APS and MES running with your own products?
We'll walk you through a demo based on a similar case and tell you honestly whether you need APS, MES or just a control dashboard.