Drools Planner is a lightweight, embeddable planning engine that optimizes planning problems. It solves use cases, such as:
Employee shift rostering: timetabling nurses, repairmen, ...
Agenda scheduling: scheduling meetings, appointments, maintenance jobs, advertisements, ...
Educational timetabling: scheduling lessons, courses, exams, conference presentations, ...
Vehicle routing: planning vehicles (trucks, trains, boats, airplanes, ...) with freight and/or people
Bin packing: filling containers, trucks, ships and storage warehouses, but also cloud computers nodes, ...
Job shop scheduling: planning car assembly lines, machine queue planning, workforce task planning, ...
Cutting stock: minimizing waste while cutting paper, steel, carpet, ...
Sport scheduling: planning football leagues, baseball leagues, ...
Financial optimization: investment portfolio optimization, risk spreading, ...
Every organization faces planning problems: provide products and services with a limited set of constrained resources (employees, assets, time and money).
Drools Planner helps normal JavaTM programmers solve planning problems efficiently. Under the hood, it combines optimization heuristics and metaheuristics with very efficient score calculation.
Drools Planner, like the rest of Drools, is business-friendly open source software under the Apache Software License 2.0 (layman's explanation). It is 100% pure JavaTM and runs on any JVM.
All the use cases above are probably NP-complete. In layman's terms, this means:
It's easy to verify a given solution to a problem in reasonable time.
There is no silver bullet to find the optimal solution of a problem in reasonable time (*).
Note
(*) At least, none of the smartest computer scientists in the world have found such a silver bullet yet. But if they find one for 1 NP-complete problem, it will work for every NP-complete problem.
In fact, there's a $ 1,000,000 reward for anyone that proves if such a silver bullet actually exists or not.
The implication of this is pretty dire: solving your problem is probably harder than you anticipated, because the 2 common techniques won't suffice:
A brute force algorithm (even a smarter variant) will take too long.
A quick algorithm, for example in bin packing, putting in the largest items first, will return a solution that is usually far from optimal.
By using advanced optimization algorithms, Planner does find a good solution in reasonable time for such planning problems.
Usually, a planning problem has at least 2 levels of constraints:
A (negative) hard constraint must not be broken. For example: 1 teacher can not teach 2 different lessons at the same time.
A (negative) soft constraint should not be broken if it can be avoided. For example: Teacher A does not like to teach on Friday afternoon.
Some problems have positive constraints too:
A positive soft constraint (or reward) should be fulfilled if possible. For example: Teacher B likes to teach on Monday morning.
Some toy problems (such as N Queens) only have hard constraints. Some problems have 3 or more levels of constraints, for example hard, medium and soft constraints.
These constraints define the score calculation (AKA fitness function) of a planning problem. Each solution of a planning problem can be graded with a score. With Planner, score constraints are written in an Object Orientated language, such as Java code or Drools rules. Such code is easy, flexible and scalable.
A planning problem has a number of solutions. There are several categories of solutions:
A possible solution is any solution, whether or not it breaks any number of constraints. Planning problems tend to have an incredibly large number of possible solutions. Many of those solutions are worthless.
A feasible solution is a solution that does not break any (negative) hard constraints. The number of feasible solutions tends to be relative to the number of possible solutions. Sometimes there are no feasible solutions. Every feasible solution is a possible solution.
An optimal solution is a solution with the highest score. Planning problems tend to have 1 or a few optimal solutions. There is always at least 1 optimal solution, even in the case that there are no feasible solutions and the optimal solution isn't feasible.
The best solution found is the solution with the highest score found by an implementation in a given amount of time. The best solution found is likely to be feasible and, given enough time, it's an optimal solution.
Counterintuitively, the number of possible solutions is huge (if calculated correctly), even with a small dataset. As you can see in the examples, most instances have a lot more possible solutions than the minimal number of atoms in the known universe (10^80). Because there is no silver bullet to find the optimal solution, any implementation is forced to evaluate at least a subset of all those possible solutions.
Drools Planner supports several optimization algorithms to efficiently wade through that incredibly large number of possible solutions. Depending on the use case, some optimization algorithms perform better than others, but it's impossible to tell in advance. With Planner, it is easy to switch the optimization algorithm, by changing the solver configuration in a few lines of XML or code.
Drools Planner is production ready. The API is almost stable but backward incompatible changes can occur. With
the recipe called UpgradeFromPreviousVersionRecipe.txt
you can easily upgrade to a newer version and quickly deal with any backwards incompatible changes. That recipe file
is included in every release.
To try it now:
Download a release zip of Drools Planner from the Drools download site.
Unzip it.
Open the directory
examplesand run the script.Linux or Mac:
$ cd examples $ ./runExamples.sh
Windows:
$ cd examples $ runExamples.bat
The Examples GUI application will open. Just pick an example:
Note
Planner itself has no GUI dependencies. It runs just as well on a server or a mobile JVM as it does on the desktop.
To run the examples in your favorite IDE, first configure your IDE:
In IntelliJ and NetBeans, just open the file
examples/sources/pom.xmlas a new project, the maven integration will take care of the rest.In Eclipse, open a new project for the directory
examples/sources.Add all the jars to the classpath from the directory
binariesand the directoryexamples/binaries, except for the fileexamples/binaries/drools-planner-examples-*.jar.Add the Java source directory
src/main/javaand the Java resources directorysrc/main/resources.
Next, create a run configuration:
Main class:
org.drools.planner.examples.app.DroolsPlannerExamplesAppVM parameters (optional):
-Xmx512M -serverWorking directory:
examples(this is the directory that contains the directorydata)
The Drools Planner jars are available in the central maven repository (and also in the JBoss maven repository).
If you use maven, just add a dependency to drools-planner-core in your project's
pom.xml:
<dependency>
<groupId>org.drools.planner</groupId>
<artifactId>drools-planner-core</artifactId>
<version>...</version>
</dependency>
This is similar for gradle, ivy and buildr. To identify the latest version, check the central maven repository.
If you're still using ant (without ivy), copy all the jars from the download zip's
binaries directory and manually verify that your classpath doesn't contain duplicate
jars.
Note
The download zip's binaries directory contains far more jars then
drools-planner-core actually uses. It also contains the jars used by other modules, such as
drools-planner-benchmark.
Check the maven repository pom.xml files to determine the minimal dependency set for
a specific version of a specific module.
You can also easily build Drools Planner from source yourself.
Set up Git and clone
drools-planner from GitHub (or alternatively, download the zipball):
$ git clone git@github.com:droolsjbpm/drools-planner.git drools-planner ...
Then do a Maven 3 build:
$ cd drools-planner $ mvn -DskipTests clean install ...
After that, you can run any example directly from the command line, just run this command and pick an example:
$ cd drools-planner-examples $ mvn exec:exec ...
Your questions and comments are welcome on the user
mailing list. Start the subject of your mail with [planner]. You can read/write to the
user mailing list without littering your mailbox through this web forum or this newsgroup.
Feel free to report an issue (such as a bug, improvement or a new feature request) for the Drools Planner code
or for this manual to the drools issue tracker.
Select the component drools-planner.
Pull requests (and patches) are very welcome and get priority treatment! Include the pull request link to a JIRA issue and optionally send a mail to the dev mailing list to get the issue fixed fast. By open sourcing your improvements, you 'll benefit from our peer review and from our improvements made upon your improvements.
Check our blog, Google+(Drools Planner, Geoffrey De Smet) and twitter (Geoffrey De Smet) for news and articles. If Drools Planner helps you solve your problem, don't forget to blog or tweet about it!