Aggregate Planning vs MPS

Indian manufacturing worker cutting steel stock on the shop floor, representing a purchase order becoming real production material

TL;DR: Aggregate planning sets overall production, workforce and inventory targets by product category, weeks to months ahead, to balance total demand against total capacity. The master production schedule (MPS) breaks that aggregate plan down into a specific, SKU-level build schedule tied to actual dates. Confusing the two means either planning at too high a level to actually schedule production, or scheduling individual jobs with no real capacity check behind them.

This guide covers what separates aggregate planning from the master production schedule, how the two feed into each other, and why skipping straight to MPS without an aggregate plan behind it causes capacity surprises.

What Is Aggregate Planning and What Is an MPS?

Aggregate planning is the process of balancing overall demand against overall capacity, workforce and material at a product-family or category level, typically weeks to months ahead, before any individual SKU gets scheduled.

A master production schedule (MPS) takes that aggregate plan and breaks it into a specific, SKU-level build schedule, what gets produced, in what quantity, by what date, feeding directly into MRP and work orders.

The two sit at different altitudes of the same planning process. Aggregate planning answers whether there is enough capacity overall, MPS answers what exactly gets built this week.

Key Differences at a Glance

The two differ on four points that actually matter for planning:

Level of detail. Aggregate planning works at a product-family or category level; MPS works at the individual SKU level with specific quantities and dates.
Time horizon. Aggregate planning looks weeks to months ahead at overall demand and capacity; MPS is typically a shorter, rolling schedule feeding immediate production.
Output. Aggregate planning produces a capacity and workforce plan; MPS produces an actual build schedule that MRP and work orders run off.
Sequence. Aggregate planning happens first, MPS is derived from it, an MPS built without an aggregate plan behind it has no real capacity check.

Diagram of the purchase management cycle: indent, RFQ, purchase order, GRN, inward QC and payment

Where Manufacturers Get This Wrong

The same mistakes show up across manufacturing SMEs:

Skipping aggregate planning entirely. Building the MPS straight from sales orders with no category-level capacity check means the schedule can look fine on paper and still be undeliverable.
Treating MPS as a forecast. MPS should reflect confirmed orders and near-certain demand, not a rough guess, or work orders end up chasing a schedule that keeps changing.
No feedback loop from MPS back to aggregate planning. If MPS keeps missing dates, the aggregate capacity assumption behind it is probably wrong, not just the schedule.
Planning workforce and material separately. Aggregate planning needs both looked at together, machine capacity means nothing if material or labor cannot keep up.
Rebuilding the plan from scratch every cycle. Without a stable aggregate plan as the anchor, MPS gets rebuilt reactively every week instead of adjusted incrementally.

Is your production schedule built from a real capacity plan, or does the MPS just chase whatever sales orders come in that week?

TranZact’s MRP engine turns confirmed orders and your actual multi-level BOM into a real work-order schedule, so what gets built each week is grounded in actual material and capacity data, not a guess.

Book a free demo →

Aggregate Planning vs MPS in Practice

Who owns it: aggregate planning usually sits with a plant head or operations manager; MPS is typically run by a production planner or scheduler.
Update frequency: aggregate plans get revisited monthly or quarterly; MPS is often reviewed and adjusted weekly or even daily.
Input: aggregate planning starts from sales forecasts and category demand; MPS starts from confirmed orders and the aggregate plan’s capacity allocation.
Flexibility: aggregate planning can absorb demand swings by adjusting workforce or shifts; MPS has much less room to move once work orders are already released.
Manufacturer relevance: a factory running multiple product lines needs both, aggregate planning to avoid overcommitting capacity, MPS to actually execute against real dates.

How TranZact Supports Aggregate Planning and MPS

TranZact’s MRP engine generates work orders directly from confirmed sales orders and multi-level BOM data, netting material and capacity requirements across every open job, so the schedule reflects real demand instead of a manual guess.

It does not run a formal category-level aggregate planning model or set workforce headcount for you, that is a business planning decision. What it does is make sure the schedule that comes out the other end, the MPS, is grounded in real order and material data.

FAQs

What is the difference between aggregate planning and a master production schedule?

Aggregate planning balances overall demand against overall capacity at a product-family level, weeks to months ahead. The master production schedule breaks that into a specific, SKU-level build schedule with actual dates and quantities.

Does aggregate planning happen before or after the MPS?

Before. Aggregate planning sets the overall capacity and workforce allocation, and the MPS is derived from it to schedule specific SKUs within that capacity.

What happens if a manufacturer skips aggregate planning and goes straight to MPS?

The MPS can look complete on paper while having no real capacity check behind it, leading to overcommitted schedules that surface as missed dates once production actually starts.

How often should aggregate planning be revisited?

Typically monthly or quarterly, though a significant demand shift or new product line should trigger an earlier revisit rather than waiting for the next scheduled cycle.

Can MPS run without a formal aggregate plan?

It can, but it is effectively planning at the same level of detail with no upstream capacity check, which is exactly what causes overcommitted schedules in growing manufacturers.