Feature Requests

We're asking to include the rule ID for the recommendation API (i.e. the API that makes the recommendation of the next best employee that can be assigned to the shift). Currently, the recommendation api only shows the rule category, not the individual rule. We would like to see the individual rule included in the recommendation API. E.g. if you have configured multiple periodRules, we would like to see the recommendation API output constraint diffs per rule, and not only aggregated. Similar like the justifications do.

When sending input files with lots of pinned items, it is relevant to see how much the solver could fit on top of the already pinned items. With an extra column that shows the pinned items in the input this would put the assigned shifts (for Employee shifts) in perspective.

The match KPI shows 100 if the matches is > 100. It is ok that the list is limited to first 100 for UI performance reasons but it is a pity that the total number in the table is not reflecting reality

Some (not all) shifts can be rescheduled, date and/or time. I.e. ideally the shift is nov 11th, 10am-11am but if that is not possible, it may be rescheduled to nov 12th, anywhere AM or nov 13th 11am-12am. There can be an order of preferred alternatives, this can be a range or an exact slot. All the rules need to be configurable within the dataset, not global (difference groups have different rules). Potentially also the duration of a shift would be somewhat dynamic.

Currently, DST change works fine for shifts, but Employee has a static timezone offset used to interpret the period date spans start and end (e.g. start and end of a day). This works fine for multiple timezones but during a DST change, the Employee's offset should change according the time zone rules.

This is a request for Timefold to build a model that assigns jobs to machines over days and weeks, optimizing for production efficiency, minimizing completion time and makespan, and balancing workloads across resources.

This is a request for Timefold to build a model that assigns jobs to machines over minutes and hours, optimizing for production efficiency, minimizing completion time and makespan, and balancing workloads across resources.

This request is to allow configuring traffic impact on various dimensions (time, region etc) to adjust expected travel time for known traffic impact.

"Today solver pods are started at the moment a request for a new model run is received by the platform. The pod takes a few milliseconds to seconds to start. This time could be reduced by always having pods on standby ready to execute runs as soon as they are submitted. This obviously comes with an additional costs, since then pods will have to be running and will be idle at times that no requests have been done as well. However this cost might be worth it for certain types of planning where response time is critical."

This is a request to have cost as an optional decision factor in the overall optimization. If fuel costs, wages and overtime costs are provided to the model, the model can use this to calculate costs and then optimize for cost reduction. Additionally the model can then expose KPIs reflecting these costs and their total.