Skip to main content

Production Planning — MRP, MRP-II and APS

Production planning is the discipline of coordinating materials, capacity, labor and tooling to produce goods on time, in the right quantity, at the right cost. It sits at the intersection of ERP, supply-chain planning and shop-floor execution. The right tooling depends on production model (make-to-stock, make-to-order, configure-to-order, engineer-to-order), batch sizes, capacity bottlenecks, and how much real-time data flows back from the shop floor. For a typical US mid-market manufacturer with 100 to 500 employees and a mixed product portfolio, the answer is usually a planning module inside the ERP plus, for the capacity-constrained operations, a specialist APS tool layered on top.

This guide describes the three layers of production planning (MRP, MRP-II, APS), how production planning integrates with ERP, the capacity-planning techniques that matter in mid-market practice, the lean-manufacturing principles that have shaped modern US production culture, and the top production-planning vendors with strong US reference depth. It is written for buyers shortlisting an ERP with serious production scope, and for operations leaders evaluating whether a specialist APS investment will pay back. We treat the topic operationally because the value of production-planning software is realized on the shop floor, not in the planning office.

Three layers of production planning

Production planning splits into three layers, each addressing a different planning horizon and a different question:

MRP (Material Requirements Planning)

Calculates what materials need to be purchased or produced, in what quantity, by what date, to meet demand. Inputs: bills of material, current stock, sales orders and forecasts, lead times. Output: planned purchase orders and planned production orders. Originated in the 1960s and codified by Joseph Orlicky in 1975. Every modern ERP includes an MRP engine. Adequate for stable demand, simple bills of material and abundant capacity.

MRP-II (Manufacturing Resource Planning)

Extends MRP with capacity planning, routing, work-center loading and shop-floor control. Inputs add: routings, work-center capacity, tool availability, labor availability. Output adds: production schedules that respect capacity constraints. Codified by Oliver Wight in 1984. Modern ERPs typically include MRP-II for the production module. Adequate for capacity-aware planning when constraints are predictable.

APS (Advanced Planning and Scheduling)

Optimizes across multiple constraints simultaneously, in finer time granularity, with iterative re-planning as conditions change. Inputs add: alternative routings, alternative resources, setup-time matrices, sequence-dependent constraints, real-time shop-floor feedback. Output: optimized production schedule, often at minute-level granularity. Examples: SAP IBP and SAP PP/DS, Siemens Opcenter APS, PlanetTogether, DELMIA Quintiq, Asprova. Adequate for capacity-constrained production with complex setup dependencies.

The decision rule: if the production environment has more than three persistent capacity constraints and setup times are sequence-dependent, APS pays back. If constraints are mostly material-driven and setups are independent, MRP-II inside the ERP is usually sufficient.

Integration of production planning with ERP

Production planning in mid-market practice almost always lives inside or tightly integrated with the ERP. Three architecture patterns dominate:

Pattern 1: Production planning inside the ERP. The ERP's production module handles MRP and MRP-II planning. Bills of material, routings, work centers and shop-floor data collection all live in the ERP. No external APS. The most common pattern in the US mid-market — it works for production environments with manageable capacity-constraint complexity.

Pattern 2: ERP plus specialist APS. The ERP holds the master data and the transactional production orders; a specialist APS reads from the ERP, optimizes the schedule, and pushes the optimized plan back to the ERP. Examples: SAP S/4HANA with SAP IBP and PP/DS; Microsoft Dynamics 365 with Siemens Opcenter APS; Epicor Kinetic with its integrated Epicor APS; and ERP estates paired with PlanetTogether. Used when production-planning complexity outgrows the ERP's native capability.

Pattern 3: ERP plus MES plus APS. Three-tier architecture: ERP for commercial and material planning; MES for real-time shop-floor execution and data collection; APS for capacity optimization. Used in larger mid-market and enterprise manufacturers with high process complexity. The integration burden is significant; the value is real for environments with material capacity savings on the table.

The choice depends on production complexity, not on company size. A 200-employee machinery manufacturer with sequence-dependent setups and capacity constraints may genuinely need pattern 3; a 1,500-employee trading company with assembly operations may only need pattern 1.

Top production-planning vendors for the US market

For US mid-market manufacturers, the practical shortlist combines ERP-internal production modules with specialist APS overlays. The most-shortlisted candidates:

ERP-internal production modules

  • Oracle NetSuite — cloud-native ERP with broad mid-market adoption; production planning, work orders and demand planning in one suite.
  • Microsoft Dynamics 365 Finance & Operations (Supply Chain Management) — strong for discrete and process production at upper mid-market scale.
  • Microsoft Dynamics 365 Business Central Manufacturing — appropriate for small-business and lower mid-market manufacturers.
  • Epicor Kinetic — purpose-built for discrete mid-market manufacturing, with finite-capacity scheduling and an integrated APS module.
  • Acumatica Manufacturing Edition — cloud ERP with consumption-based pricing; popular with growing US manufacturers and distributors.
  • Infor CloudSuite Industrial (SyteLine) and Infor M3 — deep process- and discrete-industry capability across food, chemicals, fashion and industrial machinery.
  • SAP S/4HANA PP (Production Planning) — broadest scope and deepest reference base; integrates natively with SAP PP/DS for advanced planning.
  • Plex (Rockwell Automation) — cloud-native ERP/MES with real-time production monitoring and finite-capacity scheduling, common in automotive and high-volume discrete plants.
  • IFS Cloud — project-based and asset-heavy manufacturing; aerospace, defense and EPC.
  • DELMIAworks (formerly IQMS), Aptean — industry-specialist ERP/MES platforms for repetitive and process manufacturing.

Specialist APS overlays

  • SAP IBP and SAP PP/DS — SAP-native APS; integrates seamlessly with S/4HANA.
  • Siemens Opcenter APS (formerly Preactor) — vendor-agnostic, broad reference base, integrates with SAP, Dynamics, Epicor and others.
  • PlanetTogether — mid-market APS with strong integration to Microsoft Dynamics and other ERPs.
  • Asprova — APS vendor strong in discrete and high-mix manufacturing.
  • DELMIA Quintiq (Dassault Systemes) — enterprise APS for complex multi-site optimization.

Lean manufacturing and its relationship to production planning

US manufacturing culture has been shaped by lean-manufacturing principles for decades, originating in the Toyota Production System and adapted broadly across American discrete and process manufacturing. The principles directly affect production-planning software choices:

  • Pull-based production rather than push. Production starts when a customer order arrives or when downstream consumption signals demand (Kanban). MRP-based push planning is the opposite philosophy and creates inventory waste. Modern production-planning software supports both modes, but the configuration choices matter.
  • Low-inventory operations. Lean reduces buffer inventory across the value stream, which sharpens the consequences of planning errors. Strong real-time shop-floor visibility becomes essential; weak data quality becomes painful immediately rather than at month-end.
  • Continuous flow. Production runs continuously through the value stream rather than in batches. The software must support sub-day planning granularity and real-time re-planning when conditions change.
  • Leveled production (heijunka). Demand is smoothed across production cycles to enable repetitive standard work. The software must support leveling logic alongside straight capacity scheduling.
  • Standard work. Routings and work instructions are tightly defined, with variation actively suppressed. The software must enforce routing compliance and surface variation as data, not as ad-hoc deviation.

Manufacturers running lean operations sometimes find that mainstream ERP production modules are too push-oriented and that specialist lean MES tools handle shop-floor execution better. The architecture choice often combines ERP for commercial flows with a lean-friendly MES for shop-floor operations.

Capacity planning in practice

Capacity planning is where production planning either succeeds or fails operationally. Three techniques recur in US practice:

Rough-cut capacity planning. Aggregate capacity check at the work-center level, against aggregate demand forecasts. Useful for sales-and-operations planning. Most ERPs handle this in MRP-II configuration.

Detailed capacity scheduling. Finite-capacity scheduling at the operation level, respecting setup times, tool availability and labor skill matrices. Beyond what most ERP MRP-II modules handle natively; usually requires an APS overlay.

Bottleneck-focused planning. Following the Theory of Constraints, planning prioritizes the throughput of the constraining resource and accepts under-utilization elsewhere. Particularly relevant for capacity-constrained operations. APS tools handle this natively; ERP MRP-II modules require configuration discipline.

The most common failure mode in mid-market capacity planning is treating capacity as infinite during MRP runs and discovering the conflict only when the production schedule reaches the shop floor. Disciplined finite-capacity scheduling at the time of order release prevents this; it also makes order-promise dates more honest, which improves customer-service performance materially.

Related Topics