APS vs ERP vs MES: What Is the Difference?

If you've sat in enough planning meetings, you've probably heard someone say "just put it in the ERP" or "the MES will handle that" or "we need better APS." Usually said with total confidence, and usually meaning three completely different things.

These three systems get lumped together a lot because they all sit somewhere in the "run the factory" category. But they solve different problems, on different timescales, for different people. Getting this straight matters, because a lot of scheduling headaches come from expecting one of these systems to do a job it was never built for.

ERP, MES, and APS answer three different questions. ERP plans how much to make over weeks and months. MES records and executes what happens on the floor right now. APS decides the order in which work runs, on which resource, and starting when.

If you've ever seen an ISA-95 diagram, this is roughly the Level 4 to Level 3 boundary that everyone draws and almost nobody staffs. ERP sits at Level 4, MES at Level 3, and the scheduling decision falls in the gap between them.

ERP (Enterprise Resource Planning) is the system that runs the business side of the operation. Orders, inventory levels, purchasing, finance, HR, all of it usually lives here, or at least connects through it. In most process plants this means SAP or Oracle, sometimes Infor or a regional equivalent.

When it comes to production, ERP typically plans at a fairly coarse level: weeks or months, not hours. It might tell you "we need to make 10,000 units of Product X in March" based on demand forecasts and open orders. That's genuinely useful information. It's just not detailed enough to run a shift.

Ask an ERP "should Batch 4471 run before or after Batch 4472 on Line 2 today," and you'll usually get silence, because that's not the question ERP was built to answer.

MES (Manufacturing Execution System) lives on the opposite end of the timeline from ERP. Where ERP looks at months, MES looks at right now: what's running on which machine, what's been produced, what quality checks have passed, what the current status of a work order is. Think Wonderware, Siemens Opcenter, Werum PAS-X in pharma, or a LIMS like LabWare sitting beside it for the lab side.

MES is mostly about capturing and executing, less about deciding. It records what happened (this batch started at 9:14am, this many units passed inspection) and it often enforces the steps of a process (you can't move to step 4 until step 3's checklist is signed off). It's the system of record for the shop floor.

What MES generally doesn't do well is figure out the best sequence of work in the first place, especially when there are competing constraints across machines, people, and time. It executes a plan. It doesn't usually build one.

APS (Advanced Planning and Scheduling) is where the actual sequencing decisions get made. Not "what do we need to make this quarter" (that's ERP) and not "what's happening on the line right now" (that's MES), but "in what order, on which resource, starting when." If you've been shopping for production scheduling software, this is the category you were actually looking at.

This is the layer that takes ERP's demand numbers and MES's real-time floor status and works out a genuinely executable schedule: Batch A runs on Line 2 from 6am, changes over for Batch B at 11am, meanwhile Line 3 handles the rework that came in from yesterday, and the maintenance window that was supposed to happen at 2pm gets nudged to avoid a conflict.

Older APS tools have historically been decent at this in a static sense: build the schedule once, optimise it, and mostly hold to it. Where a lot of them struggle is keeping up when things change mid-shift, which in most real plants is constantly. Newer, more adaptive approaches are built specifically to re-optimise in minutes rather than hours whenever something on the floor shifts. That's a meaningfully different design goal, and it's worth asking about directly if you're evaluating options.

APS vs MES is the comparison that trips people up most often, because those two sit closest together in the stack and both talk about work happening on real equipment. Part of it is that these systems genuinely overlap at the edges. Some ERP suites bolt on basic scheduling modules. Some MES products have simple sequencing features. Some APS tools try to absorb execution or business-planning functions too. Vendors don't always help, either, since "does everything" sounds better in a sales pitch than "does one thing well."

But the practical test is usually simple: ask what timescale a tool is actually operating on, and what decision it's actually making. Months and demand numbers, that's ERP territory. Right now and what happened, that's MES. The detailed sequence of who does what, when, and in what order, especially when that sequence has to survive real-world disruption, that's APS.

There's a second, more practical test for anyone who owns the integration: ask which system you would have to change if a reactor went down at 10am. If the honest answer is "none of them, someone would just rework the plan by hand," you've found the gap.

The common failure pattern in plants isn't usually "our ERP is bad" or "our MES is bad." It's that nobody owns the middle layer properly, so scheduling ends up happening informally: a planner's spreadsheet, a whiteboard, tribal knowledge about which changeovers to avoid.

That works until the plant gets complex enough that no one person can hold the whole picture in their head anymore, and then Production, QC, and Maintenance start planning slightly out of sync with each other without realising it. Each function's plan is perfectly rational on its own. The collision only shows up on the floor.

Getting APS right doesn't mean replacing ERP or MES. Done well, it sits between them, taking the demand signal from one and the real-time reality from the other, and turning that into a schedule someone can actually run the floor on. ERP still owns the demand plan. MES still owns execution and the batch record. APS owns the sequence, and hands it to MES to run.

If "who owns the actual schedule" has never had a clean answer at your plant, that's usually a sign this layer is missing, not that your ERP or MES is failing. This is the layer Bodhee sits in, alongside your existing systems rather than replacing either one.

MES executes and records what happens on the floor; APS decides the sequence MES then executes. MES is the system of record for production events. APS is the system of record for the schedule.

Some ERP suites include a basic scheduling module, but ERP plans in weeks and months against demand. APS sequences work in hours against live plant constraints. The two answer different questions on different timescales.

If nobody can say who owns the detailed sequence, and it currently lives in a planner's spreadsheet, the APS layer is missing regardless of how good your ERP and MES are.

No. APS sits between them, taking demand from ERP and live status from MES, and returning an executable schedule that MES runs and ERP confirms.

Advanced Planning and Scheduling. It is the layer that decides in what order, on which resource, and starting when work runs.