← Latest papers
🔢 mathematics

Resource-constrained Project Scheduling with Time-of-Use Energy Tariffs and Machine States: A Logic-based Benders Decomposition Approach

This paper addresses the Resource-Constrained Project Scheduling Problem with Time-of-Use energy tariffs and machine states by proposing a Logic-Based Benders Decomposition approach that significantly outperforms monolithic methods in minimizing makespan and energy costs, while demonstrating its generalizability to other complex scheduling problems.

Original authors: Corentin Juvigny, Antonín Novák, Jan Mandík, Zdeněk Hanzálek

Published 2026-07-07
📖 5 min read🧠 Deep dive

Original authors: Corentin Juvigny, Antonín Novák, Jan Mandík, Zdeněk Hanzálek

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are the manager of a busy factory. You have a list of tasks to complete, some machines that can only do one thing at a time, and a strict set of rules about which tasks must happen before others. This is the classic "Resource-Constrained Project Scheduling Problem" (RCPSP). It's like trying to organize a massive wedding where the caterer, the band, and the venue all have limited availability, and the cake cutting can't happen before the ceremony.

But now, add a twist: Electricity prices change throughout the day.

In some hours, power is cheap (like 3 AM); in others, it's expensive (like 5 PM). Furthermore, your most energy-hungry machine (let's call it the "Big Oven") has three moods:

  1. Cooking (Proc): It's running and eating energy.
  2. Idle: It's warm but not cooking. It uses a little energy to stay ready.
  3. Off: It's cold. Turning it back on takes time and a huge burst of energy.

Your goal is to schedule every task so that you finish the job as fast as possible and spend the least amount of money on electricity. This is a balancing act: Do you run the oven during cheap hours, even if it means the whole factory waits? Or do you rush to finish early, even if it costs a fortune in peak-hour power?

The Problem: A Puzzle Too Big for One Brain

The authors of this paper tried to solve this puzzle using two traditional methods:

  • The "Monolithic" ILP: Trying to write one giant mathematical equation that accounts for every single task, every second of time, and every machine state at once. It's like trying to solve a 1,000-piece jigsaw puzzle while blindfolded, holding all the pieces in one hand.
  • The "Monolithic" CP: A different type of logic solver that is very good at scheduling but struggles when you add the complex "electricity price" rules on top.

Both methods worked okay for small puzzles, but when the factory got bigger (more tasks), they got stuck. They couldn't find the best solution in a reasonable amount of time.

The Solution: The "Master Chef" and the "Line Cook"

The authors proposed a new, smarter way called Logic-Based Benders Decomposition (LBBD). Think of this as splitting the job between two people with different skills:

  1. The Master Chef (The Master Problem): This person is an expert in money. They look at the electricity price chart and decide: "Okay, the Big Oven should be cooking during these cheap hours and resting during these expensive ones." They don't worry about which specific cake goes in the oven; they just set the schedule for the oven's "mood" (On, Idle, Off) to save money. They use a fast mathematical solver (ILP) to do this.

  2. The Line Cook (The Subproblem): This person is an expert in logistics. They take the Master Chef's oven schedule and ask: "Can we actually fit all the other tasks (the cakes, the decorations, the guests) around this oven schedule without breaking any rules?" They use a powerful logic engine (Constraint Programming) to check if the plan works.

How they talk to each other:

  • The Master Chef makes a plan.
  • The Line Cook tries to execute it.
  • If it works: Great! They check if they can do it even better.
  • If it fails: The Line Cook says, "Hey, you can't put the oven in 'Off' mode at 2 PM because the cake batter needs to be ready then!"
  • The Master Chef takes this feedback, learns from it, and makes a new plan that avoids that specific mistake.

They repeat this conversation until they find the perfect schedule.

What They Found

The authors tested this "Team Approach" against the "Solo Approach" on hundreds of different factory scenarios:

  • When the goal is purely saving money (ignoring how long the job takes): The Team Approach (LBBD) was a massive winner. It solved problems with up to 480 tasks perfectly, while the solo methods gave up or took forever. It was like having a GPS that knew exactly when to drive to avoid traffic, while the solo driver just guessed.
  • When the goal is a mix of speed and money: The Team Approach was still usually the best, especially for big, crowded factories.
  • The Exception: If the factory was very empty (few tasks) and speed was the only thing that mattered, the old "Solo Logic" method (Constraint Programming) was sometimes faster.

The "Magic Trick" (Generalization)

The most exciting part of the paper is that this "Master Chef / Line Cook" teamwork isn't just for this specific factory. The authors showed that you can use this same teamwork strategy for other types of scheduling problems, like:

  • Flexible Job Shops: Where a task can be done on any of several machines.
  • Projects with "Blocking": Where a machine is stuck waiting for a part to arrive.

In all these cases, splitting the "Energy/Money" decision from the "Task/Time" decision made the computer solve the problem much faster and find better solutions.

Summary

In simple terms, this paper says: Don't try to solve the whole energy-scheduling puzzle in one giant brain. Instead, split it up. Have one expert handle the electricity bills and another expert handle the task logistics. Let them talk to each other until they agree on the best plan. This method is faster, smarter, and can handle much bigger, more complex real-world factories than the old ways.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →