378. Aggregate Planning

A mid-term (3–18 month) production / staffing plan that matches aggregated output to aggregated demand, deciding levels of:

Formulated as a linear program.

378.1. LP formulation

For periods 𝑡=1,,𝑇:

Variables:

Costs per unit / hire / firing:

Objective:

min𝑡(𝑐𝑃𝑃𝑡+𝑐𝑂𝑂𝑡+𝑐𝐻𝐻𝑡+𝑐𝐹𝐹𝑡+𝑐𝐼𝐼𝑡+𝑐𝐵𝐵𝑡)

Constraints (workforce balance, production capacity, inventory balance):

𝑊𝑡=𝑊𝑡1+𝐻𝑡𝐹𝑡(workforce balance)𝑃𝑡𝑘𝑊𝑡($k$ = units per worker per period)𝑂𝑡𝑜max𝑊𝑡(overtime cap)𝐼𝑡𝐵𝑡=𝐼𝑡1𝐵𝑡1+𝑃𝑡+𝑂𝑡𝐷𝑡(net inventory balance)𝐼𝑡,𝐵𝑡,𝑃𝑡,𝑂𝑡,𝐻𝑡,𝐹𝑡,𝑊𝑡0

378.2. Three pure strategies

StrategyDescriptionBest when
ChaseMatch production to demand each period; vary workforceLow inventory cost, high hire/fire flexibility, low workforce wages
LevelConstant production; let inventory + backorder absorb demand fluctuationsStable workforce, low inventory cost, low backorder cost
MixedCombination of both, plus overtime / contractReal-world; what the LP discovers automatically

Pure chase or pure level rarely optimal in practice — LP finds the right mixed strategy.

378.3. Example: monthly aggregate plan

12-month plan for a manufacturer. Demand peaks in November. Cost parameters set; LP gives:

vs pure chase (high hiring/firing): 1.5M vs pure level (high inventory): 1.4M

378.4. Connection to MRP

Aggregate planning sets the envelope — workforce, total monthly output. The detail of which specific products gets handled by:

See MPS and MRP.

378.5. Limitations

378.6. See also