APS vs MES: What Each Does and How They Work Together
Advanced planning and scheduling (APS) software decides what the plant should make, on which resource, and in what order. A manufacturing execution system (MES) manages that work on the shop floor: it coordinates and controls production, enforces how work is done, and records what happens. APS produces the schedule; MES carries it out and reports back.
Together they form a loop. The schedule goes down to the shop floor, and actual status, such as completions, downtime, and scrap, comes back up so the next schedule starts from reality.
Eyelit Technologies publishes this guide.
What is the difference between APS and MES?
The difference between APS and MES is planning versus execution: APS works out the best feasible sequence of work against finite capacity, and MES dispatches that work, enforces how it is done, and records the result.
| APS | MES | |
| Question it answers | What should we run, where, and in what order? | What is running now, and what happened? |
| Main job | Builds a sequenced schedule against machines, tools, labor, setups, and material arrival | Releases work to operators and machines, enforces routings and checks, and records production data |
| Time horizon | Typically hours to weeks ahead, depending on the operation and its scheduling needs | The current shift, in real time |
| Main inputs | Orders, routings, resources, constraints, and current shop floor status | The schedule, work instructions, and live data from operators and equipment |
| Main outputs | A feasible production schedule and, where supported, capacity-based promise dates | Production records, WIP status, quality results, downtime, and genealogy |
| Main users | Planners and schedulers | Operators, supervisors, and quality teams |
The two depend on each other. An APS schedule built on stale shop floor data drifts from reality within a shift. An MES left to run orders as they arrive can create avoidable changeovers and leave bottlenecks idle.
How do APS and MES work together?
APS and MES work together in a closed loop: APS sends the schedule to MES, MES runs the work and records it, and those actuals flow back to APS so it can replan.
- APS publishes the schedule. Each order gets a resource, a sequence, and planned start and finish times.
- MES dispatches the work. Operators see the next job at their station, with the right instructions, materials, and checks.
- MES records what happens. Completions, scrap, downtime, and process data are captured against each order as they occur.
- Events reach APS. A machine breakdown, a quality hold, or a late material delivery changes what the plant can do.
- APS replans. It builds an updated schedule from the current status.
- The new schedule returns to MES. The shop floor works from the updated sequence.
Take a typical scenario: a press goes down at 10:00 for two hours. MES records the downtime as it occurs. Depending on available capacity, tooling, and scheduling constraints, APS can move the affected jobs to an alternate machine, reschedule lower-priority work, and recalculate the dates affected. Operators see the revised queue at their stations, and planners see which customer orders moved.
How fast this loop runs depends on the integration design. Event-driven interfaces pass production changes as they occur, while polling or scheduled exchanges introduce a delay until the next update. A shared data model keeps order, resource, and status definitions consistent, and the interface still has to deliver the right information as often as the schedule needs it.
Where do APS and MES sit in the ISA-95 model?
ISA-95 is the standard framework for how business systems connect with manufacturing operations. Level 4 covers business planning and logistics, including ERP activities. Level 3 covers manufacturing operations management, including detailed scheduling and production execution. Levels 0 to 2 cover the control systems and equipment.
MES is commonly placed at Level 3, because it manages shop-floor execution and manufacturing records. APS covers finite-capacity planning and scheduling, and where it sits depends on its scope: detailed scheduling belongs to Level 3, while longer-range planning functions connect with Level 4. In practice, the function matters more than the level. APS works out a feasible schedule, and MES manages execution and returns actual status.
For how APS fits alongside ERP and material requirements planning, see our guide to APS vs ERP vs MRP.
Does a manufacturer need APS, MES, or both?
A manufacturer needs APS when the main losses come from the schedule, MES when they come from weak control and patchy records on the shop floor, and both when the schedule keeps failing because it lacks live shop floor data.
| Situation | Usually points to |
| Late orders driven by changeovers, sequencing, or shared bottlenecks | APS |
| Planners rebuilding the schedule by hand several times a week | APS |
| Paper travelers, missing production records, or weak traceability | MES |
| WIP, downtime, and scrap that only come to light after the shift | MES |
| A schedule that is out of date by mid-shift | Both, connected |
| Promise dates that drift because sales sees planned progress, and the shop floor holds actual progress | Both, connected |
Many plants start with the system that addresses the larger loss, then add the other. The order matters less than planning the connection between them from the start.
What should you look for in how APS and MES connect?
You should look for a connection that passes shop-floor events to APS as often as the operation requires, returns updated schedules to MES in a form the shop floor can use, and keeps both systems working from consistent orders, resources, and production status.
- Data model. Shared data between APS and MES removes mapping work and keeps resource and order definitions consistent. Separate systems need an interface, and someone has to maintain it every time either side changes.
- Event timing. Check whether downtime, completions, and holds reach APS in real time or at set intervals.
- What flows each way. Schedules, sequences, and dispatch lists go down; completions, scrap, downtime, and WIP come back up.
- Replanning behavior. Check how the system handles changes to an existing schedule, including whether it can limit disruption to work already planned and how those limits are set.
- Labor and equipment data. Effectiveness data from MES gives APS realistic run rates and availability to plan against.
Single-suite and separate best-of-breed products can both work. The deciding factors are how often the plant needs to replan and how much effort the integration will take to build and maintain. For the wider set of selection criteria, see our guide on how to evaluate APS software.
How do Eyelit APS and Eyelit MES work together?
How does Eyelit connect planning and execution?
Eyelit MES and Eyelit APS run a continuous feedback loop: real-time WIP, downtime, and shop-floor changes pass from MES to APS, and updated schedules return to MES.
Eyelit Technologies provides a single platform and data model covering planning, regulatory record-keeping, and manufacturing management, in place of three separate systems.
How does Eyelit APS handle schedule changes?
Eyelit APS replans with memory: when demand or supply changes, it minimizes disruption to the existing schedule, with the degree of allowed change configurable at any level or attribute.
How does Eyelit MES control and measure production?
Eyelit MES sets standards independently for labor and for machinery through one configuration interface, and tracks Overall Labor Effectiveness (OLE) and Overall Equipment Effectiveness (OEE) against those standards in real time. Eyelit MES Asset Management tracks equipment availability and preventive maintenance within the MES, covering durables, tooling, spare parts, and calibration instruments, and Operator Certification restricts critical tasks to trained resources.
For vendor-by-vendor views, see our comparisons of the 10 best APS software platforms for manufacturers and the 10 best MES software platforms for manufacturers.
