Hi Evert, Op 24-03-11 15:10, Evert Penninckx schreef: This is the normal way for hard constraints. This is a really bad idea. Take a look in the latest snapshot/hudson reference manual in the section about "Delta Score calculation" to understand why. https://hudson.jboss.org/hudson/view/Drools%20jBPM/job/drools-planner/las... Then they are called "build-in hard constraints". It's quite difficult to do this right, but as SimpleTravelingTournamentApp vs SmartTravelingTournamentApp proves, this can be definitely worth doing, because the smart one is a lot better. See "tip and tricks" section in the reference manual. But still, in my experience, making some constraints "build-in hard constraints" is a short term gain, but a possible long term loss, because you're limiting the freedom of moves. But this is use case specific. Generally, in my experience, I prefer just mixing in course-grained moves together with the fine-grained moves first, before experimenting with build-in hard constraints. -- With kind regards, Geoffrey De Smet