Public Platform launch, with trials for models (v0.26.2)

Today we’re publicly announcing the Timefold Platform. This new version of the Timefold Platform comes with the following improvements:

Timefold Platform has a new look. We’ve redesigned the UI to look more modern, professional and clean. Additionally, the platform is now easier to use on mobile devices.
Users can now self-register on app.timefold.ai and try out our Timefold Models.
Our Privacy Policy and Terms of Use have been updated to govern the use of (trials on) the Timefold Platform.
We’ve also made the following minor changes: Model Run names are limited to 255 characters, Model Run tags have a maximum of 100 characters, and we’ve introduced better validation for names of a Timefold tenant.

The new version also comes with updates to these Timefold Models:

Field Service Routing (v1 | Stable)

The recommendation API has been extended with dependent vehicle shifts. We’ve added
includeDependencies
as a new parameter to the
VisitTimeWindowRecommendationRequest
API. With this parameter you can select whether you want to check for possible dependent vehicle shift plans that might be influenced by a recommendation. If the recommendation for a visit puts it before other visits, it might change the arrival, start of service, and departure times of the previously planned visits. If those visits have relations to other visits (e.g. visit groups, visit dependency), the recommendation might also affect other vehicle shift plans. By setting the
includeDependencies
parameter to
ALL
, these dependencies will be part of the response.
We’ve changed the order of the KPI’s shown in the UI on the Model Run details page to focus on travel times before travel distances.
When running demo datasets via the Platform UI, we have added descriptions of what the demo data showcases and which features it highlights (basic features, visit groups, or visit dependencies).
We’ve updated our lunch breaks feature guide to include an explanation video.
We’ve added documentation on how to use the OpenAPI Spec.

Employee Shift Scheduling (v1 | Stable)

We’ve added a constraint to minimize gaps between split shifts for an employee. We’ve added a constraint to prefer assigning employees to shifts that are close to each other to minimize the time between those shifts. This is useful for cases where the employee works multiple shifts per day. See Minimize gaps between shifts for employee rule for more information.
When running demo datasets via the Platform UI, we’ve added descriptions of what the demo data showcases and which features it highlights (basic features, contract rules, or hourly demand).
We’ve made a minor bugfix to the visualization of a model run, and improved the overlay to show the full IDs of shifts.
There is a new guide explaining the employee preferences features.
We’ve added documentation on how to use the OpenAPI Spec.

Please let us know if you have feedback.