Feature Requests

This is a request for Timefold to become ISO 27001 certified.

This is a request for Timefold to become SOC 2 certified.

The payload of webhooks by the Timefold Platform now contains: { "id": "<the-id-of-the-run>", "status": "SOLVING_COMPLETED", // See OpenAPI spec's `SolvingStatus` for all possible options "outputLink": "https://...", // Link to the API where you can fetch the run's output "runLink": "https://...", // Link to the API where you can fetch details about the run itself } See https://docs.timefold.ai/timefold-platform/latest/api-usage#_configuring_webhooks Ideally it also contains: the name of the run the tags assigned to the run the id of the model This is useful for deciding which actions to take.

The match KPI shows 100 if the matches is > 100. It is ok that the list is limited to first 100 for UI performance reasons but it is a pity that the total number in the table is not reflecting reality

"Today solver pods are started at the moment a request for a new model run is received by the platform. The pod takes a few milliseconds to seconds to start. This time could be reduced by always having pods on standby ready to execute runs as soon as they are submitted. This obviously comes with an additional costs, since then pods will have to be running and will be idle at times that no requests have been done as well. However this cost might be worth it for certain types of planning where response time is critical."

This is a request for Timefold to make it possible to run the platform and selected models in Microsoft Azure Cloud by installing it from the Azure Marketplace.

Databricks is a data intelligence platform that can be used to house the data useful for Timefold Models. An integration between Timefold and Databricks can be useful for getting the data from external systems transformed to the input needed for a Timefold Model Run, but can also be useful to connect the Timefold Model Run output back to external systems.

Today a model run in the Timefold Platform stops solving after a certain time limit is reached (by setting config.run.termination.spentLimit ) or after a certain amount of time has passed without a better score (by setting config.run.termination.unimprovedSpentLimit ), or after a manual termination signal is issued ("Stop solving" button in the Platform UI, or API call. With this improvement we want to allow configuring a minimum percentage improvement under which a solve run would be terminated.

This is a request to build a comparison feature in the platform where two or more runs can be selected and their KPIs and run metrics be easily compared. These comparisons can then help with evaluating segments of model runs, or help with choosing the right optimization goals or do simulations and tests.

"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."