Hi Prabakar, Op 13-07-11 18:58, DroolersEye schreef: The more time you give a planning problem, the better solution it will be. Many examples are configured to run for 10 minutes, but yield a good, feasible solution after a minute or less. Just click the "terminate early" button to see it. Planner examples 5.3 will be able to refresh the gui screen as the planner finds new best solutions. However, if you do give it 10 minutes, you 'll get a even better solution. The examples which big data and many constraints take a few seconds (sometimes even a minute) to initialize. That's probably what you're seeing. Probably intended: Which example did you try out? Copy/paste the log if you're unsure it's intended. True (although I doubt it hinders much). Screenshots are a maintenance nightmare. Please create a jira for this: http://issues.jboss.org The reference manual (user guide) and the examples centralize all the material we got. Could you point out where the user guide was to abstract to understand? -- With kind regards, Geoffrey De Smet

Prabakar, The alternative would be a custom algorithm, which will be slower than Planner. However, you should limit how long you want Planner to solve. I'd recommend a short time in your case, such as 30 seconds or 1 minute. It depends on the size of your data set of course. Planner 5.3 will support out-of-the-box construction heuristics. If time is really short, you might you use a construction heuristic and no tabu search or SA at all (although I 'd still recommend to do a few seconds of TS or SA anyway). Also, you probably don't want more Planners running at the same time than your numberOfCpuCores - 1. In that situation you 'll want to queue the planning jobs: there's no jbpm-planner integration yet that does that for you yet, but patches (pull requests) are welcome ;) Op 14-07-11 21:39, DroolersEye schreef: -- With kind regards, Geoffrey De Smet