This new version of the Timefold Platform comes with the following improvements:

• We have introduced documentation about Planning AI concepts. This documentation will help to understand the concepts used in Timefold software.
• Several stability and performance improvements were made, including fixes for headless set-up of the Timefold platform and better validation when location coordinates are provided as part of input data.

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

• Field Service Routing (v1 | Stable)
• Improved Demo Data
• We have replaced the existing demo datasets with new ones that are more realistic and better showcase the model’s features.
• The new demo datasets cover basic Field Service Routing capabilities, Visit Groups, and Visit Dependencies.
• New visit dependency feature
• We have added `minStartDateAdjusterIncrement` to the `minDelayTo` `VisitDependency`. The value determines how many times the `minStartDateAdjuster` is applied. This allows a more precise control over the delay.
• More information can be found in Dependencies between visits under Visit dependency with minimum delay as a point in time.
• There is a new feature guide explaining lunch breaks and personal appointments.

• Employee Shift Scheduling (v1 | Stable)
• Improved Demo Data
• We have replaced the existing demo datasets with new ones that are more realistic and better showcase the model’s features.
• The new demo datasets cover basic Employee Shift Scheduling capabilities, Contract Period Rules, and Hourly Demand Rules.
• Flexible shift priorities
• We have added the ability to define custom priorities and weights for shifts. Whenever the model needs to choose between multiple shifts to assign to an employee, it will favor shifts with higher priority.
• See Unassigned shift rule for more information.
• Added constraints to check maximum number of locations worked for an employee
• We extended the period rules to restrict the maximum number of locations an employee works during a period.
• See documentation of the rules for more information:
• Locations worked per period not in required range for employee
• Locations worked per period not in preferred range for employee
• There is a new guide explaining the employee availability features.

Please let us know if you have feedback.

This new version of the Timefold Platform comes with the following improvements:

• We have improved the login flow, so we don't ask for permissions again when you already granted them.
• Several stability and performance improvements were made to handle large input files.

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

• Field Service Routing (v1 | Stable)
• We have renamed “multi-resource” to “multi-vehicle” in the documentation, to more clearly indicate what this feature can be used for.
• We have updated the logo for this model.

• Employee Shift Scheduling (v1 | Stable)
• We are renaming the “Employee Scheduling” model to “Employee Shift Scheduling” to distinguish between future other models involving scheduling for employees.
  (We are not changing API urls or entity names.)
• We have also marked this model as “Stable”, meaning that we promise backwards-compatibility for future minor releases. Read more about model maturity levels.
• We have updated the logo for this model.
• We have removed the shift’s duration from the constraint’s penalty. We now only consider the shift’s assignment priority.

Please let us know if you have feedback.

This new version of the Timefold Platform comes with the following improvements:

• We have added pagination to a model’s run overview.
• There is now documentation about how to interpret the results of a model run. It also includes tips for next steps to take.
• We have fixed several bugs, including more gracefully handling when you haven’t confirmed your email address yet, and we resolved a bug where users saw an empty homepage if they have access to multiple tenants.

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

• Field Service Routing (v1 | Stable)
• We have added the capability to specify that a certain visit needs to be done by a certain vehicle. More information can be found in Visit assignment restrictions.
• We have fixed a bug where fixed breaks with locations sometimes started earlier than requested.
• We have added a feature guide that explains how to use Skills and skill levels.
• The “Time windows and opening hours” feature guide now includes documentation on how to use Fixed visits.
• We have removed the separate cURL Instructions page, since these instructions are now part of the Getting Started guide.

• Employee Scheduling (v1 | Preview)
• We have removed the separate cURL Instructions page, since these instructions are now part of the Getting Started guide.

Please let us know if you have feedback.

This new version of the Timefold Platform brings several small bug fixes, as well as updates to these Timefold Models:

• Field Service Routing (v1 | Stable)
• We have added the ability to specify that specific visits need to be assigned to the same vehicle. See Visit dependencies with coordination for more information.
• We have made improvements to our Feature Guides about Time windows and opening hours and Shift hours and overtime. Both now contain improved input and output examples.
• Employee Scheduling (v1 | Preview)
• We have made several speed improvements for fairness rules in Employee Scheduling.
• Tags can now be used to define preferred and required shifts for employees. See documentation of the Employee object for more information.
• We have improved our documentation related to tags to more clearly give an overview of their possible uses. See Tags and tag types for more information.
• We have added input validation to the Employee Scheduling model to help you correct errors.
• We have added a Getting Started guide.

Please let us know if you have feedback.

This new version of the Timefold Platform comes with the following improvements:

• Improved model discovery
  You can now easily explore all models that Timefold Platform supports. You can see the features and documentation of other available models even when you’re not logged in, or if you don’t have a specific model installed on your tenant yet.
• GZIP support in API
  Our API now supports sending compressed payloads and replying with compressed responses. This is especially useful when posting big payloads to the planning endpoints.
• Configure multi-threading in the UI
  Multi-threading support was added to the API in a previous version, now it’s also available to configure in the platform UI. Go to your tenant's Models settings page and create configurations for models to configure the number of threads to use.
• Cancel a run during solving
  When a run is still solving, you can now stop the solving from the UI.
• Improved error pages
  We have improved the error pages in our platform. (We hope you’ll never see this work.)
• Distinguish initializing & solving states
  The platform now distinguishes between when a new run is initializing (e.g. a maps plugin is loading) and when it starts solving. You can see this in the platform’s UI on the Model Run page.
  
  

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

• Field Service Routing (v1 | Stable)
• When defining visit groups, you can now specify they need to be aligned at the end of the visit. You can use this if two or more technicians need to be present for a visit at the end of the job. E.g. both technicians need to be present to finish the task after one technician has completed preparation work. See Visit Group for more information.
• Employee Scheduling (v1 | Preview)
• We fixed a bug for the “minutes between shifts” rules, where the minimum wasn’t always honored for shift sequences.

We have fixed a bug where the protocol of URLs in webhooks were missing. We’ve also improved the validation checks when creating API keys and configuring webhooks.

Our platform documentation has been updated to include information about model versions, model maturity labels, and demo data. See Models for more information.

This version of app.timefold.ai, includes improvements to the two Timefold Models:

• Field Service Routing (v1 - stable)
• You now have more fine grained control over the time between dependent visits. It’s now possible to define the minimum delay as a point in time. See Visit dependency with minimum delay as point in time for more details.
• Bugfix for the OpenAPI specification validation.
• Employee Scheduling (v1 - preview)
• This model now has support for defining when contract period rules are valid. Period rules can be used to define the maximum hours per day or per week that employees can work. We have added support to configure when certain period rules are applicable. See Employee contract period rule for more information.
• Bugfix for the OpenAPI specification validation.

Multi-threading support via API
When you start a new run of a model with the API, you can now define the number of threads that can be used by the solver. By using multithreading, you can get better results faster.
You can specify the number of threads via the `config.run.maxThreadCount` variable in the JSON payload when starting a new run. Go to your Model’s API Spec page in the platform to learn more.
It’s not yet possible to configure this via the platform’s UI.

We’ve also made the following improvements to the platform’s UI:

• Option to specify headers for webhooks
  It’s now possible to configure one or more headers to send along with your webhooks. You could use this feature to send `Authorization` headers.
• Configure data retention
  On a tenant’s new Configuration page you can now configure how long run data, audit data, and score events should be stored in your tenant’s database.
• Added a Changelog page
  We are introducing a Changelog Page (You’re reading it now) on the platform. We will use this page to communicate new features and changes to the Timefold Platform as well as the models it’s running. Find it via the link in the footer of the platform.
• Descriptions for Model KPI’s
  On the “Run Overview” page we have added descriptions to the KPIs of the run to make it easier to understand what each KPI means.
• Login with email and password
  In addition to logging in with your Microsoft or Google account, we’ve now made it possible to register with other email addresses.
  

Various improvements behind the scenes include better error handling and improvements in pod startup time.

Please let us know if you have feedback.

The Timefold Platform exposes two Timefold Models:

• Field Service Routing (v1 - stable)
  Field Service Routing optimizes vehicle routes to visit customer locations with the goal of minimizing the time employees spend traveling and waiting, and increase the number of scheduled visits.
• Employee Scheduling (v1 - preview)
  Efficiently assign work shifts to employees, optimizing for employee availability, cost reduction, and employee satisfaction.

This initial public version of the Timefold Platform includes:

• REST API for easy use of the Timefold Models.
• UI for following up on the status and outcomes of Model Runs, including:
  • Score results (hard/medium/soft).
  • Score analysis results with constraints scores and justifications.
  • Best score graph showing the evolution of scores during solving.
• Tenant management, including member, API keys, and webhook management;

Please let us know if you have feedback or want to try it out.