Feature Requests

"The employee contracts feature of Timefold allows to e.g. define maximum numbers of hours per day, or per week. These limits are for fixed timeframes. But certain labour laws, or company policies, or contracts might also have requirements for rolling time windows (e.g. maximum numbers of hours worked over a rolling time window of 48 hours). Such time windows can potentially also span longer than the planning window. This is a request to make that type of contract restrictions for rolling time windows possible."

Use case: * There is already a schedule (existing planning solution, manual planning, etc) * there come in new unplanned visits * Task: Fit the unplanned visits into the schedule with keeping as much of the existing plan as-is currently we allow for freezing up a plan up until a certain moment, but that doesn’t allow to have new visits replanned before (if optimal).

For shift pairings / pairedEmployee, allow additional shifts to be selected (currently only one shift can be selected). For example, Anderson prefers to work with Brown when Anderson is working shift 1 and Brown on Shift 2. Currently, we can only select one shift and can't specify the shift order (i.e. if Anderson on this shift, then pair with brown, assigning brown to this shift. { "pairedEmployee": "BROWN", "onlyForShiftTags": ["Shift_1"] }

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.