Visit SLA’s, technician ratings support for FSR, FTE support for ESS (v0.42.1)

Today, we’re announcing version v0.42.1 of the Timefold Platform and v1.0.0 of the Timefold models.

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

(For self-hosted installations only:)
OIDC configuration now requires valid OIDC setup
: When using OpenID connect, make sure you have valid OIDC configuration, else explicitly disable it as per the updated “Installation instructions”.
Filter on Configuration Profile via Platform UI
: It’s now possible to filter the runs overview of your models by the configuration profile that was used. On the overview, click “Add filter”, and choose “Configuration profile”. We’ve also added Configuration profile as one of the possible columns for your overview. Click on the three dots at the end of the header of the table to choose which columns you want to view.

See which configuration profile was used for each run.

Choose and reorder the columns you want to see in the overview

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

Field Service Routing (v1 | Stable)

Ability to define SLA's for visits
: Often visits not only have time windows describing the general availability of the location, but they also have a preferred time for when the task of the visit should be finished, often referred to as a Service Level Agreement (SLA). More information can be found in the feature guide for Visit SLAs.
Ability to prefer picking technicians with higher ratings
: We have added a new feature that allows you to specify the rating of each technician based on feedback from previous visits. Technicians can be assigned to visits based on their ratings where technicians with the highest ratings are more likely to be assigned. Learn more in the Technician ratings feature guide.
Ability to exclude technicians/vehicles for certain visits
: We have added the possibility to prohibit vehicles from being assigned to a visit. You can specify this in the visit's
prohibitedVehicles
attribute when submitting a new route-plan. See Prohibited vehicles in the Visit requirements guide.
Several smaller bugfixes, see “New and noteworthy”.

Employee Shift Scheduling (v1 | Stable)

Allow to define employee min/max by FTE
: We have added support for full-time equivalent (FTE) configuration in employee contracts, enabling fair scheduling for employees with different employment types. This feature allows you to define part-time, full-time, and other employment arrangements while ensuring fair distribution of work. The “balance time worked” constraint now automatically adjusts for different FTE levels, so a part-time employee (FTE 0.5) working 20 hours is considered equivalent to a full-time employee (FTE 1.0) working 40 hours. See “New and noteworthy” for details.
Extended support for weekend constraints for rolling windows
: We have extended our weekend constraints support with the ability to limit weekend work in rolling windows. You can now additionally express rules such as: “Maximum 2 weekends worked in any 4-week rolling window” or “Maximum 4 weekends worked in any 16-week rolling window”. This complements our existing weekend constraints for fixed periods, giving you more options for creating employee-friendly schedules. See “New and noteworthy” for details.
A small bugfix related to the solver not terminating properly in corner cases.

Please let us know if you have feedback.