Shift proximity constraint for disruption rules
complete
M
Matej Cimbora (Solutions)
The disruption rules allow us to define "disruption windows" where selected shift re-assignments are penalized.
Typically, the disruptions in the near future are penalized more than the later disruptions.
It would be useful to have a finer granularity for the disruption for use cases where the disruption window is insufficient.
One example would be allowing the disruption only when the new shift overlaps with the original (disrupted) shift, or is within a certain scope (e.g. +- 2 hours).
The motivation is that the employees have possibly already arranged their plans based on the original shift, so we want the "new" shift to be as close to the original one as possible.
This could be a hard constraint, for some employees it's a preference, for others it's a requirement.
Log In
Jurriaan Persyn
marked this post as
complete
We’re excited to let you know that this feature is now available since our last release.
Thank you for sharing your feedback, it helps us make Timefold even better for you.
To start using the feature, see https://feedback.timefold.ai/changelog/machine-readable-validation-errors-for-fsr-weights-for-preferences-in-ess-and-mo for more details. If you have any questions or further suggestions, feel free to reach out!
Jurriaan Persyn
VP Product
Jurriaan Persyn
marked this post as
in progress
Jurriaan Persyn
marked this post as
under review