Feature Requests

For real-time replanning use cases it would be very helpful if you can refer to an existing plan (run) and only have changed data elements in the input instead of the complete input payload (e.g. new visits to take into account for Field Service Routing, a sick employee for Employee Scheduling).

For security-sensitive integrations, it would be valuable to allow custom HMAC signing options for webhooks. Specifically: Choose which headers carry the signature and timestamp. Add prefixes or postfixes to header values. Select whether the signature is calculated over the request body or the request path. This would give teams more flexibility to integrate with systems that have strict or unique webhook requirements.

This is a request to have a map available in the Timefold Platform that covers the full United States region, so routing problems spanning the full US-region can be solved in one run, instead of separate runs per state / region in the US.

It's possible to connect external map providers to Timefold for self-hosted installations (see https://docs.timefold.ai/timefold-platform/latest/self-hosted/maps-service#external_map_provider ). This is a request to also make this possible for the Timefold Cloud Platform.

On openshift local running on silicon mac i get: Back-off pulling image " ghcr.io/timefoldai/osrm-dach:latest ": ErrImagePull: choosing an image from manifest list docker: //ghcr.io/timefoldai/osrm-dach:latest : no image found in image index for architecture "arm64", variant "v8", OS "linux" Unfortunately there is no possibility to run openshift local under x86_64 / amd architecture.

This is a request to make it possible to see a list of changes made to your tenant and other settings in the Platform's UI

Ability to have termination settings that take into account time, improvement percentage.

This request is to make it possible to submit a planning problem (e.g. an employee roster, or a routing plan) as a static plan. The plan doesn't need to be further optimized, but the run should be: scored (constraint scores, etc.) have computed input & output metrics The run should be distinguishable from other optimized runs. The use case of this is so that you can then: compare the reference run to other runs via https://feedback.timefold.ai/feature-requests/p/ability-to-compare-kpis-and-statistics-from-different-runs have the same metrics computed by Timefold as for other runs

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

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