APS (Advanced Planning and Scheduling) is the software category that generates production plans and schedules, from short to long term, taking the real constraints of the plant into account — finite capacity, setups, calendars, precedences and materials. It is what turns a production requirement into a sequence the plant can actually deliver, doing so in a way that serves the company's goals, such as efficiency and service level.
It was still in the 1990s that the limitation became clear and the concept of Finite Capacity Scheduling (FCS) emerged, later evolving into APS. Both appeared for the same reason: to manage finite capacity, queues, routings and the synchronization between operations — exactly what none of the earlier systems did. The difference between them is scope: FCS was born focused on sequencing the short term; APS extended the same finite-capacity logic to the medium and long term, adding scenario simulation. Hence the name carrying both Planning and Scheduling.
A little history helps, because it explains the name. The first enterprise system built for manufacturing was neither financial nor commercial: it was MRP (Material Requirements Planning), created in the 1960s by Joseph Orlicky and Oliver Wight to calculate what to make and what to buy, exploding requirements down the levels of the bill of materials using standard replenishment lead times. The 1980s brought MRP II, and with it the awareness that capacity matters: enter the Master Production Schedule (MPS), RCCP to validate the bottleneck and CRP to walk every operation in the routing — what most plants still know today as machine loading. The ERPs of the 1990s integrated the company's functions, but inherited the same calculation logic.
Every manufacturer with an ERP already calculates material requirements. The problem is how that calculation is done: traditional MRP assumes infinite capacity and fixed lead times. It tells you that you need 5,000 units in week 12, but never asks whether the machines can cope, whether the setup between two products costs four hours, or whether the required mould is already in use. MRP II and the capacity calculations that followed (RCCP and CRP) improved the diagnosis — they flag that week 12 is overloaded — but they still don't solve it: they don't replan, they only warn.
That is precisely the gap APS fills. Instead of calculating and warning, it decides within the constraint: it fits each order onto the resource and the moment where it actually fits, respecting everything the plant has in reality. You will find the same category under other names — finite scheduling systems, detailed production planning software or Advanced Planning Systems.
In one sentence: MRP calculates what is missing; APS decides how to produce it with the resources that exist — and decides what will and will not fit.
A note on scope: APS is the technology; Supply Chain Planning is the broader business process it supports. Gartner, in fact, positions detailed production scheduling inside the SCP umbrella.
There is a common confusion: many people associate APS with shop-floor scheduling only. The first versions of the category really did just that, and the name stuck to scheduling. A complete APS, however, covers considerably more — and also leaves things out on purpose. Click each process to see the role APS plays in it.
It starts from the volumes set in the MPS — or straight from the order book, in make-to-order plants — and defines when and, above all, how each demand will be produced: which resource, in which sequence, on which shift.
This is the reason the category exists. Here every operation needed to manufacture the product is scheduled (or at least the bottleneck ones), applying the minimum, multiple and maximum lot sizes the plant allows.
Siemens Opcenter APSDecisions measured in years: whether to buy a machine, open a shift, change the footprint. APS does not run this planning, but it feeds the decision with capacity simulation.
A 20% demand increase does not mean 20% more capacity. Seeing seasonality, mix, holidays and shifts over time can prevent buying a multi-million asset that would sit idle — or stop an undersized purchase.
Consultoria NEOActual and/or forecast demand per period is the starting point of all planning. Alongside it come the inventory and service policies for each product.
APS consumes this signal, it does not produce it. Make-to-stock plants depend more on the policies; make-to-order plants still need to plan — only the origin of demand changes.
nPlanIn the S&OP horizon, APS works by product family and looks only at the most critical constraints. The goal is not to detail the shift, it is to see how much capacity the forecast volume will consume and whether action is needed — change capacity or revisit the sales plan.
By definition S&OP precedes the MPS, but because the whole dynamic of APS is built on scenario generation and capacity management, it strongly supports collaborative planning — precisely where uncertainty is highest.
nPlanDefines what to produce in each period and in what quantity, by SKU, over a horizon tied to the longest cumulative supply lead time. It then explodes that demand down the levels of the bill of materials — finished goods, work in process, raw material.
Here APS already considers more constraints than in S&OP. It is also the point that suffers most when S&OP delivers only an aggregate plan: without the real mix, operations has to infer assumptions.
nPlanThe short cycle that revises the master schedule within the month, usually on a weekly cadence: what changed in actual demand, what slipped in supply, what broke in the plant — and how to replan without breaking the commitment made in S&OP.
This is where APS proves itself day to day. A monthly plan starts ageing in the first week, and the value of the tool lies less in producing the perfect plan at month-end and more in regenerating a feasible plan in minutes when reality shifts. With demand volatility and SKU proliferation, S&OE is no longer exclusive to make-to-order: it has become critical for make-to-stock too.
Material requirements calculation still exists — but connected to a production plan that respects capacity, instead of running in isolation on unrealistic assumptions.
It is the difference between a purchasing plan that reflects what the plant will actually produce and one that reflects what the system wishes it would produce. We cover it in What is MRP?
nPlanRCCP (rough-cut capacity) and CRP (detailed capacity) are the classic MRP II load calculations: they compare requirements against available capacity and flag overload.
APS makes both redundant because it does not separate calculation from decision: instead of generating a plan and then checking whether it fits, it generates the plan inside the capacity that exists.
Siemens Opcenter APSPlans the replenishment of distribution centers from the demand at each point — and has to be connected to the production and inventory plans to work.
It is not a typical function of a plant APS, but it talks to it directly: what the DCs request becomes demand for the MPS. See What is DRP?
nPlanProduction reporting, quality control, traceability and OEE are MES territory, not APS. But the boundary is one of intense collaboration, not separation: the schedule that comes out of APS is precisely the list of orders to produce, in which sequence and on which resource — exactly what MES needs to receive in order to direct the shop floor.
And the flow runs both ways: the feedback from execution — what was reported, what slipped, what broke — feeds back into APS and allows fast rescheduling when needed. Without that feedback, the schedule ages within the first shift. They are complementary systems, not competing ones: APS decides the sequence, MES executes and measures it.
↔ APSScheduling starts from the volumes set in the MPS — or straight from the order book, in make-to-order plants — to define precisely when and, the critical part, how each demand will be produced. Every operation needed to manufacture the product is scheduled, or at least the bottleneck ones where those are clear.
What gets scheduled is the scheduling object — usually the production order. And it is not merely a mirror of the net requirement coming from MPS or MRP: the plant's minimum, multiple and maximum lot policies are applied to it. The MPS may ask for 5,000 units while the plant produces in batches of 1,200.
For scheduling to be reliable, APS needs five families of information — and this is where most projects are won or lost:
This last family deserves unpacking, because it is the subtlest one and the one that moves lead time the most — and it shows that in manufacturing, the order of the factors does change the product. If only every plant could be served by a simple Gantt: the logic of precedence between operations is vital, but it is almost never the same in every case.
Does the next operation have to wait for the whole batch to finish, or can it start earlier? Picture a table factory where tops are moved to assembly in trolleys of six: as soon as six tops are ready, they move on — even if the order is for 50 tables. That transfer quantity may be the internal handling unit (trolley, pallet, box), it may be piece by piece (equal to 1), or it may be null, when the process forces you to wait for the full quantity of the previous operation.
Some waits are required by the process: transport between departments or plants, curing, drying, cooling. In a furniture plant, assembling a table may be forbidden until eight hours after painting ends, on pain of a quality defect. In metalworking, the classic case is heat treatment — the parts come out far too hot to move on.
The mirror of the previous case, and the most overlooked: there is a maximum time to start the next step, or you lose the material or the quality. A dough that rests too long, a bath that cools, a compound that reacts outside its window. In pharma, food and chemicals, this type of rule is often more binding than the machine capacity itself — and it is what a spreadsheet cannot guarantee.
Scheduling close to a shift break requires knowing whether the operation can stop midway. A dyeing cycle cannot: it would be like interrupting a load of laundry to go out and resuming it later expecting the same result. Either it starts and finishes within the available window, or it does not start. The scheduling literature calls this preemptive (can be paused and resumed) and non-preemptive (cannot).
Chaining does not happen only inside a routing: assembly can only start once every component converges, and a delay in a sub-assembly three levels down has to propagate upward. This is where the difference between spreadsheet and APS stops being convenience and becomes capability: tracing the link between demand and order, and between order and raw material, level by level, is unfeasible by hand in any reasonably deep structure. This is also where a dependency is created (an optional simulation capability in an APS) to synchronize operations with material availability, along with the ability to decide who consumes which material when there is not enough for everyone.
An APS has to consider all of these rules automatically when scheduling — and if someone breaks them in a manual change, at the very least warn.
Before choosing a rule or a tool, it pays to recognize the terrain. The scheduling literature — Michael Pinedo being the most approachable reference — describes a scheduling problem through three elements: the resources that receive the schedule, the operations to sequence with their conditions, and the objective you want to optimize. The first one already changes everything:
Single machine is the trivial case. Parallel machines already require deciding where, and the difficulty shifts depending on whether speeds are identical, different but fixed, or different by product. Flow shop is line production, with continuous flow and order generally preserved. Job shop is functional production: each product has its own routing across different machines.
The second lens, more practical than academic, is the demand response strategy — and it determines where the pain sits and therefore what APS has to solve first:
Food, pharma, pulp and paper, continuous processes
Pain in inventory volume and cost, stockouts and efficiency with a varied mix. Attention starts in planning — but rising volatility has made S&OE critical here too.
Automotive, glass, serial machinery
Work-in-process inventory, delivery promises complicated by configuration options, and losses from mix changes. Needs strong planning and scheduling at the same time.
Packaging, footwear, textiles, metalworking, electronics
Delivery promises made hard by the backlog, lead time as a competitive factor, heavy WIP and setups rising with SKU variety. Gains the most from agile scheduling.
Steel structures, heavy machinery, tooling shops, aerospace
Long and competitive lead times, complex material management (bought alongside the project or anticipated empirically) and efficiency that still matters, even with lower expectations.
This explains why two APS projects in the same city, running the same software, end up with such different scopes. And why an honest diagnosis of environment and response strategy is worth more, at the outset, than any vendor comparison.
It is worth being blunt, because the wrong expectation is the main cause of frustration in an APS project. In planning, the gain comes from defining well what to produce in each period and, just as importantly, what will not be possible to produce for lack of capacity — which avoids overstock and stockouts at the same time, and allows medium and long-term capacity adjustments before buying an asset. Some APS products on the market can produce a Master Production Schedule (MPS), but that is only advisable in fairly specific cases, usually in an MTO or ETO environment. When more factors have to be weighed to generate a medium to long-term production plan — demand, inventory health, distribution — a dedicated production planning solution is the better choice. In scheduling, the gain comes from advanced sequencing rules: less setup, less waiting, more productivity, with shorter lead times and less work in process thanks to better synchronization.
What it does not do: it does not execute production (that is MES), it does not fix bad process data, it does not replace management judgment and it does not create capacity that isn't there. A well-implemented APS makes the problem visible and negotiable — it does not make it disappear.
The motivation changes depending on who comes looking, but it converges on the same place. For the board and C-level, it is cost reduction and revenue growth. For middle management, it is service level, efficiency, lead time and inventory. For planning analysts and coordinators — where the initiative most often starts — it is the time spent scheduling and, above all, rescheduling, with a result not even they consider good.
And, being honest about the opposite: it is not worth it if the operation has few items, simple routings, a single relevant resource, negligible setups and stable demand. In that scenario a well-built spreadsheet does the job, and an APS only adds cost and complexity. APS pays for itself where at least one of the following is present: variety, constraint and volatility — in other words, when the number of possible decisions exceeds what one person can evaluate in time.
NEO is a global reference in Siemens Opcenter APS — more than 120 manufacturers plan with us, from diagnosis to go-live.
TALK TO A SPECIALISTOPCENTER APSGUIDE: WHAT IS SCPAPS stands for Advanced Planning and Scheduling. It is the software category that generates production plans and schedules while respecting finite capacity and the other real constraints of the plant.
MRP calculates material requirements assuming infinite capacity and fixed lead times. APS decides within the constraint: it sequences orders on the resources that exist, considering setups, calendars and precedences — and shows what does not fit.
No. The ERP remains the transactional system — master data, orders, costs, purchasing. APS is the decision layer that connects to it: it reads demand and bills of materials, and returns the plan and the sequence.
Not necessarily. APS needs reliable process data, and MES is a good source — but not the only one. Waiting for the MES tends to postpone by years a planning gain that would already be available.
It is the same product, renamed: Preactor was acquired by Siemens in 2013 and became Opcenter APS. Long-standing users still know the solution by the Preactor name.
No. SCP is the business process that plans demand, inventory, production, supply and distribution. APS is part of the technology stack that enables SCP — especially from the master schedule layers downward.