Feature Requests

This is a request to make it possible to define SLA's for each visit. The model should then take this into account to reduce the risk of visits happening outside of SLA.

Imagine a scenario where 3 visits need to happen at the same location. Each visit would take about 15 minutes (some preparation, the task, evaluation). But if you would do them together, the total time of doing all 3 together might be shorter than 3 times 15 minutes. This is a feature request for the Field Service Routing Model to support automatic collapsing of visits in such scenarios.

This is a request for the Timefold Platform to be easy to install and use on Red Hat's OpenShift Platform: https://www.redhat.com/en/technologies/cloud-computing/openshift

Today you can use constraint weights to influence the importance of each constraint on a computed plan. But, since multi-objective optimization is a complex interplay of different trade-offs, it's hard to predict the outcome of such an action/change. This is a request to make it possible to instead start from defining ideal values for the output metrics of a plan, and then let Timefold figure out what the idea combination of constraint weights is - via hyper-tuning - for that desired outcome.

Today, if you want to tweak the configuration of a model (which you could do for a benchmarking or goal alignment use case), you have to re-run datasets one-by-one. This is time & resource consuming. This has the risk of overfitting. Ideally, it should be possible to select a certain segment of your datasets, and then re-run with a different configuration profile on representative datasets.

Each Timefold tenant has limitations on the amount of concurrent threads that can be used by the tenant. This is defined by the tenant's plan. When the maximum is reached, today the platform rejects new runs, and it's on the API end user to retry later. This is a request for the platform to allow to queue further runs, that then start when there are again threads available.

This is a request to make it possible for custom models running on the Timefold Platform (see https://feedback.timefold.ai/feature-requests/p/ability-for-the-timefold-platform-to-run-custom-models ) to use the Maps service of the Platform. This way model developers don't have to worry about creating a maps service to solve routing problems themselves.

This is a request to make it possible for model developers that have built own custom models with Timefold Solver or Timefold Solver Enterprise to run these models on the Timefold Cloud Platform. This will benefit the model developers, as they will get infrastructure and scaling.

This is a request to expose Public API endpoints that return: number of runs statistics about the kpis/metrics (input & output) of those runs: e.g. average/median/max/min Filterable by: tag date range

"This is a request to add an Insights page at the Model level that plots KPI of different model runs on graphs, and that has metrics of the amount of runs per time period. Ideally this page is filterable by tag, so that tags can be used to segment model runs, and the Model Insights page can be used to see how KPIs and other run metrics for a certain segment evolve."