Skip to main content

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 37

Constraints, Complexity, and Model Size

Recommended resources

Hello! Welcome to the final lesson in our module on modeling complex constraints.

In our previous lessons, we've built up a sophisticated understanding of how to formulate Mixed-Integer Linear Programs (MILPs) for Flexible Job Shop Problems (FJSP), first with sequence-dependent setup times, then with transport constraints, and finally by combining both into a single, comprehensive model.

Today, we shift our focus from formulation to analysis. The learning outcome for this lesson is to analyze the impact of setup and transport constraints on problem complexity and model size. We will investigate why these realistic additions make scheduling problems notoriously difficult to solve. Understanding this is crucial, as it provides the justification for the advanced heuristic and metaheuristic methods that are central to your thesis work and that we will begin exploring in the next module.

1. The Challenge of Realism

Adding sequence-dependent setup times and transport constraints makes our models far more applicable to real-world industrial environments. However, this realism comes at a steep computational cost. These constraints don't just add a few new equations; they fundamentally change the nature and scale of the problem.

Let's break down this impact into two key areas:

  1. Problem Complexity: The growth of the search space and the inter-dependencies between decisions.
  2. Model Size: The corresponding increase in the number of variables and constraints in our mathematical formulation.

2. Impact on Problem Complexity

The core difficulty comes from a combinatorial explosion and a dense web of dependencies.

Combinatorial Explosion

A standard FJSP already involves two layers of decisions for each operation:

  • Machine Assignment (Routing): Which machine should perform this operation?
  • Operation Sequencing: In what order should operations assigned to the same machine be processed?

Adding setup and transport constraints adds new layers of decisions:

  • Sequence-Dependent Setups: The sequencing decision now has direct time and cost implications, making the order itself a critical variable, not just a matter of feasibility.
  • Transport Constraints: This can add two more decision layers:
    • Vehicle Assignment: Which transport vehicle (e.g., AGV) should move the job?
    • Vehicle Sequencing: In what order should a vehicle perform its assigned transport tasks?

Each new layer of choice doesn't just add to the complexity—it multiplies it. The total number of possible schedules grows exponentially, making an exhaustive search impossible for all but the smallest problems.

The Web of Dependencies

More importantly, these decisions are not independent. The optimal choice for one depends on the choices made for others, creating a tightly coupled system. Consider the start time of an operation . It cannot begin until a confluence of resources is available:

  • The preceding operation of the same job, , must be finished.
  • The job must be physically present at the machine, meaning its transport task is complete.
  • The assigned machine must be free, meaning the operation previously scheduled on it is finished.
  • The setup for must be completed, which can only start after the machine is free and its duration depends on the preceding operation on that machine.
  • The assigned transport vehicle must be available to bring the next job.

This creates a complex chain of dependencies that is difficult for solvers to untangle. A small delay in one transport task can ripple through the schedule, delaying multiple machines and other jobs.

Gantt Chart Illustrating Setup, Transport, and Idle Times in Scheduling
This diagram illustrates the dependencies. An operation `Oij(a)` on machine M2 can only begin after the transport is complete. Crucially, a `setup time` must also occur, and the machine may have `idle time` while waiting for these prerequisites to be met. An optimal schedule must perfectly synchronize these interacting timelines.

3. Impact on MILP Model Size

This increase in conceptual complexity translates directly into larger and more difficult MILP models.

  • Variable Inflation:

    • To model sequence-dependent setups, we need binary variables (e.g., ) to capture the precedence of every pair of operations on a given machine. For operations and machines, this can introduce a number of variables on the order of .
    • To model a fleet of transport vehicles, we need variables for vehicle assignment, start/end times of each transport task, and sequencing variables for each vehicle.
  • Constraint Inflation:

    • Every new variable requires constraints to define its behavior.
    • The classic disjunctive constraints for machine sequencing must be modified to include the setup time parameter, linking the sequencing variables to the timeline.
    • New sets of disjunctive constraints are needed for each transport vehicle.
    • Crucial linking constraints must be added to connect the production schedule with the transport schedule (e.g., an operation's processing can only start after its transport is finished: ).

This inflation in variables and constraints dramatically increases the memory required and the size of the solution space that the solver's branch-and-bound algorithm must explore.


4. Case Study: Deconstructing a Research Model

To see these impacts in a real, research-grade context, we will analyze a paper that models a highly complex system with both AGV transport and sequence-dependent setup times. This is an excellent example of the type of model relevant to your thesis.

Energy-efficient scheduling of AGV-assisted robotic flexible ...

The paper 'Energy-efficient scheduling of AGV-assisted robotic flexible flowshops under learning and processing time uncertainty' by Dehnavi et al. presents a detailed MILP for a flexible flow shop with many realistic constraints. Please study the problem description and formulation to see how these complexities are captured.

Please read Section 'Problem statement and formulation', focusing on 'Problem description' and the 'Problem assumptions'. This will define the scope. Then, review the 'Objective functions' and the 'Constraints' (Equations 8-25). You don't need to memorize every equation, but try to identify which constraints handle setups and which handle transport. Finally, look at the results in 'Table 12' of the 'Computational experiments' section.

Let's analyze what this paper reveals about complexity.

1. Model Components and Their Impact:
The model is rich with features that increase complexity:

  • Flexible Flow Shop: Multiple parallel machines at each stage.
  • AGVs: One transport vehicle between each stage.
  • Sequence-Dependent Setup Times: explicitly modeled.
  • Learning Effect: A sophisticated feature where setup times decrease with repetition, making the setup duration dependent on the entire history of operations.
  • Energy Consumption: A second objective function, which is broken down into five components (Eq. 2-7), including specific terms for setup energy (ECSM) and transport energy (ECLM and ECNM).

Each of these features requires dedicated variables and constraints, as you saw in the formulation. For example, Constraints (16), (22), (23), and (24) are all dedicated to managing the timing of the AGVs. Constraints (17) and (18) model the complex setup time with a learning effect. The model size and complexity are clearly far greater than in a simple FJSP.

2. The Proof: Computational Limits
The most telling evidence of the impact of these constraints is in the computational results. Take a close look at Table 12.

  • The authors use an exact method, AUGMECON, to solve the MILP for small problem instances.
  • For PN1 (3 jobs, 3 stages), it finds an optimal solution in 2820 seconds (~47 minutes).
  • For PN3 (7 jobs, 3 stages), the time balloons to 12,418 seconds (~3.5 hours).
  • For PN4 (10 jobs, 3 stages) and larger, the solver times out after 14,400 seconds (>4 hours) without finding a solution.

This is a stark demonstration of NP-hardness in action. Adding just a few jobs makes the problem computationally intractable for an exact solver. The combinatorial explosion driven by the complex setup and transport decisions makes it impossible to prove optimality in a reasonable timeframe. This is the primary reason why researchers (and you, for your thesis) turn to heuristics and metaheuristics like NSGA-II, which the authors also use.

Test your understanding!

Looking at Table 10 ("The dimension of 8 test problems") and Table 12, the problem PN8 is larger than PN7 only in the number of available machine and AGV speeds (L and U). However, the CPU time for NSGA-II increases from 2620s to 3340s. Why would simply adding more speed options (not more jobs or machines) increase the computational effort so significantly for a heuristic?

Show answer

This is an excellent observation. The increase in computational effort comes from the expansion of the decision space for each operation. When you increase the number of speed options from 5 to 7, you are adding more choices that the algorithm must evaluate.

For each processing operation, the algorithm must decide:

  1. Which machine to use.
  2. When to schedule it in the sequence.
  3. Which speed to use.

By increasing L and U, you are enlarging the set of possible actions for the scheduling agent (the NSGA-II algorithm). This means:

  • The chromosome representation might need to be larger or more complex to encode this choice.
  • The search space that the genetic operators (crossover, mutation) explore becomes larger.
  • Evaluating the fitness of any given schedule becomes more complex, as the algorithm has to consider the trade-offs between more speed/energy options.

Even for a heuristic that doesn't guarantee optimality, a larger and more complex search space generally requires more time to explore effectively and converge to a high-quality solution.


5. A Deeper Look at Complexity and Solution Space Structure

The size of the model is not the only factor. The very structure of the feasible region can make a problem difficult. Another research paper offers a fascinating insight into this.

Energy-Aware Double-Flexible Job Shop Scheduling with ...

The paper 'Energy-Aware Double-Flexible Job Shop Scheduling with...' by Zuccato et al. uses Constraint Programming (CP) to solve a similar problem. Let's look at their discussion of the results.

Please read Section 6.3 'Results'. Focus on the first paragraph, where the authors compare the performance of the solver on two different datasets, P (present, decomposable) and F (future, general).

The authors make a surprising discovery:

"First, and surprisingly, we can see that CPO consistently finds a schedule only for the general dataset F, but not for the present dataset P, although the latter is decomposable and involves fewer variables, constraints, and choices."

They reason that the more constrained problem (P) has a sparse and disconnected solution space, making it difficult for the solver to even find a valid starting point. The more flexible problem (F), despite having a larger search space, has a denser, more connected feasible region, making it easier for the solver to navigate.

This teaches us a valuable lesson: complexity is not just about size. The nature of the constraints and how they shape the geometry of the solution space is equally critical. Highly restrictive setup or transport rules might create a "brittle" problem that is harder to solve than a more flexible one.


Conclusion

In this lesson, we have dissected the profound impact of incorporating realistic setup and transport constraints into scheduling models. This analysis concludes our module on modeling and sets the stage for the rest of the course.

Key Takeaways:

  • Combinatorial Explosion: Setup and transport constraints add multiple layers of decisions (sequencing, vehicle assignment, etc.), causing the search space to grow exponentially.
  • Dense Dependencies: These constraints create a tightly coupled system where decisions about machines, jobs, and vehicles are all interdependent, making optimization extremely difficult.
  • Model Inflation: The conceptual complexity translates into larger MILP models with significantly more variables and constraints.
  • Intractability: As demonstrated by the case study, exact methods like MILP solvers fail to solve even moderately sized problems with these features within a practical timeframe.

Preview of the Next Module:

The intractability of exact models for complex, real-world FJSP is the primary motivation for turning to approximation methods. We cannot guarantee optimality, but we can aim to find very good solutions in a reasonable amount of time. In our next lesson, we will begin Module 8: Metaheuristics for Scheduling. We will start with the fundamental building blocks of many powerful algorithms by learning to analyze different neighborhood structures for local search.