Feature Requests

Today, the modelOutput for a Field Service Routing run doesn't contain any visits that are unassigned. So, as a consumer of the results you need to cross-check with the input you gave the model to find them. It would be easier if the output also contained the unassigned visits.

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 define exclusions of technicians/vehicles for certain visits. This hard requirement can then be used to e.g. avoid conflicts of interest, adhere to medical restrictions, etc.

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

This is a feature request to make it possible to define rules around weekends for employees. E.g.: The employee must work a maximum of X weekends in Y weeks The employee must have a minimum of X weekends off in Y weeks The employee must work a maximum of X weekends in a period The employee must work a maximum of X consecutive weekends in a period The employee must have a minimum of X consecutive weekends off in a period The employee must work a maximum of X hours in a weekend (from Saturday 00:00 to Sunday 24:00) - is weekend a new period type? The employee must have a minimum of X weekends off in a period, this rule does not include absence (we can drop the absence requirement in the v1, maybe needs to be handled in more constraints) The employee must work a maximum of Z consecutive weekends The employee must work a maximum of every X weekends (maybe this can already be handled by pairing rules)

This is a request for the Field Service Routing model. Technicians have ratings for their past work (Similar to Google maps reviews, a customer based opinion on how good the technician did the job). The software should prioritize assigning work to the technicians with the highest ratings on the job. The weight of this constraints should be configurable

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

This is a request to make it possible to define rotations for shift types. Today something similar can be done by defining multiple combinations of shift pairing rules rules, but this often results in hundreds of pairings to define. By allowing to define e.g. weekly rotations for shift types, this would become a lot easier.