{"action":"closed","issue":{"url":"https://api.github.com/repos/jsprit/jsprit/issues/160","labels_url":"https://api.github.com/repos/jsprit/jsprit/issues/160/labels{/name}","comments_url":"https://api.github.com/repos/jsprit/jsprit/issues/160/comments","events_url":"https://api.github.com/repos/jsprit/jsprit/issues/160/events","html_url":"https://github.com/jsprit/jsprit/issues/160","id":78066360,"number":160,"title":"Question on business case","user":{"login":"demonicmetalcs","id":11269977,"avatar_url":"https://avatars.githubusercontent.com/u/11269977?v=3","gravatar_id":"","url":"https://api.github.com/users/demonicmetalcs","html_url":"https://github.com/demonicmetalcs","followers_url":"https://api.github.com/users/demonicmetalcs/followers","following_url":"https://api.github.com/users/demonicmetalcs/following{/other_user}","gists_url":"https://api.github.com/users/demonicmetalcs/gists{/gist_id}","starred_url":"https://api.github.com/users/demonicmetalcs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/demonicmetalcs/subscriptions","organizations_url":"https://api.github.com/users/demonicmetalcs/orgs","repos_url":"https://api.github.com/users/demonicmetalcs/repos","events_url":"https://api.github.com/users/demonicmetalcs/events{/privacy}","received_events_url":"https://api.github.com/users/demonicmetalcs/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jsprit/jsprit/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":35,"created_at":"2015-05-19T12:24:37Z","updated_at":"2015-07-29T19:32:21Z","closed_at":"2015-07-29T19:32:21Z","body":"Good afternoon,\r\n \r\nWe have a business case which we are trying to adapt JSprit for and so far we're very impressed with the results. We have a scenario though which seems very inefficient and I was wondering if you have a solution or a different way of handling this.\r\n \r\nThe goal is to schedule jobs for a longer period of time. For example we have 60 mechanics and 2500 orders they have to get through in a month. What we do right now is do the calculations for 1 day, take away the scheduled orders from the batch and do another calculation for the next day etc. etc. till we have scheduled a full month.\r\n \r\nThe issue here being that we basically do 2000 iterations for every day in the selection. This also means that we would never be able to schedule out a full year for example, because of the time it takes with big selections. (30000 jobs for 4 mechanics already took us 40ish seconds per iteration). \r\n \r\nTo put it a bit more concrete, we would like the ability to schedule in routes over a longer period of time taking into account obviously that a mechanic does not work 24 hours a day. Our current approach is as mentioned, we calculate a new route for every day removing the ones we already scheduled. Is this the right approach? \r\n \r\nThank you very much for your help, I am looking forward to your input. \r\n \r\nKind regards, \r\n \r\nConnor."}}