Rolling time windows contract requirements for ESS, input metrics, and several other improvements (v0.38.0)

Today, we’re announcing version v0.38.0 of the Timefold Platform and models, including improved timeline and statuses for each model run.

This new version of the Timefold Platform comes with these platform improvements:

See and compare the amount of scheduled entities and other problem size metrics
: When viewing details of a single model run, we’ll now also show some metrics related to the input. These metrics indicate the problem size and will give you more context when comparing multiple runs.
Expiry dates for tenant members
: In cases where you want colleagues or partners to have temporary access to your Timefold tenant, you are now able to set an expiry date. You can use this feature to e.g. give Timefold Solution Engineers temporary access to your tenant to help you with a certain project or troubleshooting.
Ability to self-host the Timefold Platform on OpenShift
: We added support for OpenShift deployment for self hosted installations. See updated Installation instructions for details.
Documentation updates
: We have added a guide to help you troubleshoot failing runs for self-hosted installations.

Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:

Employee Shift Scheduling (v1 | Stable)

Support for contract requirements for rolling time windows
: We have introduced several rolling window rules that allow you to specify both required and preferred amount of shifts, days, minutes, etc. worked over a rolling time window (instead of e.g. fixed weeks). This feature can help formulate requirements that need to be satisfied over a rolling window of time, for example: Maximum 10 Sunday shifts worked in any 52-week period, Maximum 40 hours worked in any 7-day period, Minimum 11 consecutive hours off in any 24-hour period. See “New and noteworthy” for details.
Days off per period in range for employees
: We have introduced 2 new constraints for better handling of days off. This feature allows a minimum and/or maximum of days off per period to be set on contracts. See “New and noteworthy” for details.

Field Service Routing (v1 | Stable)

Rebalanced hard constraint weights: A missing skill or tag in an input dataset was penalized as
-1hard
resulting in a much smaller penalty than, for example, violating the maximum service end time of a visit. As a result, an infeasible solution that broke a skill or tag requirement was favored over an infeasible solution with all skills/tags but that didn’t finish the service in time by a couple of minutes. See “New and noteworthy” for details.
We have done a small bugfix to the visualization.

Please let us know if you have feedback.