Master Production Scheduling

Chapter 11
Advanced Scheduling Models and Optimization

Post Graduate Program in Production Management
Master Production Scheduling   •   Post Graduate

Advanced Scheduling Models and Optimization

Introduction

Master production scheduling (MPS) translates aggregate production intentions into time-phased decisions for specific end items, usually over weeks or days. At an advanced level, scheduling is not merely the assignment of quantities to periods. It is a constrained decision problem involving scarce capacity, material availability, sequence-dependent setups, customer priorities, uncertainty, workforce rules, inventory, overtime, subcontracting, and schedule stability.

Optimization models help planners make these trade-offs explicit. Linear programming (LP) represents divisible decisions with linear relationships; mixed-integer linear programming (MILP) adds binary or integer variables for setups, changeovers, product selection, and logical conditions. Constraint-based planning emphasizes feasibility and propagation of restrictions. The theory of constraints (TOC) focuses managerial attention on the system constraint. Multi-objective models recognize that cost minimization alone may produce unacceptable service, instability, or operational risk.

This chapter develops these approaches and shows how they support responsible managerial judgment rather than replace it.

Learning Objectives

After studying this chapter, the reader should be able to:

  1. Formulate LP and MILP models for master scheduling.
  2. Explain the role of binary variables, capacity constraints, and inventory balance.
  3. Compare optimization, constraint-based planning, and TOC.
  4. Construct multi-objective models involving cost, service, utilization, setups, and stability.
  5. Interpret schedules using bottleneck, sensitivity, and scenario analysis.
  6. Evaluate implementation, governance, data, and ethical risks.

1. Scheduling Decisions as a Mathematical System

A planning model begins by defining a finite horizon divided into periods t = 1,2,…,T. For product i, typical decisions include:

  • xit: quantity produced in period t;
  • Iit: ending inventory;
  • Bit: backlog or late demand;
  • ot: overtime hours;
  • yit: binary setup or production-activation variable;
  • sijt: binary indication that product j follows product i in a sequence.

A fundamental inventory balance is:

Ii,t-1 + xit + rit - dit = Iit + Bit - Bi,t-1

Here, dit is demand, rit is scheduled receipt from an external source, and inventory and backlog are measured in units. The equation assumes that production, receipts, demand, inventory, and backlog are represented in the same unit and that demand occurs within the period according to the chosen timing convention. If shortages are not permitted, set Bit=0.

Capacity may be represented by:

∑i aimxit ≤ Cmt + omt for every resource m and period t

where aim is the processing time per unit of product i on resource m, Cmt is regular available capacity, and omt is overtime. Units must be consistent: if processing time is hours per unit, all capacity terms must be hours.

A common cost objective is:

min Z = ∑t∑i (cpi xit + hi Iit + pi Bit) + ∑t∑m comtomt + ∑t∑i fi yit

The parameters represent production cost, inventory-holding cost, backlog penalty, overtime cost, and setup or activation cost. This objective is applicable when costs can reasonably be approximated as additive and linear. It does not automatically capture customer segmentation, risk, sequence-dependent setups, or nonlinear learning effects.

2. Linear Programming for Aggregate MPS

LP is appropriate when quantities are divisible or sufficiently large that fractional solutions can be rounded without material operational damage. It is particularly useful for medium-term MPS decisions such as regular production, overtime, inventory, subcontracting, and workforce capacity.

Worked Example: A Two-Product Capacity Plan

An illustrative factory produces products A and B over two periods. Demand is:

PeriodDemand ADemand BRegular capacity
18060160 hours
210090160 hours

Each A requires 1 hour and each B requires 1.5 hours. Initial inventory is zero, and ending inventory is required to be zero. The plant can use 20 overtime hours per period. Let production costs be £10 for A and £12 for B, holding cost £1 per unit-period, and overtime £25 per hour.

The period-1 requirement is 80(1)+60(1.5)=170 hours, exceeding regular capacity by 10 hours. Period 2 requires 100(1)+90(1.5)=235 hours, exceeding regular plus available overtime capacity of 180 hours. Therefore, the stated demand cannot be met without subcontracting, additional capacity, inventory carried from an earlier period, or revised due dates. This feasibility test is important: an optimizer cannot create capacity that does not exist.

Suppose subcontracting is available at £30 per A-hour equivalent and £35 per B-hour equivalent. The model can decide which demand to subcontract by adding variables [[MATH,q_{it}]] and the balance equation:

Ii,t-1+xit+qit-dit=Iit

Because B consumes more capacity and may have a different margin, the optimal plan depends on all costs, capacity, and service constraints. The managerial lesson is more important than a particular numerical solution: feasibility, cost, and customer policy must be modelled together.

3. Mixed-Integer Linear Programming

Many scheduling decisions are indivisible. A machine is either set up or not; a product is either selected for a run or not; a customer order may be accepted or rejected. MILP extends LP through integer and binary variables.

Linking Production and Setup

If product i can be produced in period t only when a setup occurs, use:

xit ≤ Mityit

where yit∈{0,1} and Mit is a valid upper bound on production. A tighter bound is preferable because an unnecessarily large “big M” weakens the computational relaxation and may cause numerical difficulty. A capacity-based bound such as Mit=Cmt/aim may be used when resource m is limiting.

If a minimum run size [[MATH=L_i]] applies:

Li yit ≤ xit ≤ Mityit

This formulation prevents uneconomically small production runs. It also demonstrates a limitation: if demand is smaller than the minimum run, the model may create excess inventory unless an end-of-horizon or disposal rule is included.

Setup Capacity

If a setup consumes [[MATH,?]] setup time [[MATH,σ_i]] and production consumes ai xit, then:

∑i (ai xit+σi yit) ≤ Ct

This is valid when setup time depends only on whether product i is produced, not on the preceding product. If setup depends on the sequence, pairwise transition variables are needed. For example, sijt=1 can indicate that i is followed by j, with transition time τij. The resulting formulation must also include sequencing and subtour-elimination constraints; merely adding transition costs without enforcing a valid sequence is incorrect.

Lot Sizing and Fixed Charges

MILP is valuable for lot-sizing because fixed setup costs create economies of scale. However, the resulting model may be computationally difficult. Model size, horizon length, product count, and sequence detail should match the decision horizon. A strategic or tactical MPS may use aggregate setup approximations, while a short-term finite-capacity schedule may require detailed sequence variables.

4. Constraint-Based Planning and Feasibility

Constraint-based planning represents restrictions directly rather than primarily expressing a monetary objective. Constraints may include:

  • precedence: operation B cannot begin before operation A;
  • release dates and due dates;
  • machine eligibility;
  • labor qualifications;
  • campaign or family sequencing;
  • maintenance windows;
  • material-availability dates;
  • calendar and shift rules.

A precedence relation can be expressed as:

Sj ≥ Si + pi

where Si is the start time of operation i and pi is its processing duration. The assumption is that operation j cannot start until i is complete. For non-overlap on a single machine, a binary order variable zij can be used:

Sj ≥ Si+pi−M(1−zij)
Si ≥ Sj+pj−Mzij

Exactly one ordering must hold for two operations. The value of M must be a valid time upper bound, not an arbitrary enormous number.

Constraint programming (CP) often uses specialized propagation and global constraints, such as cumulative-resource and no-overlap constraints. It can be highly effective for complex sequencing, calendars, and logical rules, especially when feasibility is more important than a smooth cost function. MILP and CP can also be hybridized: CP may construct a feasible sequence, while MILP evaluates inventory, sourcing, or financial consequences.

5. Theory of Constraints

The theory of constraints views every system as having at least one constraint that limits throughput. The classic five focusing steps are:

  1. Identify the constraint.
  2. Exploit it using existing resources and better priorities.
  3. Subordinate other activities to the constraint’s requirements.
  4. Elevate the constraint by adding capacity or changing technology.
  5. If the constraint moves, return to step 1.

A bottleneck is not simply the resource with the highest percentage utilization. It is the resource that constrains system throughput under the relevant product mix and demand conditions. A highly utilized non-bottleneck may have little economic value if increasing its capacity does not increase finished-goods output.

TOC complements optimization. An MILP may recommend overtime on a non-bottleneck because of a local cost trade-off, whereas TOC asks whether that action improves flow through the constraint. The strongest practice is to use TOC to frame the managerial problem and optimization to quantify alternatives.

6. Multi-Objective Scheduling Models

Production schedules commonly pursue conflicting objectives:

  • minimize production, inventory, overtime, and setup cost;
  • maximize on-time delivery and service level;
  • improve bottleneck utilization;
  • minimize changeovers;
  • reduce schedule nervousness;
  • protect safety stock and strategic customers.

A weighted-sum model may be written as:

min Z = wc C + ws S + wu U + wk K + wn N

where C is normalized cost, S is a service penalty, U is underutilization or bottleneck loss, K is setup burden, N is schedule instability, and the w values are nonnegative weights. Normalization is essential because pounds, hours, percentages, and service violations cannot be meaningfully weighted in raw units. For a metric X, a simple normalization is:

XN = (X−Xmin)/(Xmax−Xmin)

The bounds must be credible and consistent across scenarios.

An alternative is the ε-constraint method: optimize one primary objective while imposing limits on others, for example:

min Cost
subject to On-time deliveries ≥ 98%
Setups ≤ 24
Schedule deviation ≤ 40 hours

This approach is often more interpretable for managers because service and stability become explicit policy constraints. A Pareto frontier contains solutions for which improving one objective would worsen at least one other objective. It helps decision-makers understand trade-offs rather than treating arbitrary weights as objective truth.

Schedule Stability

If a previous plan is x0it, a linear deviation measure is:

xit−x0it=d^+it−d^-it

with d^+it,d^-it≥0, and the objective can penalize d^+it+d^-it. This measures absolute quantity changes. If changes in the timing of setups are more disruptive, setup-change variables or frozen-zone constraints may be more appropriate. Stability is not identical to optimality: excessive freezing may preserve a poor plan, while excessive replanning damages execution.

7. Uncertainty, Robustness, and Rolling Horizons

Demand, yield, processing time, supplier reliability, and machine availability are uncertain. A deterministic schedule may be optimal only for one forecast. Practical responses include:

  • scenario analysis using optimistic, base, and pessimistic demand;
  • safety capacity and time buffers;
  • robust optimization, which protects against specified deviations;
  • stochastic programming, which models scenarios and probabilities;
  • rolling-horizon reoptimization, in which the near-term plan is frozen and the later horizon is replanned.

A schedule should be evaluated not only by expected cost but also by worst-case service, feasibility, and recovery effort. Probabilities should be evidence-based; unsupported probabilities create false precision.

8. Detailed Illustrative Case: Northstar Medical Devices

Background

Northstar manufactures three sterilizable device families on two assembly lines. Demand is uneven, setups are family-dependent, and regulatory release requires completed lots to remain identifiable. Line 1 is certified for all families; Line 2 is certified only for A and B. The company has promised 95% on-time delivery but has experienced frequent schedule changes.

Problem

The planning team minimizes manufacturing cost alone. The resulting plan uses long campaigns of the lowest-cost family, delays a high-priority family, and repeatedly changes the next week’s schedule when new orders arrive. Managers suspect that Line 1 is the true constraint, but utilization reports show Line 2 at 92% and Line 1 at 84%.

Analysis

A cross-functional team builds an MILP with production, inventory, backlog, overtime, family setup, line eligibility, and frozen-zone variables. It adds a service constraint requiring at least 95% of weighted demand to be delivered on time. A stability penalty limits changes from the published schedule. The team also maps material-release and inspection times, because capacity on an assembly line is irrelevant if product cannot be released.

TOC analysis identifies the sterilization-and-release cell, not Line 2, as the system constraint. A high Line 2 utilization is misleading because that line produces items that accumulate before the constrained release step. The revised model therefore gives priority to products that maximize throughput through the constrained cell, while avoiding unnecessary release of work-in-process.

Approach and Solution

Three scenarios are compared:

PolicyCost indexOn-time deliverySetupsSchedule changes
Cost-only MILP10088%18High
Service-constrained MILP10696%22Medium
Multi-objective plus TOC rules10997%20Low

The indices are illustrative rather than empirical. The third policy accepts a modest cost increase to protect service, reduce unstable changes, and prevent excess work-in-process before the constraint. The solution also establishes a frozen two-week zone, a weekly constraint review, and escalation rules for late materials.

Outcome and Learning Points

The case illustrates five principles. First, an objective function expresses policy, not merely mathematics. Second, local utilization is not equivalent to system throughput. Third, stability has economic value because frequent changes cause expediting, labor disruption, and quality risk. Fourth, regulatory and release constraints must be represented explicitly. Finally, a model should produce transparent alternatives that managers can challenge, not an unexplained single answer.

9. Implementation, Technology, and Governance

Successful advanced scheduling depends on data quality as much as algorithmic sophistication. Essential data include reliable routings, standard times, setup matrices, calendars, order priorities, inventory records, material lead times, and actual downtime. Master-data governance should assign ownership, approval, effective dates, and audit trails.

Scheduling applications may combine ERP/MRP data, finite-capacity engines, optimization solvers, dashboards, and machine data. AI and machine learning can improve demand forecasts, predict downtime, estimate processing times, or recommend parameter updates. However, predictive accuracy does not guarantee a feasible schedule. AI-generated recommendations require constraint validation, explainability, human approval, and monitoring for drift.

Governance issues include:

  • customer-priority rules that may unfairly disadvantage smaller customers;
  • labor schedules that create unsafe or inequitable workloads;
  • opaque algorithmic decisions that cannot be audited;
  • excessive surveillance of workers through real-time productivity data;
  • inappropriate use of personal or supplier-confidential information.

A responsible system records assumptions, model version, data timestamp, solver status, overrides, and reasons for manual intervention. Infeasibility should be reported explicitly through an infeasibility analysis or relaxation report; silently violating constraints is unacceptable.

10. Model Validation and Managerial Interpretation

Validation should occur at four levels:

  1. Structural validation: equations represent the intended business rules.
  2. Data validation: units, calendars, routings, and demand are correct.
  3. Extreme-case testing: test zero demand, full capacity, no overtime, and impossible due dates.
  4. Operational validation: planners and supervisors confirm that the schedule can be executed.

Important outputs include objective value, service level, bottleneck load, inventory profile, setup count, overtime, backlog, and shadow prices where meaningful. A shadow price estimates the marginal objective improvement from one additional unit of a constrained resource within the model’s local range. It should not be interpreted beyond that range or treated as a guaranteed market value.

Managers should ask: Which assumptions drive the result? What happens if demand is 10% higher? Which constraint is binding? What is the cost of service improvement? How much schedule flexibility remains? These questions convert optimization into informed decision-making.

Challenges and Limitations

Advanced models have important limitations. Linear costs may misrepresent real negotiations and nonlinear labor effects. Forecast uncertainty can dominate optimization precision. Large MILPs may require long computation times or yield only a bound rather than a proven optimum. Poorly chosen big-M values can weaken models. Overly detailed models become difficult to maintain, while overly aggregated models hide sequence and labor realities.

Optimization can also encourage local efficiency if system boundaries are incomplete. A plan that minimizes factory cost may increase transport, supplier risk, or customer disruption. Therefore, model boundaries should reflect the decision’s economic and operational consequences.

Best-Practice Framework

A robust advanced scheduling process should:

  1. define the decision horizon, granularity, and frozen zones;
  2. establish product, resource, material, and service data ownership;
  3. test feasibility before optimizing cost;
  4. use LP for divisible planning and MILP/CP for discrete logic;
  5. identify the system constraint using flow analysis, not utilization alone;
  6. normalize multi-objective measures and expose Pareto trade-offs;
  7. test scenarios and recovery policies;
  8. validate schedules with operators and supervisors;
  9. preserve auditability and explain manual overrides;
  10. measure realized service, stability, throughput, and constraint performance after implementation.

Chapter Summary

Advanced master production scheduling treats production decisions as a constrained system rather than an isolated quantity plan. LP models support divisible production, inventory, overtime, and sourcing decisions. MILP adds setups, minimum runs, product activation, and other discrete logic. Constraint-based planning is powerful for precedence, calendars, eligibility, and sequencing. TOC directs attention to the resource that limits total throughput, while optimization quantifies cost and service alternatives.

Multi-objective models make trade-offs among cost, service, utilization, setups, and schedule stability explicit. Weighted objectives require careful normalization; ε-constraint and Pareto approaches often provide clearer managerial interpretation. Uncertainty requires scenarios, buffers, robust methods, or rolling horizons. Implementation depends on valid data, transparent governance, operational validation, and responsible use of technology. The best schedule is not necessarily the mathematical minimum-cost schedule; it is a feasible, explainable, resilient plan aligned with system throughput and organizational priorities.

Key Terms

Linear programming: Optimization with continuous variables and linear relationships.

Mixed-integer linear programming: Linear optimization containing integer or binary variables.

Binary variable: A variable restricted to 0 or 1.

Big M: A sufficiently large valid constant used to model conditional logic.

Lot sizing: Determining production quantities and timing, often with fixed setup costs.

Setup time: Time required to prepare a resource for a product or family.

Sequence-dependent setup: Setup whose duration depends on the preceding and succeeding products.

Constraint programming: A method that represents and propagates feasibility restrictions.

Precedence constraint: A rule requiring one activity to occur before another.

Theory of constraints: A management approach focused on identifying and exploiting the system constraint.

Bottleneck: A resource or process limiting system throughput.

Multi-objective optimization: Optimization involving two or more potentially conflicting objectives.

Weighted-sum model: A model combining normalized objectives using importance weights.

ε-constraint method: Optimization of one objective subject to limits on others.

Pareto frontier: Set of non-dominated trade-off solutions.

Schedule stability: Resistance of a published plan to disruptive changes.

Rolling horizon: Repeated replanning in which the near-term plan is progressively executed or frozen.

Shadow price: Marginal value of relaxing a binding constraint within a valid local range.

Infeasibility: A condition in which no solution satisfies all model constraints.

Model governance: Controls for data, assumptions, versions, overrides, and accountability.

Review Questions

Short Answer Questions

  1. What is the purpose of an inventory-balance equation in an MPS model?
  2. Why are binary variables needed for setup decisions?
  3. Distinguish a bottleneck from a highly utilized resource.
  4. What is the purpose of normalizing objectives in a weighted-sum model?
  5. State two advantages of rolling-horizon scheduling.

Long Answer Questions

  1. Explain how an MILP can represent setup costs, minimum run sizes, and capacity limitations.
  2. Compare LP, MILP, and constraint programming for advanced production scheduling.
  3. Explain the five focusing steps of the theory of constraints and their relationship to optimization.
  4. Discuss how service, cost, setup, and stability objectives can conflict in an MPS.
  5. Evaluate the data, governance, and human factors required to implement an advanced scheduling system.

Analytical / Application Questions

  1. A plant has regular capacity of 120 hours and overtime capacity of 20 hours. Product A requires 1 hour per unit and demand is 100 units; product B requires 2 hours per unit and demand is 30 units. Determine whether all demand can be produced internally and explain one managerial response if it cannot.
  2. A schedule has lower cost but 88% on-time delivery, while another costs 6% more and achieves 96% on-time delivery with fewer schedule changes. Design an ε-constraint or weighted-sum policy and justify the required data and assumptions.
  3. Utilization of a finishing cell is 95%, but the cell’s output is frequently waiting for a sterilization process. Analyze which process is likely to be the system constraint and propose two scheduling actions using TOC principles.

Multiple Choice Questions with Answers

Question 1

Which variable most directly represents a binary setup decision?

A. x_{it}

B. I_{it}

C. y_{it}

D. d_{it}

Correct Answer: C. y_{it}

Question 2

In the inventory balance, what does d_{it} normally represent?

A. Demand in period t

B. Setup time

C. Overtime capacity

D. Production cost

Correct Answer: A. Demand in period t

Question 3

Why should a big-M value be as tight as valid bounds permit?

A. It guarantees zero inventory

B. It strengthens computational performance and numerical reliability

C. It eliminates all integer variables

D. It converts MILP into LP

Correct Answer: B. It strengthens computational performance and numerical reliability

Question 4

Which method is especially focused on precedence, calendars, and complex feasibility rules?

A. Constraint programming

B. Simple exponential smoothing

C. Economic order quantity only

D. Financial ratio analysis

Correct Answer: A. Constraint programming

Question 5

According to the theory of constraints, what should managers do first?

A. Increase every machine’s utilization

B. Identify the system constraint

C. Maximize finished-goods inventory

D. Eliminate all setups

Correct Answer: B. Identify the system constraint

Question 6

What is a key requirement when combining objectives with a weighted sum?

A. All objectives must have identical units

B. Objectives should be normalized appropriately

C. All weights must be negative

D. Constraints must be removed

Correct Answer: B. Objectives should be normalized appropriately

Question 7

The ε-constraint method typically does what?

A. Removes service requirements

B. Optimizes one objective while limiting other objectives

C. Allows every constraint to be violated

D. Uses only continuous variables

Correct Answer: B. Optimizes one objective while limiting other objectives

Question 8

If regular capacity is 100 hours, overtime is 20 hours, and required processing is 135 hours, how many hours must be covered by another action?

A. 5 hours

B. 15 hours

C. 20 hours

D. 35 hours

Correct Answer: A. 5 hours

Question 9

What does a Pareto solution mean?

A. It is always the cheapest solution

B. It violates at least one hard constraint

C. No objective can improve without worsening at least one other objective

D. It contains no binary variables

Correct Answer: C. No objective can improve without worsening at least one other objective

Question 10

Which practice best supports responsible scheduling governance?

A. Hide manual overrides

B. Use unexplained algorithmic priorities

C. Record assumptions, model versions, and override reasons

D. Ignore infeasibility reports

Correct Answer: C. Record assumptions, model versions, and override reasons

Master Production Scheduling
Chapter 11 of 15